[Samba] samba resolves wrong wins ip address

John Russell jorussel at cisco.com
Fri Jan 2 16:46:38 GMT 2004

Hello all,
This has been making me crazy for a while, but it seems like a really
easy fix.  I just can't figure out what it is.  Any ideas would be
greatly appreciated.

I have two Linux machines existing on a mostly MS network and have samba
running well on each.  However, one machine resolves the wrong ip
address of the other machine.  Here's the setup.

Machine 1: Laptop
uses DHCP to get dynamic address
uses samba-3.0.1 (wins server = a.b.c.d) to register name/ip address
with WINS server
	so MS and samba machines on the network can resolve
	its hostname to its dynamic address.
also runs vmware in bridged networking mode (read on)

Machine 2: Server
has static ip address
uses samba-2.2.7a (wins server = a.b.c.d) to resolve hostnames of hosts
with dynamic DHCP addresses, including machine 1.   

Both machine 1 and 2 resolve hostnames of hosts running MS Windows with
DHCP perfectly.   

However, when I try to ping machine 1 from machine 2, it pings the ip
address of the vmware network interface (vmnet0) and not eth0.  Its not
important if you know what vmware is or does I think. Basically machine
2 is pinging the address of the wrong network interface for machine 1.  

However, and this is the killer, all other (MS) machines on the network
ping machine 1 with the address for eth0,  the network interface that I
want.  Everything works fine.

Only machine 2 pings the wrong network interface (vmnet0) address.  

I'm guessing that this can be fixed with a configuration setting on
machine 1 (who may not be advertising its address properly and only
samba notices the problem).  However, I'm not sure about this.  Just

Does anyone have any idea what is going on here and how I can convince
machine 2 that machine 1's address is the one from eth0?  Thanks for any

John Russell 

More information about the samba mailing list