February 21, 200719 yr For the past three weeks or so I have had continual connectivity issues. The TOT-sourced ADSL feed seems stable, at least the ADSL light on my wireless modem is solid, but my Firefox tabs show "connection reset" several times an hour. How can I troubleshoot this?
February 21, 200719 yr In the address bar of the browser type about:config scroll down to the Network.http.keep-alive and make sure that is set to true scroll down to network.http.keep-alive.timeout and set that to about 400
February 21, 200719 yr Read Opendns Change your settings and all will be well. It is for me. It also pays to check back through the last 2-3 days of posts. This topics was covered, 2 days ago. http://www.thaivisa.com/forum/index.php?showtopic=107298
February 22, 200719 yr Author Many thanks Cdnvic for the about: config - never even knew about it. And bountiful thanks to Astral; I just put in the new Opendns DNSes - both TCP/IP and in the modem/router. I hoping big improvements are heading my way.
February 22, 200719 yr Same here... half the time it just doesn't connect. Sometimes better sometimes worse. OpenDNS didn't make a difference for me. It seemed not so much a DNS issues, more like intermittent network outages (very short ones). So I would click on some link -> can't be found -> hit reload all is well. The outage lasted only for seconds at a time. Which makes me think that maybe the Thai proxy server is a bit funny these days. It did not affect continuous connections at all - my VPN would run just fine. It would be like this all day long. TOT ADSL here as well. Co-incidentally, this did not happen at all today. But it has been driving me crazy the last 3 weeks or so. It was not just my TOT connection either, happened in Cafes as well.
February 23, 200719 yr What value did you find for the timeout? Mine was 300 already, so a change to 400 does not sound that much,
February 23, 200719 yr Author I would say my downtime is halved. Not perfect, but certainly a significant improvement.
February 24, 200719 yr In the address bar of the browser type about:configscroll down to the Network.http.keep-alive and make sure that is set to true scroll down to network.http.keep-alive.timeout and set that to about 400 Would you care to share how you came up with the 400 for the timeout?
February 24, 200719 yr In the address bar of the browser type about:configscroll down to the Network.http.keep-alive and make sure that is set to true scroll down to network.http.keep-alive.timeout and set that to about 400 Would you care to share how you came up with the 400 for the timeout? Sounded about right I needed more than default to reach latent servers in Asia, but didn't want to wait around to get the message if it wasn't there so it seemed a good compromise.
February 24, 200719 yr I have a few friends using TOT - and we are all having trouble. TOT went downhill ever since the earthquake and never came back to where it was. I get the same thing all the time and I have a fast connection - bus - gold - My friend has regular 1024 and his is the same. Right now I'm using my backup 1024 Indy from TT&T and it beats the crap out of TOT.
Create an account or sign in to comment