From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1) Gecko/20031114 Description of problem: When I try to browse the network to access XP machines, I get the message: Couldn't display "smb:///", because Nautilus cannot contact the SMB master browser. Check that an SMB server is running in the local network. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Open up Newtork Servers from the menu. 2. 3. Actual Results: I got the message: Couldn't display "smb:///", because Nautilus cannot contact the SMB master browser. Check that an SMB server is running in the local network. Expected Results: It should have browsed the network and found the other computers on the network. There are other computers (XP computers) that have existing shares. Additional info:
Do you have a firewall enabled on your computer? To check, do service iptables stop as root and try to browse again.
After stopping iptables, I am able to browse and see the network. Should I just turn off the iptables service?
Well it is a "feature". You probably accepted the defaults during the install on the firewall screen which is to block most open ports including the ones needed by Samba to browse. You can do a chkconfig iptables off if you are sure you dont need a firewall or you can run the redhat-config-security tool and open up the necessary ports to allow for Samba browsing and shares.
I have a similar problem, except I don't get a warning, just an empty smb:/// window. I have stopped iptables and restarted smb, but I still get no shares. It works fine the other direction (I can browse the network from XP), and I can smbmount from the command line, but "Network Servers" from the menu gets me nada.
Was K Kane's problem resolved. I experience the same symptoms.
Please attach your smb.conf file to this bug report for review.
Created attachment 97573 [details] Samba Configuration File All modifications to the original smb.conf ar those entries in the file preceeded with the Commented Line "# Gawawh". I hope it is just a boring typo. Some additional info: At installation the system name was 'train90', this has been changed to 'Firewall' via : System Tools -> Network -> DNS -> Hostname (was train90 changed to Firewall). No DNS running, only set up as a DNS Client. I'm not sure if this would be of any assistance, but past experience with node name changes has resulted in erratic behavior. Thank you for your assistance, and I hope it is just a boring 'typo'.
The iptables seem to make no difference. XP can see redhat fine in network neighborhood. Redhat can see XP and itself through smbclient.
I had the same problem as Brent Rowse until I did "service iptables stop". Then, I could view my network fine. However, I restarted iptables with "service iptables start" and I can still see my network.
The way I fixed the problem is to add this line to /etc/sysconfig/iptables: -A RH-Firewall-1-INPUT -i eth0 -j ACCEPT then stop iptables, and start it. this should fix the problem
As there wasn't any recent activity on this I'll mark as duplicate of a recent bug with the same problem. Chris, Bruce please add yourselves as CC there and add any additional info you have. Don't forget to have iptables off. *** This bug has been marked as a duplicate of 168908 ***