Re: Ping always resolves to a specific ip, but nslookup resolves properly
From: Pegasus \(MVP\) (I.can_at_fly.com)
Date: 02/10/04
- Next message: William Stacey [MVP]: "Re: Ping always resolves to a specific ip, but nslookup resolves properly"
- Previous message: Henrik: "Ping always resolves to a specific ip, but nslookup resolves properly"
- In reply to: Henrik: "Ping always resolves to a specific ip, but nslookup resolves properly"
- Next in thread: William Stacey [MVP]: "Re: Ping always resolves to a specific ip, but nslookup resolves properly"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 10 Feb 2004 12:42:18 +1100
Check your hosts file (c:\winnt\system32\drivers\etc\hosts).
"Henrik" <anonymous@discussions.microsoft.com> wrote in message
news:dad901c3ef76$51626c50$a601280a@phx.gbl...
> On a specific system running Windows 2000 Professional,
> running ping on a specific hostname in our network returns
> an ip number "199.85.4.55" and reroutes to a web site
> pool.com.
>
> When I use nslookup to resolve the hostname, it returns
> the correct ip number. Ping always points to the wrong ip
> number. I looked into the hosts file and the lmhosts file.
>
> Are there any other files that ping uses to resolve
> hostnames?
>
> I would appreciate any assistance. Thank you.
- Next message: William Stacey [MVP]: "Re: Ping always resolves to a specific ip, but nslookup resolves properly"
- Previous message: Henrik: "Ping always resolves to a specific ip, but nslookup resolves properly"
- In reply to: Henrik: "Ping always resolves to a specific ip, but nslookup resolves properly"
- Next in thread: William Stacey [MVP]: "Re: Ping always resolves to a specific ip, but nslookup resolves properly"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
