Re: nslookup and ping disagree

[Jon Harris]

Come on guy they are USERS they don't think never have never will!  Never
let a user have Admin credentials they only play and cause you problems.

Jon

On Thu, Feb 12, 2009 at 7:38 PM, Mike Gill wrote:

> OMG.. someone will pay. Sorry, disregard. Hosts file was modified, and not
> by me. These were fresh machines from Dell and it's a small remote site so
> a
> couple people there know the admin creds. I know I didn't do it and I
> didn't
> think anyone there was capable of it. Should have looked there first.
> Crikey! What were they thiking?
>
> --
> Mike Gill
>
>
> -Original Message-
> From: Troy Meyer [mailto:troy.me...@monacocoach.com]
> Sent: Thursday, February 12, 2009 4:18 PM
> To: NT System Admin Issues
> Subject: RE: nslookup and ping disagree
>
> When nslookup (your DNS server) disagrees with ping (your local box), it
> sounds like a host file configuration somewhere.  Did you setup a static
> host entry for testing at one time and leave it on this one machine?
>
> -troy
>
>
>
>  ~ Finally, powerful endpoint security that ISN'T a resource hog! ~
> ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~
>

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

RE: nslookup and ping disagree

[Mike Gill]

OMG.. someone will pay. Sorry, disregard. Hosts file was modified, and not
by me. These were fresh machines from Dell and it's a small remote site so a
couple people there know the admin creds. I know I didn't do it and I didn't
think anyone there was capable of it. Should have looked there first.
Crikey! What were they thiking?

-- 
Mike Gill


-Original Message-
From: Troy Meyer [mailto:troy.me...@monacocoach.com] 
Sent: Thursday, February 12, 2009 4:18 PM
To: NT System Admin Issues
Subject: RE: nslookup and ping disagree

When nslookup (your DNS server) disagrees with ping (your local box), it
sounds like a host file configuration somewhere.  Did you setup a static
host entry for testing at one time and leave it on this one machine?

-troy



~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

Re: nslookup and ping disagree

[Peter van Houten]

Check your hosts file for hardcoded address?

Also check the User Configured fields (under Alternate IP address
config) for other IP address details.

Lastly, I have noticed that if an address was previously hardcoded and
then changed to use a DC's NS, it tends to keep the same address (if it
was in the same range as the NS).


-Original Message-
From: Mike Gill [mailto:lis...@canbyfoursquare.com]
Sent: Thursday, February 12, 2009 4:11 PM
To: NT System Admin Issues
Subject: nslookup and ping disagree

I have an odd problem with a Windows Vista client (2008 domain) that
can't resolve a website properly. Pinging the site from other
machines on the same network and outside of the network shows the
website at the correct address. Running nslookup on the problem
machine and any other machine on the network shows the correct
address. But pinging the site, or browsing to the website on the
problem machine shows the old address switched away from months ago.
I've tried flushing the DNS, cleaning browser caches, creating new
user profiles, etc. I've tried enabling only the DC as the name
server with no secondary, then reflushing... I can't find where the
old IP is being resolved from. When the site was first moved, we had
this problem with just the wireless clients (which this is) but it
cleared itself out in a couple days before I had a chance to really
look into it. It appears there is one machine left still that can't
get it right. ipconfig shows the same info as any other workstation
wired or wireless. Any suggestions?


~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

RE: nslookup and ping disagree

[Troy Meyer]

When nslookup (your DNS server) disagrees with ping (your local box), it sounds 
like a host file configuration somewhere.  Did you setup a static host entry 
for testing at one time and leave it on this one machine?

-troy

-Original Message-
From: Mike Gill [mailto:lis...@canbyfoursquare.com] 
Sent: Thursday, February 12, 2009 4:11 PM
To: NT System Admin Issues
Subject: nslookup and ping disagree

I have an odd problem with a Windows Vista client (2008 domain) that can't 
resolve a website properly. Pinging the site from other machines on the same 
network and outside of the network shows the website at the correct address. 
Running nslookup on the problem machine and any other machine on the network 
shows the correct address. But pinging the site, or browsing to the website on 
the problem machine shows the old address switched away from months ago. I've 
tried flushing the DNS, cleaning browser caches, creating new user profiles, 
etc. I've tried enabling only the DC as the name server with no secondary, then 
reflushing... I can't find where the old IP is being resolved from. When the 
site was first moved, we had this problem with just the wireless clients (which 
this is) but it cleared itself out in a couple days before I had a chance to 
really look into it. It appears there is one machine left still that can't get 
it right. ipconfig shows the same info as any other workstation wired or 
wireless. Any suggestions?

 

-- 
Mike Gill

 


 

 


~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

RE: nslookup and ping disagree

[Ken Schaefer]

HOSTS file?
Proxy configuration?

Cheers
Ken

From: Mike Gill [mailto:lis...@canbyfoursquare.com]
Sent: Friday, 13 February 2009 11:11 AM
To: NT System Admin Issues
Subject: nslookup and ping disagree

I have an odd problem with a Windows Vista client (2008 domain) that can't 
resolve a website properly. Pinging the site from other machines on the same 
network and outside of the network shows the website at the correct address. 
Running nslookup on the problem machine and any other machine on the network 
shows the correct address. But pinging the site, or browsing to the website on 
the problem machine shows the old address switched away from months ago. I've 
tried flushing the DNS, cleaning browser caches, creating new user profiles, 
etc. I've tried enabling only the DC as the name server with no secondary, then 
reflushing... I can't find where the old IP is being resolved from. When the 
site was first moved, we had this problem with just the wireless clients (which 
this is) but it cleared itself out in a couple days before I had a chance to 
really look into it. It appears there is one machine left still that can't get 
it right. ipconfig shows the same info as any other workstation wired or 
wireless. Any suggestions?

--
Mike Gill







~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~