ping keeps using old IP address of another computer

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have de-sabled and then re-enabled a NIC on one of the w2k which resulted
in this NIC getting a new IP address from the router. I changed the address
in the lmhosts (I have usage lmhosts enabled) on the other computer, but it
still uses the old IP when pinging.

Where do I control that from?
 
<aa> wrote:
: I have de-sabled and then re-enabled a NIC on one of the w2k which
resulted
: in this NIC getting a new IP address from the router. I changed the
address
: in the lmhosts (I have usage lmhosts enabled) on the other computer, but
it
: still uses the old IP when pinging.
:
: Where do I control that from?

Where does the workstation point to for DNS?
Do you also have a HOSTS file?

--
Roland Hall
/* This information is distributed in the hope that it will be useful, but
without any warranty; without even the implied warranty of merchantability
or fitness for a particular purpose. */
Online Support for IT Professionals -
http://support.microsoft.com/servicedesks/technet/default.asp?fr=0&sd=tech
How-to: Windows 2000 DNS:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;308201
 
1. Where does the workstation point to for DNS?

I do not understand the question. If you mean TCP/IP settings, then it is
set to obtain the DNS server address automatically.

2. Yes I do have hosts file in the same folder as lmhosts
 
<aa> wrote:
: 1. Where does the workstation point to for DNS?
:
: I do not understand the question. If you mean TCP/IP settings, then it is
: set to obtain the DNS server address automatically.
:
: 2. Yes I do have hosts file in the same folder as lmhosts

Sorry, I have a few projects going on and a dog with health issues.

Yes, TCP/IP settings. If obtains automatically, but where does the DNS
point to? What is the Primary DNS?
Is there anything in the HOSTS file other than 127.0.0.1?

--
Roland Hall
/* This information is distributed in the hope that it will be useful, but
without any warranty; without even the implied warranty of merchantability
or fitness for a particular purpose. */
Online Support for IT Professionals -
http://support.microsoft.com/servicedesks/technet/default.asp?fr=0&sd=tech
How-to: Windows 2000 DNS:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;308201
 
Thanks, Roland. I hope your dog is better now.

1. Yes, there was the old address in hosts, I corrected it and it is OK now.
However I do not understand why hosts overrules lmhosts while my TCP/IP is
set to use lmhosts ?

2. How shall I determine, where does the DNS point to?
 
<aa> wrote:
: Thanks, Roland. I hope your dog is better now.

Thank you. She was diagnosed with diabetes mullitis, so it is a life long
illness. She is doing better and we hope to have her around a lot longer.

: 1. Yes, there was the old address in hosts, I corrected it and it is OK
now.
: However I do not understand why hosts overrules lmhosts while my TCP/IP is
: set to use lmhosts ?

Has correcting it made a difference with your issue?
HOSTS doesn't overrule LMHOSTS. HOSTS is TCP/IP. LMHOSTS is NetBIOS.

: 2. How shall I determine, where does the DNS point to?

ipconfig /all

--
Roland Hall
/* This information is distributed in the hope that it will be useful, but
without any warranty; without even the implied warranty of merchantability
or fitness for a particular purpose. */
Online Support for IT Professionals -
http://support.microsoft.com/servicedesks/technet/default.asp?fr=0&sd=tech
How-to: Windows 2000 DNS:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;308201
 
Roland,
1. She was diagnosed with diabetes mullitis, so it is a life long

So let her have a long life.

2. Has correcting it made a difference with your issue?
Yes, it sorted it out

3. HOSTS doesn't overrule LMHOSTS. HOSTS is TCP/IP. LMHOSTS is NetBIOS

Are you sure? The might be TCP/IP and NetBIOS respectively, but here we are
talking about mapping NetBIOS names to TCP/IP.
Both files seem to contain the TCP/IP - NetBIOS names pairs.
In HOSTS, among other things I had
192.168.1.11 Desktop (which is the NetBIOS computer name)
And ping Desktop was pinging 192.168.1.11 which was, as I said, re-assigned
to another computer (actually to the computer from wich I was ponging
Desktop, i.e. that other computer was pinging itself)
When I changed .11 to .13 (which became the new IP address of Desktop after
I disabled and re-enabled the NIC) in HOSTS everything became normal.

4. ipconfig /all returns two DNS addresses:
192.168.1.11 - which is the rouiter
194.98.0.1 - God knows where this one came from. Perhaps from my ISP (the
router is also a ADSL modem and is connected to Internet). If it comes from
my computer settings, where should I look for it (ming I have DNS server
obtain automatically)?
 
<aa> wrote:
: Roland,
: 1. She was diagnosed with diabetes mullitis, so it is a life long
:
: So let her have a long life.

We give her a shot every morning, have adjusted her diet and have changed
our schedules, so she can live as long as possible.
http://www.scripting.com/davenet/stories/Thingsyoucanlearnfromadog.html

: 2. Has correcting it made a difference with your issue?
: Yes, it sorted it out

Great!

: 3. HOSTS doesn't overrule LMHOSTS. HOSTS is TCP/IP. LMHOSTS is NetBIOS
:
: Are you sure? The might be TCP/IP and NetBIOS respectively, but here we
are
: talking about mapping NetBIOS names to TCP/IP.
: Both files seem to contain the TCP/IP - NetBIOS names pairs.
: In HOSTS, among other things I had
: 192.168.1.11 Desktop (which is the NetBIOS computer name)
: And ping Desktop was pinging 192.168.1.11 which was, as I said,
re-assigned
: to another computer (actually to the computer from wich I was ponging
: Desktop, i.e. that other computer was pinging itself)
: When I changed .11 to .13 (which became the new IP address of Desktop
after
: I disabled and re-enabled the NIC) in HOSTS everything became normal.

Yes. Ping is not a NetBIOS utility. It is a TCP/IP utility.

You should have:
ipaddress FQDN

Ex.
130.57.4.70 novell.com

However:
130.57.4.70 novell

....will work.

To test:
ping novell

This is the response you get:
Ping request could not find host novell. Please check the name and try
again.

Why? Novell is an unknown and it is NOT a computer listed on this subnet.

Now add:
130.57.4.70 novell

....to your hosts file.

ping novell

This is the response you get:
Pinging novell [130.57.4.70] with 32 bytes of data:

Reply from 130.57.4.70: bytes=32 time=58ms TTL=45

If you then execute IE and put novell in the address bar, it will take you
to the novell.com site but in the address bar you will see:
http://novell/

not... http://novell.com/

Why? Because your computer found an entry in the HOSTS file, which it
checks first prior to making a DNS request.
Can you still put in novell.com to get there?
Sure. This time it will convert to http://www.novell.com/

Now, let's change the novell entry, in the HOSTS file, to:

127.0.0.1 novell.com

ping novell

The response you get is:
Ping request could not find host novell. Please check the name and try
again.

ping novell.com

The response you get is:
Pinging novell.com [127.0.0.1] with 32 bytes of data:

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

Can I now not get to novell.com?
Sure. You can always use www.novell.com because you are not blocking it and
there is a DNS entry for www.

If you're not running NetBIOS, and you do not have a HOSTS entry with a
single name, then you cannot ping it because TCP/IP requires a DNS entry to
resolve the name when a HOSTS entry does not exist. NetBIOS will allow you
to return a NetBIOS name if NetBIOS over TCP/IP is enabled.

So, what else did you learn here? If you want to block sites, you can put
them in your HOSTS file and point them to yourself. How is this helpful?
What if you put in your localhost address and the domain of an ad server?
You eliminate ad servers from being able to track you with embedded images
in email, store cookies on your computer, etc. You will still get the
relevant part of the email message but you they won't know it. However,
accepting text only messages does the same thing without all the extra work.

: 4. ipconfig /all returns two DNS addresses:
: 192.168.1.11 - which is the rouiter
: 194.98.0.1 - God knows where this one came from. Perhaps from my ISP (the
: router is also a ADSL modem and is connected to Internet). If it comes
from
: my computer settings, where should I look for it (ming I have DNS server
: obtain automatically)?

If your router is assigning IP addresses to client via DHCP, it may also be
passing DNS information. If you have Active Directory running on a server,
then you want the server to provide DHCP and DNS and not point to any ISP
DNS servers. If you only have clients (peer-peer) network, then using the
ISPs servers in this manner is what you want.

Don't forget to remove the novell entry from your HOSTS file. (O:=

HTH...

--
Roland Hall
/* This information is distributed in the hope that it will be useful, but
without any warranty; without even the implied warranty of merchantability
or fitness for a particular purpose. */
Online Support for IT Professionals -
http://support.microsoft.com/servicedesks/technet/default.asp?fr=0&sd=tech
How-to: Windows 2000 DNS:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;308201
 
There is an error in my last post:
novell.com is not an FQDN.
An example of an FQDN is actually www.novell.com. (with the ending period)
....but this is not required in your HOSTS file, at least not on MSFT
networks.

--
Roland Hall
/* This information is distributed in the hope that it will be useful, but
without any warranty; without even the implied warranty of merchantability
or fitness for a particular purpose. */
Online Support for IT Professionals -
http://support.microsoft.com/servicedesks/technet/default.asp?fr=0&sd=tech
How-to: Windows 2000 DNS:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;308201
 
Thanks, Roland a very comprehensive explanation.
I need a bit of time to digest it and experiment.
Thanks.
 
Back
Top