Matias Morawicki
2009-Dec-18 15:15 UTC
[Samba] Cannot see server in win Neighborhood (again)
Hello u all, sorry to bring this issue back again, but I?ve been searching and trying all the advices suggested in previous posts and I still can?t see the samba server in the win network neighborhood. I can see the samba shares from win via net view \\servername but if I issue a plain "net view" samba won?t show up. only the win machines, the same i can see on the Neighborhood... I?ve tried stopping iptables, different smb.conf from the simple examples of t first chapters of samba by example, to plenty of options... that?s why I?m not including my smb.conf, because I?ve tried many variations, always with the same results. I even tried a working smb.conf from another linux box which was showing in win Neighborhood... and when I select local master = no Samba would stay without master! I issue smbclient -L servername -U% and the master section remains empty. It?s like samba is not being able to "talk" to the rest of the workgroup. (of course they are all in the same workgroup) Btw, the server is a Centos 5.3, with samba 3.2.15 (it also happened with the default samba, so I?ve upgraded just in case...) I hope someone can point me some directions... thanks in advance!! Matias
Gaiseric Vandal
2009-Dec-18 15:56 UTC
[Samba] Cannot see server in win Neighborhood (again)
On 12/18/09 10:15, Matias Morawicki wrote:> Hello u all, sorry to bring this issue back again, but I?ve been > searching and trying all the advices suggested in previous posts and I > still can?t see the samba server in the win network neighborhood. > > I can see the samba shares from win via net view \\servername > > but if I issue a plain "net view" samba won?t show up. only the win > machines, the same i can see on the Neighborhood... > > I?ve tried stopping iptables, different smb.conf from the simple > examples of t first chapters of samba by example, to plenty of > options... that?s why I?m not including my smb.conf, because I?ve > tried many variations, always with the same results. I even tried a > working smb.conf from another linux box which was showing in win > Neighborhood... > > and when I select local master = no Samba would stay without master! > I issue smbclient -L servername -U% and the master section remains empty. > > It?s like samba is not being able to "talk" to the rest of the > workgroup. (of course they are all in the same workgroup) > > Btw, the server is a Centos 5.3, with samba 3.2.15 (it also happened > with the default samba, so I?ve upgraded just in case...) > > I hope someone can point me some directions... > > thanks in advance!! > > Matias >Are you using a WINS server- I find that makes a lot of these issues go away. My guess is that your samba machines and windows machines are talking to different net bios browser masters (I use WINS servers to avoid having to figure out this stuff.) I have, at home, run in to this same issue with Windows machines (workgroup not domain, and no samba servers involved) not seeing each other in network neighborhood. Does turning off the XP firewall (assuming that you are using XP Pro) make a difference?
Matias Morawicki
2009-Dec-18 19:01 UTC
[Samba] Cannot see server in win Neighborhood (again)
2009/12/18 Gaiseric Vandal <gaiseric.vandal at gmail.com>> On 12/18/09 10:15, Matias Morawicki wrote: > >> Hello u all, sorry to bring this issue back again, but I?ve been >> searching and trying all the advices suggested in previous posts and I >> still can?t see the samba server in the win network neighborhood. >> >> I can see the samba shares from win via net view \\servername >> >> but if I issue a plain "net view" samba won?t show up. only the win >> machines, the same i can see on the Neighborhood... >> >> I?ve tried stopping iptables, different smb.conf from the simple >> examples of t first chapters of samba by example, to plenty of >> options... that?s why I?m not including my smb.conf, because I?ve >> tried many variations, always with the same results. I even tried a >> working smb.conf from another linux box which was showing in win >> Neighborhood... >> >> and when I select local master = no Samba would stay without master! >> I issue smbclient -L servername -U% and the master section remains empty. >> >> It?s like samba is not being able to "talk" to the rest of the >> workgroup. (of course they are all in the same workgroup) >> >> Btw, the server is a Centos 5.3, with samba 3.2.15 (it also happened >> with the default samba, so I?ve upgraded just in case...) >> >> I hope someone can point me some directions... >> >> thanks in advance!! >> >> Matias >> >> > Are you using a WINS server- I find that makes a lot of these issues go > away. My guess is that your samba machines and windows machines are > talking to different net bios browser masters (I use WINS servers to avoid > having to figure out this stuff.) > > > I have, at home, run in to this same issue with Windows machines (workgroup > not domain, and no samba servers involved) not seeing each other in network > neighborhood. Does turning off the XP firewall (assuming that you are > using XP Pro) make a difference? > > Thanx for the reply Gaiseric!yes, I?m using "wins support = yes" and I?ve set the DHCP to set the clients to use the samba server as wins server.I?ve checked the win clients and they get the correct conf. I haven?t tried turning off the XP firewall, but when I tried a basic samba configuration in a ubuntu server in another box just to test, they were able to see it in the neigbohood... so I guess the issue is on the Centos side. I tried the same smb.conf from that working ubuntu-samba and didn?t make it on the Centos... thanks again! Matias
Are you listening on port 139, or only on port 445? Microsoft had a great idea when they implemented SMB over TCP on port 445 and eliminated the ancient and inefficient NETBIOS over TCP, or NetBT (on port 139). Unfortunately, they didn't think it all the way through - you still need NETBIOS to populate the network neighborhood, so if your Samba server only listens on port 445, you won't get happy in your network neighborhood. In Vista and Windows 7, this problem is fixed: they now use UPnP (renamed to Network Discovery) to populate the network neighborhood (and do a lot of other neat stuff). Samba does not yet support UPnP, though. Bottom line: even though Samba supports turning off NetBT, DON'T. This problem is exacerbated if you are using an IPv6 network, because Microsoft no longer even supports NETBIOS at all.> -----Original Message----- > From: samba-bounces at lists.samba.org [mailto:samba- > bounces at lists.samba.org] On Behalf Of Matias Morawicki > Sent: Friday, December 18, 2009 7:16 AM > To: samba at lists.samba.org > Subject: [Samba] Cannot see server in win Neighborhood (again) > > Hello u all, sorry to bring this issue back again, but I?ve been > searching and trying all the advices suggested in previous posts and I > still can?t see the samba server in the win network neighborhood. > > I can see the samba shares from win via net view \\servername > > but if I issue a plain "net view" samba won?t show up. only the win > machines, the same i can see on the Neighborhood... > > I?ve tried stopping iptables, different smb.conf from the simple > examples of t first chapters of samba by example, to plenty of > options... that?s why I?m not including my smb.conf, because I?ve > tried many variations, always with the same results. I even tried a > working smb.conf from another linux box which was showing in win > Neighborhood... > > and when I select local master = no Samba would stay without master! > I issue smbclient -L servername -U% and the master section remains > empty. > > It?s like samba is not being able to "talk" to the rest of the > workgroup. (of course they are all in the same workgroup) > > Btw, the server is a Centos 5.3, with samba 3.2.15 (it also happened > with the default samba, so I?ve upgraded just in case...) > > I hope someone can point me some directions... > > thanks in advance!! > > Matias > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba
Matias Morawicki
2009-Dec-22 20:44 UTC
[Samba] Cannot see server in win Neighborhood (again)
2009/12/19 Matias Morawicki <matiasmorawicki at gmail.com>> > 2009/12/18 Kevin Keane <subscription at kkeane.com> > > Are you listening on port 139, or only on port 445? >> >> Microsoft had a great idea when they implemented SMB over TCP on port 445 >> and eliminated the ancient and inefficient NETBIOS over TCP, or NetBT (on >> port 139). Unfortunately, they didn't think it all the way through - you >> still need NETBIOS to populate the network neighborhood, so if your Samba >> server only listens on port 445, you won't get happy in your network >> neighborhood. >> >> > mmm I guess so, I?m gonna check on monday... > > thanks 4 the tip!!!! > > >this is very odd... We finally decided to move the server to debian (it was a quite recently installed box and we weren't quite happy with centos) but... same issue!! (sorry about that centos!!!) We're running a ubuntu box with the same simple conf side by side and nothing, win clients can see the ubuntu and not the debian... hardware??? buggy ethernet card??? is that possible?? www server on the debian is perfectly accesible... debian is listening on 139 and 445. this is what i get when from the debian box i issue a smbclient -L winclient (LOLA is the win client) Domain=[JAGUARHOUSE] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager] Server Comment --------- ------- LOLA JAGUARHOUSE PSYD64 psyd64 server (Samba, Ubuntu) Workgroup Master --------- ------- JAGUARHOUSE LOLA this with smbclient -L ubuntubox smbclient -L 192.168.1.101 -U% Domain=[JAGUARHOUSE] OS=[Unix] Server=[Samba 3.4.0] Sharename Type Comment --------- ---- ------- print$ Disk Printer Drivers IPC$ IPC IPC Service (psyd64 server (Samba, Ubuntu)) Domain=[JAGUARHOUSE] OS=[Unix] Server=[Samba 3.4.0] Server Comment --------- ------- LOLA JAGUARHOUSE PSYD64 psyd64 server (Samba, Ubuntu) Workgroup Master --------- ------- JAGUARHOUSE LOLA and this when i do it to the debian itself: linux:/etc/samba# smbclient -L linux -U% Domain=[JAGUARHOUSE] OS=[Unix] Server=[Samba 3.2.5] Sharename Type Comment --------- ---- ------- print$ Disk Printer Drivers IPC$ IPC IPC Service (linux server (Debian)) Domain=[JAGUARHOUSE] OS=[Unix] Server=[Samba 3.2.5] Server Comment --------- ------- LINUX linux server (Debian) Workgroup Master --------- ------- JAGUARHOUSE LINUX is like the debian samba is definitely not "talking" to the others! again, i'm using the basic smb.conf that came with the ubuntu: linux:/etc/samba# testparm Load smb config files from /etc/samba/smb.conf Processing section "[printers]" Processing section "[print$]" Loaded services file OK. Server role: ROLE_STANDALONE Press enter to see a dump of your service definitions [global] workgroup = JAGUARHOUSE server string = %h server (Debian) map to guest = Bad User obey pam restrictions = Yes passdb backend = tdbsam pam password change = Yes passwd program = /usr/bin/passwd %u passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* . unix password sync = Yes syslog = 0 log file = /var/log/samba/log.%m max log size = 1000 dns proxy = No usershare allow guests = Yes panic action = /usr/share/samba/panic-action %d any clues??? thanx again!!! Matias