Hi, I have 3 Samba servers run Samba 2.0.7 on RH6.2, with Kernel 2.2.16-3. Everything seems to be OK, except that my Win9x clients cannot see other Win9x clients across the subnets. Each server has 2 n/w cards installed, with IP Forwading enabled etc. If the user knows the machine name, he can get access to the shared resources across all 3 subnets, but using the n/w neighbourhood browser, shows only those users on the same subnet. The Win9x clients are all set to point to the same primary WINS server, and the secondary WINS server is set to the server that they login to. Each of the SAMBA servers has "OS Level =" >=60, to ensure that the NT servers on the network do not become controllers. All the Win9x clients are setup to use the same Workgroup, while the servers are on a separate Workgroup. If this is the problem, how do I resolve this, without changing the workgroups on each client or the servers? Any help will be appreciated. Regards Enrico Payne mailto:enricop@pharma.co.za Below is a copy of the Global section of my smb.conf file for the main (WINS) server... <----SNIP----> [global] workgroup = JBPN netbios name = JBPN1 server string = Samba Server 2.0.7-4 security = DOMAIN encrypt passwords = Yes password server = jbpn1 jbpn4 jbpn6 jbpn3 jbpn7 username map = /etc/smb.username.map restrict anonymous = Yes log file = /var/log/samba/log.%m max log size = 50 name resolve order = host wins bcast socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 load printers = No logon script = start.bat logon path = \\jbpn1\home\profiles\%u domain logons = Yes os level = 65 preferred master = Yes domain master = Yes dns proxy = No wins support = Yes admin users = enricop ryanh <--- END SNIP----> The following is the global section for one of the other servers. <---SNIP---> [global] workgroup = JBPN netbios name = JBPN4 server string = Samba Server 2.0.7-4 security = DOMAIN encrypt passwords = Yes password server = jbpn4 jbpn1 jbpn6 jbpn3 jbpn7 username map = /etc/smb.username.map restrict anonymous = Yes log file = /var/log/samba/log.%m max log size = 50 name resolve order = host wins bcast socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 load printers = No logon script = start.bat logon path = \\jbpn4\home\profiles\%u os level = 60 preferred master = Yes dns proxy = No wins server = xxx.xxx.xxx.xxx # JBPN1's ip address is here <---END SNIP--->
On Wed, 16 Aug 2000 20:14:53 +1000, Enrico Payne wrote:>Hi, I have 3 Samba servers run Samba 2.0.7 on RH6.2, with Kernel 2.2.16-3. > >Everything seems to be OK, except that my Win9x clients cannot see other >Win9x clients across the subnets. > >Each server has 2 n/w cards installed, with IP Forwading enabled etc. If the >user knows the machine name, he can get access to the shared resources >across all 3 subnets, but using the n/w neighbourhood browser, shows only >those users on the same subnet. The Win9x clients are all set to point to >the same primary WINS server, and the secondary WINS server is set to the >server that they login to. Each of the SAMBA servers has "OS Level =" >=60, >to ensure that the NT servers on the network do not become controllers.[...] Well, you didn't machine if any of the NT servers is a PDC or not. The problem with it that a NT PDC is by default a domain master browser. So, if any of your Samba server becomes a domain master browser, the NT PDC will immediately start another domain browser election and will loose, start another election, loose it and so on. Another issue is that you have, according to your smb.conf files, two samba servers defined as preferred masters. The result will be the same as above - at least as far as I know :). Short quotation for browsing.txt that came along with Samba. "Note that you should NOT set Samba to be the domain master for a workgroup that has the same name as an NT Domain: on each wide area network, you must only ever have one domain master browser per workgroup, regardless of whether it is NT, Samba or any other type of domain master that is providing this service." I suggest, you designate one of your NT or Samba servers and domain master browser and make sure, that no other machine ever tries to become a domain master browser. Take a look at ethereal (ethereal.zing.org). You can check the network traffic with ethereal and identify all these master browser elections. On your NT boxes try using browstat.exe that it part of the NT resource kit. That can help you in the troubleshooting (who is master browser, who is backup browser, list the browser list, etc.). -- Etus
Hi Etus, thanks for the response. I should have noted that the NT servers are on different domains to the Linux servers, although they are on the same subnets. Would this make a difference? If I set the the "Preferred Master" to No on all but my Domain Master server, then, from what I understand, they will never become controllers for the other subnets to which they are connected. Surely it would be best for these machines (that have a direct link to both subnets) to be the preferred master browsers, while only one machine is the Domain Master? I am new to this, but this is what I understood from the Samba docs. Any comments? Regards Enrico Payne mailto:enricop@pharma.co.za