Trying To Connect To Websites That Are Timingout

[lingyai]

It seems I having trouble connecting to a few websites but have no problem with connecting to most others. (I am using True)

For example digg.com when I go there it tries to connect but then after like 10 seconds the url in the address bar changes from digg.com to http://203.146.129.137:9000/ and says the connection has timed out.

I am not sure why this is. I went to opendns.com and started using their addresses but that didn’t solve the problem.

I know the websites I am trying to access are not down so it must be a problem with True right?

Anybody else having this problem?

[Martin_F]

It is the connection outside Thailand that is causing the problem too much access at the point when you are requesting the connection.

Just keep on refreshing and it should come.

Or a problem with your service provider.

[StrongView]

I'm getting this problem too...from True and on CSLox @ work. I went to the server named (http://203.146.129.137) and got a gaming site. Odd....

[PeaceBlondie]

I am having virtually the same problem as the OP, since last night about 10 pm Bangkok time. ThaiVisa and most other websites connect just fine, but one forum in the USA always times out. I use the world's slowest dial-up with LoxInfo.

[lingyai]

I'm getting this problem too...from True and on CSLox @ work. I went to the server named (http://203.146.129.137) and got a gaming site. Odd....

yes something like this happened to me. I put in one site and got another.

oh now things seem to be working.

Edited March 7, 2007 by lingyai

[MsFigure]

Also having this exact same problem trying to get onto my own website.

Anyone have a clue as to how long this problem will go on for? We use TOT ipStar.

Even though I can't access a certain site, are others still able to (elsewhere in the world)?

Thanks,

Di

Edited March 7, 2007 by MsFigure

[cdnvic]

If you're using Firefox, type about:config in the address bar and scroll down till you see

network.http.keep-alive

If the value isn't true, right-click on the line and click toggle.

Below it is network.http.keep-alive.timeout

The default setting is 300. Right-click and choose modify, then enter 400 to 600 as the new value. I'd try 400 and see if it works before going too high.

[Crushdepth]

We had the same problem at work this morning. If anyone is still having difficulties try clearing your browser cache, it worked for us.

[MsFigure]

If you're using Firefox, type about:config in the address bar and scroll down till you see

network.http.keep-alive

If the value isn't true, right-click on the line and click toggle.

Below it is network.http.keep-alive.timeout

The default setting is 300. Right-click and choose modify, then enter 400 to 600 as the new value. I'd try 400 and see if it works before going too high.

Crushdepth - We had the same problem at work this morning. If anyone is still having difficulties try clearing your browser cache, it worked for us.

Don't know which one of these 2 worked but all I know is that everything is working again.

THANK YOU !