Can't Ping When Name Resolved using lmhosts File

[Brian Whiting]

I have a simple home network with two computers and a Tivo. They are
connected via a Vonage capable router to the internet. The two computers
are running XP and 2kPro respectively. The 2000 machine is the server with
the drive shares. Both machines are in the same workgroup, WNS, and are on
the 192.168.15.0/24 subnet. The XP client address is 192.168.15.4 and the
2000 Pro machine with the file shares is 192.168.15.55. I am unable to map
a drive from the XP client to the 2kPro server shares. I get a network path
not found error. I have the following entry in my lmhosts file on the XP
client: 192.168.15.55 microadd #PRE. I have done nbtstat -R and
nbtstat -c with the results below:
C:\WINDOWS\system32\drivers\etc>nbtstat -c

Local Area Connection:
Node IpAddress: [192.168.15.4] Scope Id: []

NetBIOS Remote Cache Name Table

Name Type Host Address Life [sec]
------------------------------------------------------------
MICROADD <03> UNIQUE 192.168.0.55 -1
MICROADD <00> UNIQUE 192.168.0.55 -1
MICROADD <20> UNIQUE 192.168.0.55 -1

C:\WINDOWS\system32\drivers\etc>
I cannot ping the microadd system by name even though it seems to resolve
correctly:
C:\WINDOWS\system32\drivers\etc>ping microadd

Pinging microadd [192.168.0.55] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.0.55:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\WINDOWS\system32\drivers\etc>

It will ping just fine by ip address but not resolve a name with -a:
C:\WINDOWS\system32\drivers\etc>ping -a 192.168.15.55

Pinging 192.168.15.55 with 32 bytes of data:

Reply from 192.168.15.55: bytes=32 time<1ms TTL=128
Reply from 192.168.15.55: bytes=32 time<1ms TTL=128
Reply from 192.168.15.55: bytes=32 time<1ms TTL=128
Reply from 192.168.15.55: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.15.55:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

If I add the record to the hosts file, it pings correctly. Wireshark is not
revealing any particular clues as to why the lmhosts resoved pings do not
work. There are no ip address conflicts on the tiny network.

 

[Andrei Ungureanu [MVP]]

There4 is a small difference between the ping by hostname and ping by
ipaddr:

<Pinging microadd [192.168.0.55] >

192.168.0.55 which is different than 192.168.15.55

--
Regards,
Andrei Ungureanu
www.eventid.net
Test our new EventReader!
http://www.altairtech.ca/eventreader/default2.asp?ref=au

 

[BW]

There4 is a small difference between the ping by hostname and ping by
ipaddr:

<Pinging microadd [192.168.0.55] >

192.168.0.55 which is different than 192.168.15.55

Thank you. I guess I've stared at it too long & that one got by me. I knew
it had to be something simple.

 

[Andrei Ungureanu [MVP]]

You're welcome!

PS: I remember that in the past (when I was working for Oracle) I had a
support call from NASA with a similar issue. So even NASA guys can make this
mistake.
--
Regards,
Andrei Ungureanu
www.eventid.net
Test our new EventReader!
http://www.altairtech.ca/eventreader/default2.asp?ref=au

There4 is a small difference between the ping by hostname and ping by
ipaddr:

<Pinging microadd [192.168.0.55] >

192.168.0.55 which is different than 192.168.15.55

Thank you. I guess I've stared at it too long & that one got by me. I
knew
it had to be something simple.