Ive been having a sporadic problem that is annoying the hell out of me. I am having problems accessing one certain website, but everyone else can access it fine. Including my ISP. They keep telling me they can access it fine, but its just not working on my side. When i try to load the page, it just gets to the "waiting for ........" portion and gets stuck. Tried it with both firefox and IE. Same thing, except IE displays the "internet explorer cannot display the webpage" error. The funny thing is if i use a public proxy server, i can access the site. If im using the "direct connection" option in my browser though, it wont display. All other sites work fine, just this one. Said site is.....4chan.org. The front page loads fine, but the boards dont. Well, THIS time(third time now), all the boards on zip.4chan.org or orz.4chan.org are refusing to load. The random board located on img.4chan.org and the boards at cgi.4chan.org are loading fine. ISP apparently has no clue what is causing it and is grasping at straws(turn off anti-virus blah blah blah). You probably want the tracerts that ive been giving them as well : Code: Tracing route to zip.4chan.org [66.207.165.176] over a maximum of 30 hops: 1 9 ms 7 ms 8 ms 10.53.128.1 2 9 ms 9 ms 13 ms 172.20.53.193 3 20 ms 8 ms 8 ms 172.26.53.1 4 11 ms 14 ms 8 ms 172.20.8.125 5 11 ms 8 ms 8 ms 203.116.5.97 6 19 ms 17 ms 15 ms 203.118.3.229 7 237 ms 230 ms 237 ms p16-0-2-0.r21.tokyjp01.jp.bb.gin.ntt.net [129.25 0.12.241] 8 233 ms 244 ms 230 ms ae-2.r20.tokyjp01.jp.bb.gin.ntt.net [129.250.3.2 09] 9 237 ms 248 ms 234 ms as-1.r20.snjsca04.us.bb.gin.ntt.net [129.250.2.3 4] 10 244 ms 227 ms 234 ms ae-0.r21.snjsca04.us.bb.gin.ntt.net [129.250.2.9 7] 11 227 ms * * ae-2-54.bbr2.LosAngeles1.Level3.net [4.68.102.97 ] 12 276 ms 215 ms 275 ms as-1-0.bbr2.Dallas1.Level3.net [64.159.0.245] 13 275 ms 277 ms 278 ms ae-24-54.car4.Dallas1.Level3.net [4.68.122.112] 14 * * 279 ms 4.78.224.150 15 277 ms 281 ms 277 ms 66.207.165.176 Code: Tracing route to orz.4chan.org [66.207.165.168] over a maximum of 30 hops: 1 10 ms 8 ms 8 ms 10.53.128.1 2 8 ms 8 ms 18 ms 172.20.53.193 3 9 ms 6 ms 9 ms 172.26.53.1 4 9 ms 9 ms 10 ms 172.20.8.125 5 10 ms 9 ms 12 ms 203.116.5.97 6 25 ms 19 ms 17 ms 203.118.3.229 7 232 ms 234 ms 230 ms p16-0-2-0.r21.tokyjp01.jp.bb.gin.ntt.net [129.25 0.12.241] 8 233 ms 245 ms 245 ms as-0.r21.lsanca03.us.bb.gin.ntt.net [129.250.3.1 45] 9 236 ms 244 ms 234 ms as-1.r20.snjsca04.us.bb.gin.ntt.net [129.250.2.3 4] 10 234 ms 226 ms 231 ms ae-0.r21.snjsca04.us.bb.gin.ntt.net [129.250.2.9 7] 11 227 ms 244 ms * ae-2-56.bbr2.LosAngeles1.Level3.net [4.68.102.16 1] 12 276 ms 230 ms 217 ms ae-2-56.bbr2.SanJose1.Level3.net [4.68.123.161] 13 278 ms 278 ms * as-1-0.bbr2.Dallas1.Level3.net [64.159.0.245] 14 282 ms * 279 ms 4.78.224.150 15 278 ms 279 ms 281 ms 66.207.165.168
Do you have any other computers in your house that you can try to access the site on? or perhaps a friend with a laptop? First step should be to rule out your computer [OT] just out of interest, why is your computers IP address 10.53.128.1? did you choose to use that address range yourself or are you on a massive (private) network? [/OT]
No other comps. For some reason its working now, maybe my ISP did something. My ISP assigns the IP addresses, so i have no clue.
This is mainly for future reference, since it seems to be working for you. For an issue like yours, there are 3 general possibilities for the cause of the issue. Client issue - a problem on your operating system, browser, etc. Network issue - something between you and the server Server issue - something on the server end is either failing or blocking you To cover the first issue, I'd boot to a live Linux distro. That will eliminate all possible client-level problems, since you have a fresh & clean OS, browser, etc. To address the second, there's not too much you can do except test another computer from the same network, do traceroutes, etc. However, I really don't believe that was the issue in your case, since you can trace all the way to the hosts in question. Your packets are getting there. On the 3rd possible issue, your IP could be on a blacklist or firewall ACL for the site in question. This one is the most difficult to diagnose, since you have no way to see what's happening on the server end. If it was a general problem on the server, it would probably effect everyone, not just you. The best way to approach this is to troubleshoot through steps 1&2, then contact the admin, providing all you did to troubleshoot the issue. Best regards, -AT
That would be a client-end issue. Windows does have DNS cache problems on occasion, but booting to a new OS would certainly eliminate that as a possibility. That's why I recommend it as an initial troubleshooting step; it clears several possibilities right up front. Namely malware, misconfiguration issues, and plain old Microsoft bugs.