Conversation started Jan 20, 2011 at 18:10.
Jan 20, 2011 18:10
darn.... I can't get to SU, SO, MSO or SE... but for some reason can get here...
try closing your browser, using ccleaner (clearing temp files), then retrying.
@David done all that, reset router as well
most of the internet is working fine as well, only found the SE sites problematic
hmmm, doesn't work in other browsers either >(
@DMA57361: Can you reach stackexchange.com?
Jan 20, 2011 18:18
@DMA57361: Have you tried pinging the sites?
ping superuser.com should give 64.34.119.12.
no... was messing with dns h/o
@TomWij yup, matching result here
What does a tracert or pathping (Windows only, more analysis) with the parameter superuser.com reveal?
it routes "successfully" to stackover.com [64.34.119.12]
(althought one step in the chain is a set of 3 timeouts)
Hmm, so no DNS resolving problems, it didn't show dropped packets either?
@DMA57361 @TomWij funny... I'm writing up a blog entry on DNS issues
Jan 20, 2011 18:22
nothing dropped except the line that failed entirely
switching to google's DNS and clearing everything doesn't seem to have helped either
@DMA57361: Do you have Google Chrome?
I have it installed, yes, but I've not tried it yet
(for this problem, I mean)
Try it, if it doesn't work then visit chrome://net-internals/ and try:
- Check if the proxy tab lists the right settings, these should be the ones taken from Internet Explorer.
- See if the event tab lists any errors, and see what it lists when trying to resolve superuser.com, for me it gives:
there's no proxy settings, which is correct
(P) t=1295547738381 [st=0] +HOST_RESOLVER_IMPL_JOB  [dt=8]
                        --> host = "superuser.com"
                        --> source_dependency = {"id":42493,"type":7}
(P) t=1295547738389 [st=8] -HOST_RESOLVER_IMPL_JOB
                        --> address_list = ["64.34.119.12:80"]
- See if the DNS tab lists a superuser.com entry, for me it gives:
superuser.com	ADDRESS_FAMILY_UNSPECIFIED	64.34.119.12:80
Jan 20, 2011 18:27
superuser.com UNSPECIFIED 64.34.119.12 33168
@DMA57361: And if all looks fine, the tests tab should allow you to type in superuser.com and show you a lot of details.
erm, this page isn't tabbed ? ... I may have an old version
I only get errors where it says "Use Firefox's proxy settings", but that's because I don't have Firefox. Nice to see it's smart enough to probe Firefox when Internet Explorer is broken... :-D
Isn't there a tests tab?
on chrome://net-internals/ there's no tabs at all - just lots of sections above one-another, and I can't see "tests"
@DMA57361: 10.0.634.0 dev here, but well, some statistics aren't fully implemented but they should be sufficient to troubleshooting where the problem lies.
Jan 20, 2011 18:30
lol
5.0.375.127
let me try updating :)
@DMA57361 Seems like an old version, isn't there a textbox at the bottom which allows you to test?
> Blog: Chrome on stable channel has been updated to 8.0.552.237 for all platforms.
chrome isn't my standard browser
Yeah, probably not a bad idea.
Yeah, I just don't know how to troubleshoot in other browsers, but I guess that looking for network diagnostics there might give similar pages.
much better...let's have a look
tabs! ah ha :D
testing now
FAIL
Fetch http://superuser.com/ Don't use any proxy
-101
41960
second one is also taking ages...so doesn't bode well
do you know how many tests it tries?
Strange, you can ping to it, so you can reach the machine and packets aren't dropped.
To me that would say that something is filtering your network traffic.
Have you tried disabling firewalls?
Jan 20, 2011 18:39
only have the Windows one on
@DMA57361: Try disabling it just to be sure that the settings aren't messed up. Although...
anywhere have a list of the error numbers these tests return?
all I'm getting is -101
It might be unlikely that something is specifically blocking superuser.com.
na, not change
@TomWij and stackexchange.com and stackoverflow.com but not chat.SE.com...
ERROR: Error 101 (net::ERR_CONNECTION_RESET): Unknown Error
Jan 20, 2011 18:42
is chat on a different IP range?
@TomWij ah...
By googling "google chrome 101".
well all tests complete, all FAIL after ~41s
Connection reset would seem like a firmware action, either by ISP or by your Windows Firewall.
@TomWij ah, I was being too specific it seems
@DMA57361: Yeah, likely to be timeouts.
Jan 20, 2011 18:43
oo, I can get to meta.SE as well
Chat is 69.59.196.211 while SU is 64.34.119.12 while Meta.SE is 64.34.80.165.
So yeah, looks like different ranges.
well...maybe I'll just have to do something else this evening
@DMA57361: If disabling anti-virus, firewall and cleaning temp data doesn't resolve anything; then yes, it might be your ISP...
Those are the suggestions I can find from Google Employees.
Cleaning temp data won't help as you are just getting the right IP.
Windows Firewall is unlikely as you probably haven't blocked the site or IP specifically.
So, an update or setting change to your anti-virus software (that has web filtering) could probably be the issue; if it isn't the ISP.
hadn't though of AV, but it didn't help
But yeah, troubleshooting has to end somewhere. I wouldn't feel like calling the ISP either, unless the issue remains for a long time.
Jan 20, 2011 18:51
hmmm, oh well
thank's for your help
Leaned pathping while I had problem some weeks ago.
I had a perfect connection with people from The Netherlands while gaming, but there was weird lag when gaming with someone from America.
Furthermore, scalable sites like Google just work fine, but Stack Exchange didn't work for me either.
But, it was just an issue that night and it didn't come back later...
Guess some major switch was having issues.
 
Conversation ended Jan 20, 2011 at 18:53.