[Samba] Can connect directly, but not browse samba server from
Windows Workgroup network
lars at beagle-ears.com
Wed Apr 16 01:24:49 GMT 2008
Konstantin Gredeskoul wrote:
> I have a Fedora 8 linux server, running samba 3.0.28a-0.fc8. I am
> doing the simplest thing of all - exposing a public read-only share
> within MS Workgroup environment. My server has a fixed local IP
> address (192.168.1.200) and it's on the same subnet as the rest of the
> machines. The server and machines are connected to a 24 port CISCO
> My problem is that I can connect to my samba share from any windows
> computer, by typing it's IP address: \\192.168.1.200\share - and this
> works perfectly.
> But I do not see my samba server when I browser the workgroup from a
> windows machine.
I wonder if this is related to the problem I reported yesterday, also
using 3.0.28a on Fedora Core 8 (Windows 98 client cannot connect.)
I believe the browser announcement is a UDP function, and on my system
it looks like the UDP functions are not operating on that build of
Samba. Please try to do a "netstat -a | grep udp" and see if Samba
(smbd/nmbd) is bound to UDP ports 137 and 138. On my system it is
not ... only the TCP ports are activated.
I think this was working correctly until "yum update" brought in the
current Samba RPM.
A friend of mine is running Samba 3.0.25 on OpenSuSE and reports that
UDP is not bound there either. Have the defaults changed?
How do I turn the UDP based SMB version back on ?
/ Lars Poulsen
More information about the samba