Guarddog and SMB

TSloth · 05-24-2005, 04:14 PM

I have Guarddog installed on SimplyMEPIS 3.3.

When I turn off Guarddog, I can see the Samba server and its shares.
When I have Guarddog on, I can't see the Samba server and its shares.
When Guarddog is on, /var/log/messages shows occasional messages:
kernel: DROPPED IN=eth0 OUT= MAC= SRC=(me) DST=192.168.0.255 LEN=127 etc.
I think I need to configure Guarddog to let my SMB queries out or back in or something...
Could someone please clue me in - how to adjust Guarddog to allow me to see the Samba server(s) on the network and access their shares?

Thank you,
- TSloth

Capt_Caveman · 05-24-2005, 10:05 PM

In the Guarddog configuration menu, select the protocol tab, then "local network" and then select the Microsoft SMB box, then save and exit. If that still doesn't help, you may need to add the local broadcast address to the local zone.

TSloth · 05-26-2005, 12:56 PM

Thank you, Capt_Caveman! It's working slick as ... can be.
K -> Internet -> Connection -> Smb4K browses the workgroup just fine.

For those who will be setting up Guarddog 2.4.0, it's
Protocol tab
Local zone
expand Network group (in the Network Protocol window)
Microsoft SMB over TCP ... should be checked

- TSloth

IBall · 06-10-2005, 03:13 AM

I have a computer running debian sarge, and I used Guarddog to set up the firewall. However, I can't get my laptop to connect using Samba, or my other linux box to print using CUPS.

They work correctly when I disable the firewall. I have tried the above suggestions, but it still does not work.

Any Suggestions??

Thanks in advance,
--Ian

guldo · 08-20-2005, 11:32 AM

Thank you all for this thread

Anyway, the firewall does not let me mount the windows share.
I mean:

Code:

# mount -t smbfs //192.168.0.2/Share /mnt/xp/ -o username=utente
timeout connecting to 192.168.0.2:445
timeout connecting to 192.168.0.2:139
Error connecting to 192.168.0.2 (Operation already in progress)
29817: Connection to 192.168.0.2 failed
SMB connection failed

How should I fix this?

Thanks

dracolich · 08-24-2005, 04:57 PM

Guldo, is the utente user currently logged on when attempting this? When connecting to a Win2K or XP machine using Samba you have to connect as the currently logged-on Win user.

IBall, if you're still having problems connecting after allowing SMB protocol (port 445), make sure NetBIOS is also allowed for local zone. That opens ports 138 and 139. Those also are required for successful Samba connections. Be sure all three are closed for the internet zone! CUPS requires port 631 to be open. Check on that. I'm not quite sure which brach you'll find it under and I'm not at a Linux box right now. You may have to create an entry for it.