I am using Samba version 3.0.10-1.fc2. It is configured as an NT domain controller and has been working well. I needed to add a routed (over VPN) connection to the system but cannot get the routed clients to access the browse list. The clients are all Windows XP professional. The remote client is not a domain member. All clients work when directly connected to the Samba server (broadcast), whether domain members or not. I run WINS support on Samba which is working. I can see my remote machine registered under WINS and can query the WINS database with nblookup from all clients. DNS is also fine (forward and reverse) from all clients. I can also manually attach to a share from the routed client with a UNC-Path. IP connectivity is fine between all machines in the network, windows connectivity also. It is just the browse list that doesn't work. 192.168.x.y are my local networks, 10.8.x.y is the routed network. Here are the relevant entries from smb.conf: [global] workgroup = KNOBLOCH netbios name = ANIMALHOUSE interfaces = eth0, eth1, eth2, lo bind interfaces only = no wins support = yes passdb backend = tdbsam username map = /etc/samba/smbusers smb ports = 139 44 server string = Samba DC hosts allow = 192.168. 10.8. 127.0.0.1 hosts deny = 0.0.0.0/ security = user local master = yes preferred master = yes os level = 255 domain master = yes domain logons = yes name resolve order = wins lmhosts bcast I would be very grateful if someone knows what is wrong here, Robert von Knobloch.
> It is configured as an NT domain controller and has been working > well. I needed to add a routed (over VPN) connection to the system > but cannot get the routed clients to access the browse list. The > clients are all Windows XP professional. The remote client is not a > domain member. All clients work when directly connected to the Samba > server (broadcast), whether domain members or not. > I run WINS support on Samba which is working. I can see my remote > machine registered under WINS and can query the WINS database with > nblookup from all clients. > DNS is also fine (forward and reverse) from all clients. I can also > manually attach to a share from the routed client with a UNC-Path. > IP connectivity is fine between all machines in the network, windows > connectivity also. It is just the browse list that doesn't work.I suspect that either broadcasting isn't working, i.e. pinging 10.8.x.255 won't reach the remote clients (or pinging that from the remote client won't reach Samba), or the remote machines are broadcasting for the browse list instead of contacting the WINS server directly. Have you told the client PCs the IP of the WINS server? (via DHCP or in the local machine's network config?) Cheers, Adam.
> What concerns me is the NetBIOS reply (NetServerGetInfo response) to > server queries by the domain controller (is also the WINS server - > all on Samba). > But my config has: > local master = yes > preferred master = yes > domain master = yes > domain logons = yesWhat happens if you put the "os level" option back to 33? (or 65.) ?I know it's a long shot, but just in case setting it to 255 is too high...> There is clearly a mismatch between measured responses and the > configuration in smb.conf. Is this a version issue. Would be pleased > to receive any suggestions.I'm sorry I can't help further with this - you might want to post a new topic as it looks like Samba isn't becoming the browse master when it should, as opposed to being a browse list issue. Cheers, Adam.