Hi. I'm having a wee problem with Samba. It's configured to be the Netbios Master Browser for my home network. It's working perfectly ..... except that the browse list only contains a single machine - the Samba machine. I can get to any other machine using it's netbios name - \\megans - and everything works fine. The logs all show that it's working alright - it wins all the browser elections and no errors show up. The only weird thing I've noticed is that in the "log.<machine name>" lanman.c is mentioned after a client connection is made (shouldn't come into things at all but I don't think it's any problem??). Otherwise, things look just peachy. I've tried all the usual stuff (smbstatus/smbclient/nbtstat .... created shares and they show up etc), google, docs from all over the place blah yadda etc. Not a damn thing :( Any ideas?? I'm running Debian unstable with the 2.6.6 kernel and Samba 3.0.4. smb.conf [global] netbios name = debian workgroup = Workgroup wins support = yes security = share os level = 65 domain logons = no domain master = yes preferred master = yes local master = yes hosts allow = 192.168.1. 127. interfaces = eth0 lo bind interfaces only = Yes interfaces = 192.168.1.1/24 name resolve order = wins lmhosts host bcast browse list = yes dns proxy = yes printing = cups printcap name = /etc/printcap load printers = yes guest account = nobody log level = 3 log file = /var/log/samba/log.%m Netstat -a shows: tcp 0 0 debian:netbios-ssn *:* LISTEN tcp 0 0 debian:microsoft-ds *:* LISTEN udp 0 0 debian:netbios-ns *:* udp 0 0 *:netbios-ns *:* udp 0 0 debian:netbios-dgm *:* udp 0 0 *:netbios-dgm *:* debian:/usr/local/samba/var/locks# cat wins.dat VERSION 1 0 "__MSBROWSE__#01" 1088324891 255.255.255.255 e4R "DEBIAN#00" 1088283997 192.168.1.1 66R "DEBIAN#03" 1088283997 192.168.1.1 66R "DEBIAN#20" 1088283997 192.168.1.1 66R "MEGANS#00" 1088324846 192.168.1.41 64R "MEGANS#20" 1088324846 192.168.1.41 64R "MTROUSERS#00" 1088324803 192.168.1.10 64R "MTROUSERS#20" 1088324803 192.168.1.10 64R "RITWA#00" 1088311573 192.168.1.12 64R "RITWA#03" 1088311591 192.168.1.12 64R "RITWA#20" 1088311592 192.168.1.12 64R "WORKGROUP#00" 1088324846 255.255.255.255 e4R "WORKGROUP#1b" 1088283997 192.168.1.1 64R "WORKGROUP#1e" 1088324846 255.255.255.255 e4R debian:/usr/local/samba/var/locks# cat browse.dat "WORKGROUP" c0001000 "DEBIAN" "WORKGROUP" "DEBIAN" 400d9a03 "Samba 3.0.4" "WORKGROUP" ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.
Shane Taylor said:
Hi.
I'm having a wee problem with Samba. It's configured to be the Netbios Master Browser for my home network. It's working perfectly ..... except that the browse list only contains a single machine - the Samba machine. I can get to any other machine using it's netbios name - \\megans - and everything works fine.
Hi Shane, Try turning on "wins proxy = yes" in smb.conf You shouldn't need it, but I have seen issues where client machines announce themselves to the master, but it does not re-announce them.
From the man page for smb.conf:
wins proxy (G) This is a boolean that controls if nmbd(8) will respond to broadcast name queries on behalf of other hosts. You may need to set this to yes for some older clients. Default: wins proxy = no Hope that helps. -- Greig McGill
Cheers Greig. Unfortunately that didn't fix the problem. However, it seems to have changed the damn things behaviour. Now, I *sometimes* get 2 out of 4 machines showing in the browse list - mine and a friends. However, the Samba box and Megans don't show. And if I ignore it for a while, it goes back to showing just the Samba machine!! Pram ---------------->>>> Toys :( Shane. Quoting Greig McGill <greig(a)hamiltron.net>:
Shane Taylor said:
Hi.
I'm having a wee problem with Samba. It's configured to be the Netbios Master Browser for my home network. It's working perfectly ..... except that the browse list only contains a single machine - the Samba machine. I can get to any other machine using it's netbios name - \\megans - and everything works fine.
Hi Shane,
Try turning on "wins proxy = yes" in smb.conf You shouldn't need it, but I have seen issues where client machines announce themselves to the master, but it does not re-announce them.
From the man page for smb.conf:
wins proxy (G) This is a boolean that controls if nmbd(8) will respond to broadcast name queries on behalf of other hosts. You may need to set this to yes for some older clients.
Default: wins proxy = no
Hope that helps.
-- Greig McGill
_______________________________________________ wlug mailing list | wlug(a)list.waikato.ac.nz Unsubscribe: http://list.waikato.ac.nz/mailman/listinfo/wlug
---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.
participants (2)
-
Greig McGill -
Shane Taylor