Samba WINS server gives old IP address?
Posted on 2004-08-17
I have a WORKGROUP Windows network with 2 Samba servers, PRIMARY and BACKUP. PRIMARY is acting as a file server and a WINS server. BACKUP is rigged to win browse master elections. Typically everything works just fine.
The DHCP server is set to distribute the WINS server address.
There is a Windows 2000 server (SERVER) that was set to get an address with DHCP for some reason. This makes it hard to monitor as its address changes so I want to move it to a static address.
When I change the IP address on SERVER, windows clients can non longer resolve it by name. SERVER is set to register with the WINS server. Many restarts. nbtstat -RR, etc.
BACKUP is not set to use a WINS server. It resolves via broadcast and smbclient -L //SERVER works great.
PRIMARY cannot resolve SERVER. It gets the old address SERVER was at (10.0.0.150) when it was using a DHCP lease. I suspect that's why the client machines get the same problem address.
Running smbclient under debug mode shows that it's getting its address from its own (local) WINS server. I've deleted the contents of /var/cache/samba with samba stopped, to no avail. There isn't an lmhosts file on the samba server, nor is there an entry for SERVER in /etc/hosts. I tried adding a DNS entry for server but that didn't help, even with dns proxy set to be on.
PRIMARY can talk to SERVER by IP just fine, e.g. smbclient -I 10.0.0.10 -L //SERVER
'nmblookup SERVER' on PRIMARY returns the old address.
Exploring with nmblookup and nbtstat shows no additional WINS servers. I've tried forcing elections to no avail.
So, somehow PRIMARY is getting the old address from somewhere, but I'm not seeing who could be offering that information or why it would trust that over the machine's own registration. I don't actually have any reason to believe SERVER is registering via WINS successfully, but I don't have any reason to belive it's failing either. There is nothing noted in SERVER's Event Log.
For now I've assigned SERVER a static lease to keep it still, but I'd like to get it out of the DHCP range.
Thanks for any insight.