Local (LAN) Hostname IP lookup problems

Stereodude

Not really a
Joined
Jan 22, 2002
Messages
10,865
Location
Michigan
I swapped out my router yesterday for a different one and now my fileserver's hostname reports the wrong IPv4 address to other systems on the LAN. The server has a static IPv4 address. Rebooting the router yesterday fixed the issue for some number of hours, but now it's back.

I'm guessing it's some sort of master browser issue, but I'm not sure. The net view command fails to complete successfully on several of the systems on the LAN. It does complete on the server, but running the code found here:
Code:
for /f "delims=\= " %C in ('net view ^| find "\\"') do @echo -Checking %C && @nbtstat -a %C | find "MSBROWSE"
did not report back the master browser (per the script).

I'm sort of stuck... Some tests from another PC on the LAN:

Attempt to ping it IPv4:
Code:
C:\Windows\System32>ping filez -4

Pinging filez [198.105.254.228] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.


Attempt to ping it IPv6:
Code:
C:\Windows\System32>ping filez -6

Pinging Filez [fe80::d1a5:bfe0:bb68:f62d%18] with 32 bytes of data:
Reply from fe80::d1a5:bfe0:bb68:f62d%18: time<1ms
Reply from fe80::d1a5:bfe0:bb68:f62d%18: time=1ms
Reply from fe80::d1a5:bfe0:bb68:f62d%18: time=1ms
Reply from fe80::d1a5:bfe0:bb68:f62d%18: time=1ms

Ping statistics for fe80::d1a5:bfe0:bb68:f62d%18:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 1ms, Average = 0ms

nbtstat can't find it:
Code:
C:\Windows\System32>nbtstat.exe -a filez

Ethernet:
Node IpAddress: [192.168.1.126] Scope Id: []

    Host not found.

using nbtstat with the IP of the system returns this: (mac address removed by me)
Code:
C:\Windows\System32>nbtstat -A 192.168.1.151

Ethernet:
Node IpAddress: [192.168.1.126] Scope Id: []

           NetBIOS Remote Machine Name Table

       Name               Type         Status
    ---------------------------------------------
    FILEZ          <20>  UNIQUE      Registered
    FILEZ          <00>  UNIQUE      Registered
    GROUPIES       <00>  GROUP       Registered
    GROUPIES       <1E>  GROUP       Registered
    GROUPIES       <1D>  UNIQUE      Registered
    ☺☻__MSBROWSE__☻<01>  GROUP       Registered

    MAC Address = xx-xx-xx-xx-xx-xx
AFAIK, the last line in the table means it is the master browser.

The hostname does not resolve via nslookup.
Code:
> filez
Server:  router.asus.com
Address:  192.168.1.1

*** router.asus.com can't find filez: Non-existent domain

However, other local network hostnames do. Like:
Code:
> HP_840_G1
Server:  router.asus.com
Address:  192.168.1.1

Name:    HP_840_G1.stereodude.net
Address:  192.168.1.129

So, how can I determine where the IP of 198.105.254.228 for filez is coming from? It appears the system is the master browser, but why would it misreport it's own IP (presuming that was the source of the incorrect IP)?


As a test temporary workaround I set the server to DHCP from a static IP and set the router to always assign it the same IP it had before. That seems to be working (for now?). With this workaround it will ping (only via IPv4, IPv6 can't find the hostname) and pass a nslookup for it. I can see after this change it no longer reports itself as the master browser (using nbtstat -A 192.168.1.151). I also see the router reports itself as the master browser. However, I'm not sure if the router reported it was the master browser before as well also (I didn't check). The server only has one BROWSER related message in the event log which occurred right after I set it to DHCP.
Code:
The browser has forced an election on network \Device\NetBT_Tcpip_{67707D4A-9EA7-4076-8BDC-94C27581BE02} because a master browser was stopped.
 
Top