Konstantin Gredeskoul
2008-Apr-16 00:27 UTC
[Samba] Can connect directly, but not browse samba server from Windows Workgroup network
Dear Samba gurus,
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
switch.
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 would like to set it up so that the users don't
need to type the IP address when they connect, and rather see the
server in their network neighborhood. But no matter what I do, I can
not see the server listed.
Here's my /etc/samba/smb.conf:
[global]
security = share
workgroup = MYGROUP
server string = Samba Server
netbios name = MYSERVER
comment = My Server
dns proxy = no
load printers = no
[share]
path = /data
read only = Yes
browseable = Yes
public = Yes
guest ok = yes
The samba server does not show up in the "nmblookup" either, but all
other machines do:
> nmblookup MYGROUP
querying MYGROUP on 192.168.1.255
192.168.1.118 MYGROUP <00>
192.168.1.107 MYGROUP <00>
192.168.1.101 MYGROUP <00>
192.168.1.104 MYGROUP <00>
192.168.1.105 MYGROUP <00>
192.168.1.112 MYGROUP <00>
192.168.1.109 MYGROUP <00>
192.168.1.111 MYGROUP <00>
192.168.1.110 MYGROUP <00>
192.168.1.117 MYGROUP <00>
192.168.1.115 MYGROUP <00>
192.168.1.106 MYGROUP <00>
Also, running smbclient against my server shows expected output:
[deploy@arderon tmp]$ smbclient -L 192.168.1.200
Password:
Domain=[MYGROUP] OS=[Unix] Server=[Samba 3.0.28a-0.fc8]
Sharename Type Comment
--------- ---- -------
Share Disk My Server
IPC$ IPC IPC Service (Samba Server)
Domain=[MYGROUP] OS=[Unix] Server=[Samba 3.0.28a-0.fc8]
Server Comment
--------- -------
MYSEVER My Server
Workgroup Master
--------- -------
MYGROUP MYSERVER
MYSERVER KASUGAI
Any idea what could be happening here? Is there some UDP blocking going on?
--
Thanks
Konstantin
blog ? http://tektastic.com
music ? http://polygroovers.com
gtalk ? kigster
Lars Poulsen
2008-Apr-16 01:24 UTC
[Samba] Can connect directly, but not browse samba server from Windows Workgroup network
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 > switch. > > 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
Konstantin Gredeskoul
2008-Apr-16 02:12 UTC
[Samba] Can connect directly, but not browse samba server from Windows Workgroup network
> 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.On my system only 139 tcp is activated. The only udp ports active on my system are 55298 (wth?), 5353 (mdns) and 123 (ntp).> I think this was working correctly until "yum update" brought in the > current Samba RPM.Wow this is a great insight. I might try building a local copy and seeing if that fixes the problem. Thanks much Konstantin blog ? http://tektastic.com music ? http://polygroovers.com gtalk ? kigster
Leonid Zeitlin
2008-Apr-16 12:21 UTC
[Samba] Re: Can connect directly, but not browse samba server from Windows Workgroup network
Konstantin,
Just in case, check that nmbd is running.
Thanks,
Leonid
"Konstantin Gredeskoul" <kigster@gmail.com> ???????/???????? ?
????????
?????????:
news:fd4096480804151726j780faf69qe9721dd991b15fe7@mail.gmail.com...
Dear Samba gurus,
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
switch.
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 would like to set it up so that the users don't
need to type the IP address when they connect, and rather see the
server in their network neighborhood. But no matter what I do, I can
not see the server listed.
Here's my /etc/samba/smb.conf:
[global]
security = share
workgroup = MYGROUP
server string = Samba Server
netbios name = MYSERVER
comment = My Server
dns proxy = no
load printers = no
[share]
path = /data
read only = Yes
browseable = Yes
public = Yes
guest ok = yes
The samba server does not show up in the "nmblookup" either, but all
other machines do:
> nmblookup MYGROUP
querying MYGROUP on 192.168.1.255
192.168.1.118 MYGROUP <00>
192.168.1.107 MYGROUP <00>
192.168.1.101 MYGROUP <00>
192.168.1.104 MYGROUP <00>
192.168.1.105 MYGROUP <00>
192.168.1.112 MYGROUP <00>
192.168.1.109 MYGROUP <00>
192.168.1.111 MYGROUP <00>
192.168.1.110 MYGROUP <00>
192.168.1.117 MYGROUP <00>
192.168.1.115 MYGROUP <00>
192.168.1.106 MYGROUP <00>
Also, running smbclient against my server shows expected output:
[deploy@arderon tmp]$ smbclient -L 192.168.1.200
Password:
Domain=[MYGROUP] OS=[Unix] Server=[Samba 3.0.28a-0.fc8]
Sharename Type Comment
--------- ---- -------
Share Disk My Server
IPC$ IPC IPC Service (Samba Server)
Domain=[MYGROUP] OS=[Unix] Server=[Samba 3.0.28a-0.fc8]
Server Comment
--------- -------
MYSEVER My Server
Workgroup Master
--------- -------
MYGROUP MYSERVER
MYSERVER KASUGAI
Any idea what could be happening here? Is there some UDP blocking going on?
--
Thanks
Konstantin
blog » http://tektastic.com
music » http://polygroovers.com
gtalk » kigster
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba