• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2361
  • Last Modified:

ping of netbios name does not resolve to correct IP address

Old Windows NT domain
Windows XP Pro workstation

I have a client that was trying to add an ODBC source on their XP Pro PC.  Whenever the tried to connect it failed.  I noticed that they were trying to connect to a standalone server that is on this network.  The server name is ERP1.  It has an internal IP Address of 192.168.1.6.

When I ping that server's netbios name (erp1), it resolves to an IP address that is not on our private network.  The ping goes on the internet and finally resolves to a 65.x.x.x address, which is our service provider.  I assume, for some reason the IP Address for ERP1 can NO T be found internally, so it is trying to resolve it elswhere.

I'm a little rusty on NT server configuration, so I tried some things on the XP Pro computer.

I added a line to an LMHOSTS file I created.
192.168.1.6 ERP1 #PRE

This seemd to solve the problem on one computer but the next day it did NOT work again.  This did NOT solve the problem on the original user's PC.

I also tried adding, in TCP/IP settings/advanced, the WINS server address.  Unfortunately, this did not help either.

Any suggestion would be appreciated.
0
yeller
Asked:
yeller
  • 4
  • 3
1 Solution
 
eulacCommented:
try adding the line
   192.168.1.6 ERP1
in the winxp client
    c:\WINDOWS\system32\drivers\etc\hosts
0
 
Rob WilliamsCommented:
Do you have an internal DNS server? If so add its IP to the network adapter as the first DNS server rather than the ISP's DNS. If this is a 2000/2003 domain (you mentioned NT) you should only use your DNS server, and the ISP only added as a Forwarder in the server's DNS.

LMHosts is usually used for NetBIOS names as you have done. Hosts is usually for DNS names. Odd that it would loose that, unless you have antispyware that is overwriting the LMhosts and Hosts files.
0
 
yellerAuthor Commented:
eulac,  I don't think adding the line
   192.168.1.6 ERP1
in the winxp client
    c:\WINDOWS\system32\drivers\etc\hosts
will help.  Hosts is usually for DNS names.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
yellerAuthor Commented:
RobWill,

I do use Spybot, but it did NOT overwrite my LMHosts file.  It still contains:  192.168.1.6 ERP1 #PRE.
0
 
Rob WilliamsCommented:
From an earlier post of mine:
To check your LMHosts file entries are accepted at a command prompt enter
  nbtstat  -R
which will purge and reload the local name cache
then enter
  nbtstat  -c
to display the current name cache which should include your LMHosts file entries.
Note; the nbtstat "switches" R & c are case sensitive.
The names will only show up if you used the 'PRE' option, or if not, if you have used the name with a ping or similar command enabling them to be cached

There are a few oddities with the file, have a look at the following:
-Lmhosts file is useful for NetBIOS name resolution where other solutions are not available.
-LMHosts is located in the Windows directory under c:\Windows (or WINNT)\System32\Drivers\Etc\LMHosts.sam , instructions are included within the file. Any line starting with # is just a comment and is ignored. Open the file with Notepad and add entries for your computers as below;
192.168.0.101      CompName       #PRE
-Hit enter when each line is complete (important), then save the file without a file extension. To be sure there is no extension ,when saving enclose in quotations like "LMHosts".
-PRE has to be capitalized, however you do not need it, though should give you faster resolution where it is "pre-loaded"
-use a Tab between entries in a line rather than spaces (recommended but not necessary)
-if adding the domain and or domain controller the # of spaces used is even critical. See:
http://support.microsoft.com/kb/q180094/

0
 
yellerAuthor Commented:
RobWill,  I ran your commands.  Here are the results of nbtstat -c

Local Area Connection 2:
Node IpAddress: [192.168.1.101] Scope Id: []

                  NetBIOS Remote Cache Name Table

        Name              Type       Host Address    Life [sec]
    ------------------------------------------------------------
    DB02           <00>  UNIQUE          192.168.1.2         2
    ERP1           <03>  UNIQUE          192.168.1.6         -1
    ERP1           <00>  UNIQUE          192.168.1.6         -1
    ERP1           <20>  UNIQUE          192.168.1.6         -1
    SDP            <1C>  GROUP           192.168.1.2         600

I can see ERP1 but when I ping it it still resolves to a 65.x.x.x.
Any ideas?
0
 
Rob WilliamsCommented:
Very interesting.
What does the following show:
   ipconfig /displaydns
If it shows anything related to ERP1 run:
   ipconfig /flushdns

Do you have an internal DNS server?
Is this a domain?
Name resolution sequence of methods varies with the network configuration but the host and lmhost files usually precede DNS.
If it is a domain try adding the FQDN to the Hosts file as well such as:
192.168.1.6  ERP1.MyDomain.local

You can also add the domain to the LMHosts file:
10.0.0.1   PDCNAME #PRE #DOM:DOMAIN_NAME
 10.0.0.1   "DOMAIN_NAME    \0x1b"   #PRE
See: http://support.microsoft.com/kb/314108/EN-US/
Read carefully the notes about spacing.
0
 
Rob WilliamsCommented:
Thanks yeller. I hope you were able to get it sorted.
Cheers !
--Rob
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now