Some URLs not resolving

  • Thread starter Thread starter Chris May
  • Start date Start date
C

Chris May

This is evidently not an IE problem since Mozilla is affected as well. I don't
know whether XP is responsible, but perhaps somebody will be familiar with this
problem and know where the fault may be.

Some URLs will often not resolve when I try to reach them with either IE or
Mozilla. For instance, I am often unable to get www.newegg.com, although I can
reach the site immediately by inputting 204.14.213.185. When I open the Command
window and run a tracert on www.newegg.com, it immediately resolves to
204.14.213.185. But what could be keeping my Internet browsers from failing
rather often to get that and some other sites resolved?

Since running tracerts on the balky URLs works, it seems the problem must be
somewhere in XP rather than with my ISP. But what could be causing it? Any
ideas?

I'm running XP Home SP2. It's current with updates. My Internet connection is
highspeed cable.

Thanks for any help.
ChrisM
 
Sounds like a DNS problem since the friendly name doesnt sound like it is
binding to the ip. First step would be to clear the DNS cache.
In a cmd prompt type in ipconfig /flushdns and hit enter.
Also, if your running IE6 on XP SP2 try the following in a cmd prompt.
iexplore.exe /rereg and hit enter.

It should just hourglass and go away withiin seconds.

Try the sites.


If that fails try manually binding an ip to a freindly name by using the
hosts file.

Go to c:\windows\system32\drivers\etc and open up the hosts file with notepad.

Find this entry " 127.0.0.1 localhost "

Directly below it type in the ip address of a faulting site and then the
friendly name.

Example:

127.0.0.1 localhost
72.14.207.104 www.google.com

Then save and try the site.
 
| Instead of running a tracert, try ping:
| ping newegg.com
| ping 204.14.213.185
|
| What are the results?

Pinging works fine:

C:\>ping www.newegg.com

Pinging www.newegg.com [204.14.213.185] with 32 bytes of data:

Reply from 204.14.213.185: bytes=32 time=36ms TTL=239
Reply from 204.14.213.185: bytes=32 time=36ms TTL=239
Reply from 204.14.213.185: bytes=32 time=36ms TTL=239
Reply from 204.14.213.185: bytes=32 time=35ms TTL=239

Ping statistics for 204.14.213.185:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 35ms, Maximum = 36ms, Average = 35ms

Doesn't look like any problem there.

ChrisM
 
| Sounds like a DNS problem since the friendly name doesnt sound like it is
| binding to the ip. First step would be to clear the DNS cache.
| In a cmd prompt type in ipconfig /flushdns and hit enter.
| Also, if your running IE6 on XP SP2 try the following in a cmd prompt.
| iexplore.exe /rereg and hit enter.

I had already cleared the DNS cache, which didn't solve the problem. After
running "rereg," however, everything seems to be working again even with
Mozilla. It's a little puzzling how something in IE could be affecting another
browser, but I'll just accept it if that's the cure.

Thanks very much for your help.

ChrisM
 
Chris said:
This is evidently not an IE problem since Mozilla is affected as
well. I don't know whether XP is responsible, but perhaps somebody
will be familiar with this problem and know where the fault may be.

Some URLs will often not resolve when I try to reach them with either
IE or Mozilla. For instance, I am often unable to get
www.newegg.com, although I can reach the site immediately by
inputting 204.14.213.185. When I open the Command window and run a
tracert on www.newegg.com, it immediately resolves to 204.14.213.185.
But what could be keeping my Internet browsers from failing rather
often to get that and some other sites resolved?

Since running tracerts on the balky URLs works, it seems the problem
must be somewhere in XP rather than with my ISP. But what could be
causing it? Any ideas?

I'm running XP Home SP2. It's current with updates. My Internet
connection is highspeed cable.

Thanks for any help.
ChrisM
Click to expand...

Shot in the dark: Some viruses disable access to some sites (so you can't
clean out the malware). This might prove a fruitful line of inquiry.
 
| Shot in the dark: Some viruses disable access to some sites (so you can't
| clean out the malware). This might prove a fruitful line of inquiry.

Thanks, but I doubt that's the case this time since problem sites have been
connecting occasionally. Anyway, it appears things may be resolved now.

ChrisM
 
Back
Top