AVG blocking access to Samba Share

Matt

Any one know why AVG firewall on my Vista laptop is blocking outgoing access to my Samba share on my Linux desktop?

If I enable the firewall, it blocks the request. When I disable it, it's allowing me to connect out to the Linux box.

I've had a look, and the firewall rules have an entry for SMB in there

MikeS

i use a program called iptraf to monitor network connections and it shows where connections are being blocked and terminated

try turning off your linux firewall to rule out that side

could be something simply such as icmp packets are being dropped thus not allowing the 3 way handshake authentication

service iptables stop and try

I am an AVG reseller as well 😛

Matt

It's AVG that is blocking the traffic, not my iptables on the linux box.

MikeS

does the linux box accept icmp packets from your lan ?

MikeS

is it simply a network drive on your windows install [shared folder ] samba ?

and u cannot access the drive ?

Matt

Yeah, if I turn AVG firewall off on my Vista laptop, it allows me to access the samba share which is being served from the Linux PC.

As soon as I turn AVG back on, it doesn't allow the connection.

AVG Firewall On

AVG Firewall Off

MikeS

can u ping 192.168.0.2 with avg up ?

are you hitting your linux box even though it is saying u cannot connect

thats why i use iptraf d00d

does port 139 have a rule to allow your linux box access

137,138,139 445

Matt

Windows Laptop pinging Linux Server

Linux Server pinging Windows Laptop

Can you not set AVG to allow all traffic to and from a certain IP address through?

MikeS

is netbios running ?

could also be nat related but unlikely

Matt

It's definately something AVG is doing on my Windows Laptop.

Just set it to allow all traffic:

and it's letting me access the Linux box.

Matt

Well.....fuck me sideways!

I've just told AVG to do a full application scan for the firewall, and also added port 139 into the SMB firewall rules, as it was only showing 137-138, and it's working!

MikeS

😛

yey it works !

Matt

I'd still like to know exactly how it fixed itself, so I'm going to break it again

MikeS

u sure it was not port 139 causing the problems

Matt

It may have been, but just to be sure, I'll change it back to the original config, and see what happens.