Can't access some websites...Update: Resolved...

[MaxDSP]

I can access site like AT forums, fark, slickdeals.net but cant go to americanexpress.com, newegg.com, gottadeal.com. I get Page cannot be displayed errors. Ive already cleared temp files, cookies, history, restarted pc, flushed dns, etc. Ive also tried to access the sites with IE6 and Firefox but same issue.

Could it be an issue Comcast side?

Here's a tracert I ran on Google if that helps:

Tracing route to www.google.akadns.net [216.239.57.147]
over a maximum of 30 hops:

Tracing route to www.google.akadns.net [216.239.57.147]
over a maximum of 30 hops:

1 <10 ms <10 ms <10 ms 192.168.0.1
2 * * * Request timed out.
3 16 ms 16 ms <10 ms 68.87.227.33
4 16 ms 15 ms <10 ms 68.87.229.165
5 15 ms <10 ms 16 ms 68.87.229.161
6 15 ms <10 ms 16 ms 12.118.76.5
7 15 ms <10 ms 16 ms 12.123.6.82
8 15 ms <10 ms 16 ms 12.123.6.65
9 15 ms <10 ms 16 ms 209.0.227.77
10 * 16 ms 16 ms 209.244.8.9
11 63 ms 62 ms 47 ms 64.159.0.242
12 62 ms 63 ms 62 ms 4.68.123.106
13 63 ms 62 ms 63 ms 209.247.202.218
14 62 ms 47 ms 47 ms 216.239.47.194
15 47 ms 46 ms 63 ms 216.239.49.93
16 63 ms 62 ms 63 ms 216.239.57.147

 

[mechBgon]

Do an ipconfig /all to get the IP's of the Comcast DNS servers and try pinging them both. See if one's down.

 

[MaxDSP]

nope, they both seem to be up (im behind a router btw, got the dns ip's from the router page). Are the times normal or kind of on the high side?

F:\>ping 63.240.76.198

Pinging 63.240.76.198 with 32 bytes of data:

Reply from 63.240.76.198: bytes=32 time=31ms TTL=54
Reply from 63.240.76.198: bytes=32 time=31ms TTL=54
Reply from 63.240.76.198: bytes=32 time=31ms TTL=54
Reply from 63.240.76.198: bytes=32 time=31ms TTL=54

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

F:\>ping 204.127.199.8

Pinging 204.127.199.8 with 32 bytes of data:

Reply from 204.127.199.8: bytes=32 time=78ms TTL=53
Reply from 204.127.199.8: bytes=32 time=62ms TTL=53
Reply from 204.127.199.8: bytes=32 time=47ms TTL=53
Reply from 204.127.199.8: bytes=32 time=62ms TTL=53

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

 

[mechBgon]

I'm not sure what the ping times ought to be. You might look at your HOSTS file and ensure that the only thing in it is 127.0.0.1 localhost. If you installed any additional listings yourself (or if malware did), try taking it out.

 

[Uncle Bob]

what happens if you try a tracert to newegg.com or any of the other problem sites?

 

[MaxDSP]

F:\>tracert www.newegg.com
Unable to resolve target system name www.newegg.com.

 

[Jeffyboy]

Is it just secure websites you can't access? Maybe you'll have to try something like
regsvr32 softpub.dll
to re-register important files.

http://support.microsoft.com/d...cid=kb;en-us;813444#12

Jeff

 

[Uncle Bob]

C:\DOCUME~1\BOB>ping www.newegg.com

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

Request timed out.
Reply from 64.94.111.114: Destination net unreachable.
Request timed out.
Reply from 64.94.111.114: Destination net unreachable.

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

seems newegg.com is down?

 

[Uncle Bob]

update:

I've just checked www.newegg.com in my browser and it loads fine but I still can't ping the site and I can't tracert to either so their firewall is obviously setup to reject ping requests...

you could try opening http://216.52.208.185/ in your browser, this will at least rule out DNS problems

 

[MaxDSP]

Originally posted by: Uncle Bob
update:

I've just checked www.newegg.com in my browser and it loads fine but I still can't ping the site and I can't tracert to either so their firewall is obviously setup to reject ping requests...

you could try opening http://216.52.208.185/ in your browser, this will at least rule out DNS problems

Using the ip address, I could open up the site. I cant open it up if I type in www.newegg.com however. This means that it is a DNS-related problem right?

 

[MaxDSP]

Originally posted by: mechBgon
I'm not sure what the ping times ought to be. You might look at your HOSTS file and ensure that the only thing in it is 127.0.0.1 localhost. If you installed any additional listings yourself (or if malware did), try taking it out.

The HOSTS file only shows the localhost entry.

 

[mrEvil]

Hmmmm.....going to suggest something that you may have already done. Have you run any anti-spyware software on your system and also done a full AV scan? Just something that I did not see you write down that I would also try. Nothing like a trojan or some spyware to "assist" you in your browsing, though normally just with IE.

 

[MaxDSP]

Originally posted by: mrEvil
Hmmmm.....going to suggest something that you may have already done. Have you run any anti-spyware software on your system and also done a full AV scan? Just something that I did not see you write down that I would also try. Nothing like a trojan or some spyware to "assist" you in your browsing, though normally just with IE.

It's also happening with Firefox and Outlook. When I try to download from Hotmail and my own website's email addresses, I get errors.

 

[Uncle Bob]

Originally posted by: MaxDSP

Originally posted by: Uncle Bob
update:

I've just checked www.newegg.com in my browser and it loads fine but I still can't ping the site and I can't tracert to either so their firewall is obviously setup to reject ping requests...

you could try opening http://216.52.208.185/ in your browser, this will at least rule out DNS problems

Using the ip address, I could open up the site. I cant open it up if I type in www.newegg.com however. This means that it is a DNS-related problem right?

That's the way I read it. Check your isp hasn't had problems or reassigned the DNS servers to other addresses.

 

[MaxDSP]

Over at dslreports.com I see a few posts regarding people having trouble accessing .edu domains and complete outages in and around Boston/East Coast, but nothing local around Chicago. I checked the router and while it lists the DNS servers that it got from Comcast, it doesn't give me an option to change them. I released and renewed the IP for the router and rebooted/power-cycled the modem but none of that helped. Guess I'll have to give Comcast a call later on today and see if it's a known issue or just my machine.

 

[MaxDSP]

Finally found the root cause of the issue...it's definetly the DNS server listings in my router's configuration. When I plugged the pc straight into the cable modem, the DNS server listings I got were 63.240.76.4 and 204.127.198.4. I've checked everywhere in the router configuration pages but cannot for the life of me see where I can change the dns addresses. Powercycling the router isnt helping and neither is releasing and renewing the ip for the router. Anyone familiar with changing these kind of settings on a Dlink DI-604? Didnt find anything on dlinks site

 

[MaxDSP]

Update: Emailed dlink tech support and although I thought I had the most current firmware installed, turned out I didnt. I installed the most recent one and found that they had added fields to modify DNS severs on one of the configuration pages.

BTW, I was surprised at the response time from Dlink. I emailed them about 4:30 pm yesterday and recieved a reply with the instructions around 4:56 pm the same day.