Skip to main content

Incorrect IP address is returned when you ping a server by using its NetBIOS name

I was pinging from Windows 2012 R2 machine to a Windows 2016. Both are multi-homed boxes, Windows 2012 R2 have 3 NIC cards, Windows 2016 got 4. 

Windows will try to figure out the best interface to use by determining the quality of network connection - which eventually shows up as the metrics of the interface. The lower the metric number the higher the order of preference. 

In one case, I had 2 network interfaces on flat network (no routing) and one interface that is routed but has the lowest metric. The issue was that that one network thinks it has the IP of the given NetBIOS name but was actually pointing to wrong IP, it seems like one of the routers have cached the IP incorrectly. Tracing where it was cached is not easy specially so if you don't have control of the network. 

Anyway, since the box actually have 3 direct connections to the other unit and it refuses to use the other network interfaces, the best option was to modify hosts file (C:\Windows\System32\drivers\etc\hosts) and hard code the IP to Name. There are multiple downsides to this one, dynamic IP assignment means it will eventually stop working in the future and if this link goes down then it will not use the other interfaces.

Reference(s):

https://support.microsoft.com/en-us/help/981953/an-incorrect-ip-address-is-returned-when-you-ping-a-server-by-using-it

 

Comments

Popular posts from this blog

Error! Could not locate dkms.conf file install VirtualBox 4.1.8 on Ubuntu 11.10

Tried to update my Ubuntu host today and it did pickup that new version of VirtualBox is available (4.1.8). All other packages installed properly except that VirtualBox installation was complaining about missing dkms.conf file, see error message below. $: sudo /etc/init.d/vboxdrv setup * Stopping VirtualBox kernel modules [ OK ] * Uninstalling old VirtualBox DKMS kernel modules Error! Could not locate dkms.conf file. File: does not exist. [ OK ] * Trying to register the VirtualBox kernel modules using DKMS [ OK ] * Starting VirtualBox kernel modules [ OK ] Though it looks like installation was fine but I am concerned about its effects to VirtualBox functionality. To fix this, do: $: cd /var/lib/dkms/vboxhost $: sudo rm -r 4.1.4 $: sudo /etc/init.d/vboxdrv setup Of course you have to re

The following add-ins could not be started MonoDevelop.GnomePlatform

Installing MonoDevelop in OpenSUSE 12.2 from its repository was very easy. When running it for the first time though I got the message: The following add-ins could not be started: The root of the trace shows MonoDevelop.GnomePlatform,2.8 A quick search shows that MonoDevelop depends on libgnomeui . This should have been part of dependencies when installing the application but well.... Below is the screen shot of the error message. References: http://software.1713.n2.nabble.com/MonoDevelop-and-openSUSE-12-1-td7462957.html [2013/04/09] - Same issue observed in OpenSUSE 12.3 and also the same fix. [2014/11/02] - Same issue observed in OpenSUSE 13.3, mondevelop 3.0.6 and the same fix.