samba - Nov 2007 - nmbd keeps trying to contact IP Address on wrong network

Looking for a solution to this problem. I have Googled all over the 
place but haven't found a definitive answer.

I have a Samba Server that ONCE was on a network where there was SECOND 
Samba Server with IP Address 192.168.20.3. Today, the FIRST server is 
on a network with an address range 10.0.0.0/255.255.255.0 and it has no 
way of finding that SECOND Server 192.168.20.3.  However, 
/var/log/messages is full of errors that say:

Nov  4 04:07:29 fileserver nmbd[5248]: [2007/11/04 04:07:29, 0] 
libsmb/nmblib.c:send_udp(791)
Nov  4 04:07:29 fileserver nmbd[5248]:   Packet send failed to 
192.168.20.3(137) ERRNO=Network is unreachable
Nov  4 04:07:29 fileserver nmbd[5248]: [2007/11/04 04:07:29, 0] 
nmbd/nmbd_packets.c:send_netbios_packet(163)
Nov  4 04:07:29 fileserver nmbd[5248]:   send_netbios_packet: 
send_packet() to IP 192.168.20.3 port 137 failed
Nov  4 04:07:29 fileserver nmbd[5248]: [2007/11/04 04:07:29, 0] 
nmbd/nmbd_namequery.c:query_name(245)
Nov  4 04:07:29 fileserver nmbd[5248]:   query_name: Failed to send 
packet trying to query name ACCOUNTING<1b>

I can see that the file /var/cache/samba/wins.dat includes a reference 
to the IP Address 192.168.20.3 (I have seen some postings suggesting 
that wins.dat can be the cause of this error).  If I delete wins.dat 
and restart samba, the reference to 192.168.20.3 comes back.

I can state with total confidence that there are no network interfaces 
on this machine configured to be in the 192.168.20.x range. In fact, 
only one of 3 network interfaces is currently active and has an IP 
Address.

Is there any way that I can get this Samba Server to stop looking for 
192.168.20.3?

-- Andy
________________________________________________________________________
Email and AIM finally together. You've gotta check out free AOL Mail! - 
http://mail.aol.com

andyliebman@aol.com wrote:
> Looking for a solution to this problem. I have Googled all over the 
> place but haven't found a definitive answer.
>
> I have a Samba Server that ONCE was on a network where there was 
> SECOND Samba Server with IP Address 192.168.20.3. Today, the FIRST 
> server is on a network with an address range 10.0.0.0/255.255.255.0 
> and it has no way of finding that SECOND Server 192.168.20.3.  
> However, /var/log/messages is full of errors that say:
>
> Nov  4 04:07:29 fileserver nmbd[5248]: [2007/11/04 04:07:29, 0] 
> libsmb/nmblib.c:send_udp(791)
> Nov  4 04:07:29 fileserver nmbd[5248]:   Packet send failed to 
> 192.168.20.3(137) ERRNO=Network is unreachable
> Nov  4 04:07:29 fileserver nmbd[5248]: [2007/11/04 04:07:29, 0] 
> nmbd/nmbd_packets.c:send_netbios_packet(163)
> Nov  4 04:07:29 fileserver nmbd[5248]:   send_netbios_packet: 
> send_packet() to IP 192.168.20.3 port 137 failed
> Nov  4 04:07:29 fileserver nmbd[5248]: [2007/11/04 04:07:29, 0] 
> nmbd/nmbd_namequery.c:query_name(245)
> Nov  4 04:07:29 fileserver nmbd[5248]:   query_name: Failed to send 
> packet trying to query name ACCOUNTING<1b>
>
> I can see that the file /var/cache/samba/wins.dat includes a reference 
> to the IP Address 192.168.20.3 (I have seen some postings suggesting 
> that wins.dat can be the cause of this error).  If I delete wins.dat 
> and restart samba, the reference to 192.168.20.3 comes back.
>
> I can state with total confidence that there are no network interfaces 
> on this machine configured to be in the 192.168.20.x range. In fact, 
> only one of 3 network interfaces is currently active and has an IP 
> Address.
>
> Is there any way that I can get this Samba Server to stop looking for 
> 192.168.20.3?
>
> -- Andy
> ________________________________________________________________________
> Email and AIM finally together. You've gotta check out free AOL Mail! 
> - http://mail.aol.com
I had a similar problem -- deleted wins.dat and forced the entry in 
smb.conf:

interfaces = eth0

restarting the service wasn't enough -- had to STOP the service(s) and 
then restart.

That fixed it.

-=R