General discussion

Locked

Samba and Firewal

By smith.garry ·
I have been using samba to conect my linux box and a win98 machine. The problem I've got is that when I install the program firewal, the linux machine disappears out of network neighbourhood. The reason I installed firewal is to use IP Masquerading. This work fine on Suse Linux 6.3, but now I'm using 6.4. I also tried using find computer from windows, but this cannot find the linux box. I can ping the machine from windows with no problem. Any ideas, and is their another way of masquerading without the firewal program

Thanks

This conversation is currently closed to new comments.

5 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Samba and Firewal

by Linuxian In reply to Samba and Firewal

Make sure you have User Datagram Protocol (UDP) ports 137 and 138 and Transmission Control Protocol (TCP) port 139 open. Microsoft Networking ( and Samba ) components rely on these ports (especially TCP port 139) for NetBIOS communication.
Theseare the ports that are used to transport netbios data over tcp/ip which allows you to browse the network via network neighborhood.

Collapse -

Samba and Firewal

by smith.garry In reply to Samba and Firewal

Poster rated this answer

Collapse -

Samba and Firewal

by jherrin1 In reply to Samba and Firewal

check the configuration of firewal, and make sure that all of the ports associated with SMB are open and not closed by the program you installed.

Collapse -

Samba and Firewal

by smith.garry In reply to Samba and Firewal

Poster rated this answer

Collapse -

Samba and Firewal

by smith.garry In reply to Samba and Firewal

This question was closed by the author

Back to Linux Forum
5 total posts (Page 1 of 1)  

Related Discussions

Related Forums