Network host insists on retaining wrong ip address for client

[riprap1951]

Hello, All
[WinXP Pro SP2 wireless network w/ D-Link DI-624 router, auto DHCP
setup]
I realize that there're hundreds of posts on name resolution
problems; I've read thru a great many of them, trying to fix the
problem myself, before posting this. Here's the deal:
Host computer/desktop <"host"> is hard-connected to router.
Laptop unit <"laptop"> connects with adapter card.
Laptop can ping the host by ip address & computer name. No problem.
Host can ping the laptop by ip address, but not by name.
What I've already done:
1] Made double-sure that the #PRE entries in both computers'
LMHOSTS files are accurate.
2] Made sure that in the laptop's adapter's properties > TCP/IP
properties > advanced > "enable lmhosts lookup" box is checked.
3] From the host computer [the one seemingly w/ name res problem]
from the cmd-line I ran "nbtstat -r", which according to the Help is
supposed to purge existing netbios names and re-enter the ones
currently in lmhosts file. No joy.
4] Made sure that the Windows firewall on BOTH units is off &
disabled.
5] Here's where you networking experts get the big clue: In the
router's status window, the laptop's ip address shows up accurate. In
the host computer's lmhosts file the laptop's address is correct. BUT
when I run "net view" from the host-computer's cmd-line, the laptop
units name comes up BUT with the wrong ip address.
Why in the heck, after I ran nbtstat -r on host-computer, does it
insist on retaining the wrong ip address for the laptop/client? I am
thoroughly-stumped [:-|
Any help I could get on this would be greatly-appreciated. Thanks in
advance!
riprap

 

[riprap1951]

[Just riprap again]
To anyone with similar symptoms: I got it working. The idea of using
"nbtstat" was a good one, but where I went wrong [in trying to purge
existing netbios names and re-loading the ones from LMHOSTS] was in
using a lowercase "-r" after the cmd "nbtstat".
I re-read the Help, ran "nbtstate -R", and it fixed the
host-computer's name resolution problem.
Happy networking [;-)

riprap.

 

[Chuck]

Hello, All
[WinXP Pro SP2 wireless network w/ D-Link DI-624 router, auto DHCP
setup]
I realize that there're hundreds of posts on name resolution
problems; I've read thru a great many of them, trying to fix the
problem myself, before posting this. Here's the deal:
Host computer/desktop <"host"> is hard-connected to router.
Laptop unit <"laptop"> connects with adapter card.
Laptop can ping the host by ip address & computer name. No problem.
Host can ping the laptop by ip address, but not by name.
What I've already done:
1] Made double-sure that the #PRE entries in both computers'
LMHOSTS files are accurate.
2] Made sure that in the laptop's adapter's properties > TCP/IP
properties > advanced > "enable lmhosts lookup" box is checked.
3] From the host computer [the one seemingly w/ name res problem]
from the cmd-line I ran "nbtstat -r", which according to the Help is
supposed to purge existing netbios names and re-enter the ones
currently in lmhosts file. No joy.
4] Made sure that the Windows firewall on BOTH units is off &
disabled.
5] Here's where you networking experts get the big clue: In the
router's status window, the laptop's ip address shows up accurate. In
the host computer's lmhosts file the laptop's address is correct. BUT
when I run "net view" from the host-computer's cmd-line, the laptop
units name comes up BUT with the wrong ip address.
Why in the heck, after I ran nbtstat -r on host-computer, does it
insist on retaining the wrong ip address for the laptop/client? I am
thoroughly-stumped [:-|
Any help I could get on this would be greatly-appreciated. Thanks in
advance!
riprap

I would very much like to see some diagnostics here. Please provide "browstat
status" and "ipconfig /all" from each computer. Read this article, and linked
articles, and follow instructions precisely (download browstat!):
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>
http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp

Is Windows Firewall the only security program involved here?
<http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>
http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html

There is a section on name resolution under NBT, that you might find
instructive, in the NT Browser white paper - look for the section titled
"Microsoft TCP/IP and Name Resolution".
<http://www.microsoft.com/technet/archive/winntas/deploy/prodspecs/ntbrowse.mspx>
http://www.microsoft.com/technet/archive/winntas/deploy/prodspecs/ntbrowse.mspx

 

[Chuck]

[Just riprap again]
To anyone with similar symptoms: I got it working. The idea of using
"nbtstat" was a good one, but where I went wrong [in trying to purge
existing netbios names and re-loading the ones from LMHOSTS] was in
using a lowercase "-r" after the cmd "nbtstat".
I re-read the Help, ran "nbtstate -R", and it fixed the
host-computer's name resolution problem.
Happy networking [;-)

riprap.

Case sensitivity is very important in many places. Thanks for letting us know.