kburn Posted November 3, 2007 Share Posted November 3, 2007 (edited) is this happening to anyone else? i'm using True DSL and haven't been able to connect to wikipedia for 3 days. edit: i'm in Bangkok. Edited November 3, 2007 by kburn Link to comment Share on other sites More sharing options...
Acquiesce Posted November 3, 2007 Share Posted November 3, 2007 I'm in Bangkok and have just tested it, no problems. Link to comment Share on other sites More sharing options...
kburn Posted November 3, 2007 Author Share Posted November 3, 2007 Acquiesce - are you using True? when i try to access it all i get is a blank page. Link to comment Share on other sites More sharing options...
cdnvic Posted November 3, 2007 Share Posted November 3, 2007 Clear your cache and try reloading the page. Other things to try: Switch to OpenDNS, and most Thai ISPs have crap DNS. http://www.opendns.org/ If you are using Firefox type about:config in the address bar and scroll down until you see network.http.keep-alive.timeout , right-click on it, choose modify and change the value to 1000 That will keep it from timing out on a lagged connection. Link to comment Share on other sites More sharing options...
yeti Posted November 4, 2007 Share Posted November 4, 2007 is this happening to anyone else? i'm using True DSL and haven't been able to connect to wikipedia for 3 days.edit: i'm in Bangkok. I'm having the same problem, True Bangkok as well. All other websites are ok. Pinging en.wikipedia.org gives me this: ping en.wikipedia.orgPinging rr.yaseo.wikimedia.org [203.212.189.253] with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 203.212.189.253: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss) Can someone confirm that rr.yaseo.wikimedia.org [203.212.189.253] is normal? A tracert gives me: tracert en.wikipedia.orgTracing route to rr.yaseo.wikimedia.org [203.212.189.253] over a maximum of 30 hops: 1 34 ms 20 ms 19 ms ppp-124.120.189.1.revip2.asianet.co.th [124.120.189.1] 2 20 ms 48 ms 47 ms ppp-210.86.189.46.revip.asianet.co.th [210.86.189.46] 3 22 ms 22 ms 22 ms 10.169.46.1 4 51 ms 56 ms 21 ms 58-97-25-102.static.asianet.co.th [58.97.25.102] 5 48 ms 21 ms 21 ms 61-90-133-237.static.asianet.co.th [61.90.133.237] 6 21 ms 70 ms 21 ms 61-90-254-89.static.asianet.co.th [61.90.254.89] 7 22 ms 22 ms 22 ms 203-144-144-9.static.asianet.co.th [203.144.144.9] 8 23 ms 21 ms 63 ms TIG-Net28-9.trueinternetgateway.com [122.144.28.9] 9 307 ms 306 ms 307 ms SG-ICR-ANC1-26-206.trueinternetgateway.com [122.144.26.206] 10 307 ms 306 ms 327 ms US-ICR-DC1-26-222.trueinternetgateway.com [122.144.26.222] 11 * 306 ms 306 ms GigabitEthernet3-0.IG3.PAO1.ALTER.NET [157.130.211.77] 12 307 ms 305 ms 305 ms 0.so-1-2-0.XL1.PAO1.ALTER.NET [152.63.51.54] 13 381 ms 310 ms 358 ms 0.so-5-2-0.XT1.SCL2.ALTER.NET [152.63.54.134] 14 306 ms 307 ms 333 ms 0.so-6-0-0.BR3.SCL2.ALTER.NET [152.63.49.1] 15 307 ms 306 ms 306 ms 204.255.169.162 16 318 ms 308 ms 310 ms ae-1.r20.snjsca04.us.bb.gin.ntt.net [129.250.5.33] 17 438 ms 425 ms 442 ms as-2.r20.tokyjp01.jp.bb.gin.ntt.net [129.250.2.35] 18 462 ms 438 ms 438 ms as-0.r00.seolko01.kr.bb.gin.ntt.net [129.250.3.246] 19 471 ms 480 ms 459 ms 129.250.16.50 20 * * * Request timed out. 21 * * * Request timed out. 22 * * * Request timed out. 23 * * * Request timed out. 24 * * * Request timed out. 25 * * * Request timed out. 26 * * * Request timed out. 27 * * * Request timed out. 28 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out. Trace complete. So the culprit seems to be 129.250.16.50 right? That's NTT America. I'll try switching to open DNS. Link to comment Share on other sites More sharing options...
Insight Posted November 4, 2007 Share Posted November 4, 2007 I haven't been able to access using True in Bangkok, but can from other machines. The cynic in me thinks there's been an attempt to block it? Link to comment Share on other sites More sharing options...
ashacat Posted November 4, 2007 Share Posted November 4, 2007 Yeah, I'm on True in Bangkok and also cannot open Wikipedia. Link to comment Share on other sites More sharing options...
yeti Posted November 4, 2007 Share Posted November 4, 2007 Switching to Open DNS (see cdnvic post) fixed the problem . Link to comment Share on other sites More sharing options...
davejonesbkk Posted November 4, 2007 Share Posted November 4, 2007 I have internet in my service apartment (no idea what company i just pay the landlord) and wiki has been on and off for over 48 hours now.... as of right now it wont open at all....better not be blocked!!!!!!!! Link to comment Share on other sites More sharing options...
percy2 Posted November 4, 2007 Share Posted November 4, 2007 Clear your cache and try reloading the page.Other things to try: Switch to OpenDNS, and most Thai ISPs have crap DNS. http://www.opendns.org/ If you are using Firefox type about:config in the address bar and scroll down until you see network.http.keep-alive.timeout , right-click on it, choose modify and change the value to 1000 That will keep it from timing out on a lagged connection. Thanks Vic Cheers Link to comment Share on other sites More sharing options...
kburn Posted November 4, 2007 Author Share Posted November 4, 2007 cdnvic - thanks. switching to OpenDNS got Wikipedia working again. but now a few other sites(that were working yesterday) don't open. any ideas? Link to comment Share on other sites More sharing options...
cdnvic Posted November 4, 2007 Share Posted November 4, 2007 cdnvic - thanks. switching to OpenDNS got Wikipedia working again. but now a few other sites(that were working yesterday) don't open.any ideas? Study Buddhism... it helps teach us not to desire such things in the first place. Link to comment Share on other sites More sharing options...
qualtrough Posted November 4, 2007 Share Posted November 4, 2007 True too, cannot access for 2-3 days now. I use it all the time so I am bummed. Link to comment Share on other sites More sharing options...
sprq Posted November 5, 2007 Share Posted November 5, 2007 Me too, for 3 or 4 days now, using True. Link to comment Share on other sites More sharing options...
joebuzzard Posted November 5, 2007 Share Posted November 5, 2007 (edited) Well, at least I'm not the only one with this problem. I was going nuts trying to figure it out. Thing is, I could access via True WI-FI network outside, but not from my home network. I guess outside, it might not necessarily be an actual True network I'm on. Whatever. It's very frustrating. Edited November 5, 2007 by joebuzzard Link to comment Share on other sites More sharing options...
sprq Posted November 7, 2007 Share Posted November 7, 2007 I called true an hour ago about it and they just called back to say "the network team has found the problem" and they're working on it and that they'll call me later about it. Sometimes things in Thailand are super-efficient, thank god. Link to comment Share on other sites More sharing options...
delboy Posted November 7, 2007 Share Posted November 7, 2007 (edited) No Wiki for me either for 3 days. I'm on Maxnet, other friends having no problems. ok to access it on dial-up connection. Edited November 7, 2007 by delboy Link to comment Share on other sites More sharing options...
joebuzzard Posted November 7, 2007 Share Posted November 7, 2007 Tried OpenDNS and adjusting the settings in Firefox as suggested above, and that didn't work either. I sent an e-mail to tech support at True, and they called me back, and were saying something about an engineer coaching me through my proxy settings. Unfortunately, I was at work and unable to access my home network. I wonder what they were on about? I've never had to mess with the proxy settings before. Hopefully they'll be back in touch. I use Wikipedia a lot, so it's kind of pain, it being the only website I can't access. Link to comment Share on other sites More sharing options...
Firefoxx Posted November 8, 2007 Share Posted November 8, 2007 Using the default True settings, you can't access wikipedia. However, if you set your proxy to True's proxy, or if you set your DNS settings to somewhere else, you can access it. It's probably just a bad configuration on True's part, which isn't anything new. Don't expect a fix anytime soon. Link to comment Share on other sites More sharing options...
lopburi3 Posted November 8, 2007 Share Posted November 8, 2007 I am using OpenDns settings on TRUE and Wikipedia can not be viewed. This has been the case all week. Edit: have returned to TRUE DNS assigned servers and same - timeout. Link to comment Share on other sites More sharing options...
joebuzzard Posted November 8, 2007 Share Posted November 8, 2007 Turned off Open DNS settings, since they weren't a solution, anyway. As poster above mentioned, I had to manually set the true proxy, and now Wikimedia is working fine. Firefox Tools > Options > Advanced > Network > Settings > Manual proxy configuration > HTTP Proxy > proxy.asianet.co.th > Port 80 Ok Ok Explorer Tools > Internet Options > Connections > Lan Settings > Proxy server > Click box > Address: proxy.asianet.co.th > Port: 80 Ok Ok Link to comment Share on other sites More sharing options...
cclub75 Posted November 8, 2007 Share Posted November 8, 2007 (edited) I am using OpenDns settings on TRUE and Wikipedia can not be viewed. This has been the case all week.Edit: have returned to TRUE DNS assigned servers and same - timeout. Same. True ADSL. Time out. I figured out only yesterday. However http://wikipedia.org/ goes through (slowly). What is worrying is the message about Maxnet.... What are they doing ? New dirty experiments regarding a proxy... to control access, without reading the notice ? I said that because during the Great YouTube Drama, the timeout was a trick used sometimes (and with other video websites). A typical thai way applied to censorship : we don't do nothing... it's just a timeout... network problem. Edited November 8, 2007 by cclub75 Link to comment Share on other sites More sharing options...
joebuzzard Posted November 8, 2007 Share Posted November 8, 2007 (edited) What are they doing ? New dirty experiments regarding a proxy... to control access, without reading the notice ? I said that because during the Great YouTube Drama, the timeout was a trick used sometimes (and with other video websites). A typical thai way applied to censorship : we don't do nothing... it's just a timeout... network problem. What are the implications of the proxy setting? Can somebody explain in dummy talk? I noticed that now it is not possible to edit wikipedia because of open proxy. So I think this is a bad thing. I can use secure log in and make edits though, https://secure.wikimedia.org/wikipedia/en/wiki/Main_Page Also, during the access troubles, I could access via the secure server, but functionality wasn't the best. It was very slow. Still, it doesn't address the disturbing issue of proxies and such that I'm not even sure what it means. Edited November 8, 2007 by joebuzzard Link to comment Share on other sites More sharing options...
Wolf Posted November 13, 2007 Share Posted November 13, 2007 (edited) Turned off Open DNS settings, since they weren't a solution, anyway.As poster above mentioned, I had to manually set the true proxy, and now Wikimedia is working fine. Firefox Tools > Options > Advanced > Network > Settings > Manual proxy configuration > HTTP Proxy > proxy.asianet.co.th > Port 80 Ok Ok Explorer Tools > Internet Options > Connections > Lan Settings > Proxy server > Click box > Address: proxy.asianet.co.th > Port: 80 Ok Ok Until today no Wikipedia as well. Joe Buzzards solution did the trick for me. Thanks, mate. Edited November 13, 2007 by Wolf Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now