Old IP stuck somewhere?

Greetings

I am trying to reach a web site who recently changed their IP, and now I
cannot reach the site. While I can ping the new IP, I cannot browse to it. It
does not appear to be a hashed winsock - I have no problems reaching any
other site - it's this one site only that seems to have gotten stuck
somewhere with the old IP. Is there a local table on the PC where URL's and
IP's are associated?

Any ideas? I have viewed the other posts where the symptoms seem similar,
but again it's only 1 site that I can no longer reach. Here's the rub - I
have another box, a Win2K machine on dial-up, that see's the new site
perfectly ok.

The machine I'm using is WinXP Pro SP2, IE6 SP2, 1gig ram, 1.7 gHz - TIA for
any help afforded.

MisterWeather

MisterWeather wrote:
Greetings

I am trying to reach a web site who recently changed their IP, and
now I cannot reach the site. While I can ping the new IP, I cannot
browse to it. It does not appear to be a hashed winsock - I have no
problems reaching any other site - it's this one site only that seems
to have gotten stuck somewhere with the old IP. Is there a local
table on the PC where URL's and IP's are associated?

Any ideas? I have viewed the other posts where the symptoms seem
similar, but again it's only 1 site that I can no longer reach.
Here's the rub - I have another box, a Win2K machine on dial-up, that
see's the new site perfectly ok.

The machine I'm using is WinXP Pro SP2, IE6 SP2, 1gig ram, 1.7 gHz -
TIA for any help afforded.

MisterWeather

ipconfig /displaydns

But if they changed their IP, and didn't adjust their DNS accordingly, why
do you think the old IP would help? You aren't hosting your own public DNS
in house, are you? If you can't reach their website by IP (http://ipaddress)
it's not your problem, it's theirs, right?

On Tue, 30 Nov 2004 19:15:02 -0800, "MisterWeather"
wrote:

Greetings

I am trying to reach a web site who recently changed their IP, and now I
cannot reach the site. While I can ping the new IP, I cannot browse to it. It
does not appear to be a hashed winsock - I have no problems reaching any
other site - it's this one site only that seems to have gotten stuck
somewhere with the old IP. Is there a local table on the PC where URL's and
IP's are associated?

Any ideas? I have viewed the other posts where the symptoms seem similar,
but again it's only 1 site that I can no longer reach. Here's the rub - I
have another box, a Win2K machine on dial-up, that see's the new site
perfectly ok.

The machine I'm using is WinXP Pro SP2, IE6 SP2, 1gig ram, 1.7 gHz - TIA for
any help afforded.

MisterWeather

Can you ping the site by name, and by ip address, successfully? If so, I'd
doubt that the problem is your dns cache.

But try "ipconfig /flushdns" if you wish.

--
Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.

Greetings and - DOH!

I hate to admit such a basic error on my part, but the problem was so basic
I did not think to start at the beginning. The host file was pointing to the
old IP; as soon as I renamed the host file and rebooted, viola! It worked
just fine. Perhaps this is an issue in some of the other posts if they are
having similar problems?

Thanks again for the response.

MisterWeather

"Lanwench [MVP - Exchange]" wrote:

MisterWeather wrote:
Greetings

I am trying to reach a web site who recently changed their IP, and
now I cannot reach the site. While I can ping the new IP, I cannot
browse to it. It does not appear to be a hashed winsock - I have no
problems reaching any other site - it's this one site only that seems
to have gotten stuck somewhere with the old IP. Is there a local
table on the PC where URL's and IP's are associated?

Any ideas? I have viewed the other posts where the symptoms seem
similar, but again it's only 1 site that I can no longer reach.
Here's the rub - I have another box, a Win2K machine on dial-up, that
see's the new site perfectly ok.

The machine I'm using is WinXP Pro SP2, IE6 SP2, 1gig ram, 1.7 gHz -
TIA for any help afforded.

MisterWeather

ipconfig /displaydns

But if they changed their IP, and didn't adjust their DNS accordingly, why
do you think the old IP would help? You aren't hosting your own public DNS
in house, are you? If you can't reach their website by IP (http://ipaddress)
it's not your problem, it's theirs, right?

MisterWeather wrote:
Greetings and - DOH!

I hate to admit such a basic error on my part, but the problem was so
basic I did not think to start at the beginning. The host file was
pointing to the old IP; as soon as I renamed the host file and
rebooted, viola! It worked just fine.

That's great. We'll just pretend you never posted anything about this
problem. ;-)

Perhaps this is an issue in
some of the other posts if they are having similar problems?

Entirely possible, but the troubleshooting process usually involves asking
about hosts, which I would've done if you continued to have problems....you
said you could ping the new IP and couldn't browse to it - I presumed "it"
meant the IP....not the hostname

Thanks again for the response.

MisterWeather

"Lanwench [MVP - Exchange]" wrote:

MisterWeather wrote:
Greetings

I am trying to reach a web site who recently changed their IP, and
now I cannot reach the site. While I can ping the new IP, I cannot
browse to it. It does not appear to be a hashed winsock - I have no
problems reaching any other site - it's this one site only that
seems to have gotten stuck somewhere with the old IP. Is there a
local table on the PC where URL's and IP's are associated?

Any ideas? I have viewed the other posts where the symptoms seem
similar, but again it's only 1 site that I can no longer reach.
Here's the rub - I have another box, a Win2K machine on dial-up,
that see's the new site perfectly ok.

The machine I'm using is WinXP Pro SP2, IE6 SP2, 1gig ram, 1.7 gHz -
TIA for any help afforded.

MisterWeather

ipconfig /displaydns

But if they changed their IP, and didn't adjust their DNS
accordingly, why do you think the old IP would help? You aren't
hosting your own public DNS in house, are you? If you can't reach
their website by IP (http://ipaddress) it's not your problem, it's
theirs, right?