Jump to content

Thai Visa Not Loading


theoldgit

Recommended Posts


netsh interface ip set dns "Local Area Connection" static 8.8.8.8
netsh interface ip add dns name="Local Area Connection" addr=8.8.4.4
netsh interface ip set dns "Wireless Network Connection" static 8.8.8.8
netsh interface ip add dns name="Wireless Network Connection" addr=8.8.4.4
pause

create a batch file with the above code and run it whenever you want to use Google's DNS

Link to comment
Share on other sites

  • 2 weeks later...

:whistling:

Same here...tried for nearly 5 hours to post a reply to one topic...but nothing got through before it timed out.

Think it was my internet connection.

I'm here in flooded Lat Prao and connecting through True.

Seems to have cleared in the last hour or so.

I was able to log in to ThaiVisa but slow, and never did manage to post a reply.

But it seems to be working normally now.

:lol:

addendum:

But while I was unable to post into TV...I was also able to log-in to my U.S. bank with minimum delay.

Not sure why...but I don't blame ThaiVisa.

There is also about a foot of water outside my house...so any internet connection is fime by me.

:D

Edited by IMA_FARANG
Link to comment
Share on other sites

Same problem.

True. Firefox. No DNS (or just True DNS). Same problem with Chrome and IE.

It's been happening for a day or two. Mostly not loading all the images ("Hot Topic").

I had a brief respite this morning, but it's back to loading slow.

Sure you will have the same problem with any other browser if it is a DNS problem. I have no problem whatsoever, using NO DNS means that it is using the DNS from your ISP. Simply do not use it. Use either OpenDNS / DYNDNS or even use the public DNS from Time Warner or any other public DNS. Each and every ISP has the same problem in Thailand. As a workaround you could go to: www.unblock.biz or use a proxy.

Link to comment
Share on other sites

Same problem.

True. Firefox. No DNS (or just True DNS). Same problem with Chrome and IE.

It's been happening for a day or two. Mostly not loading all the images ("Hot Topic").

I had a brief respite this morning, but it's back to loading slow.

Sure you will have the same problem with any other browser if it is a DNS problem. I have no problem whatsoever, using NO DNS means that it is using the DNS from your ISP. Simply do not use it. Use either OpenDNS / DYNDNS or even use the public DNS from Time Warner or any other public DNS. Each and every ISP has the same problem in Thailand. As a workaround you could go to: www.unblock.biz or use a proxy.

I swap between the default ISP (True) DNS and a DNS provided to me by George. I usually need to swap at least once a day. I have found that occasionally a <CTRL>-<F5> will fix the problem temporarily.

Link to comment
Share on other sites

  • 1 month later...

I have been having this same issue for the past few weeks. I am on TRUE adsl 9Mbps and I use multiple browsers and google dns (8.8.8.8). The only way I can get the pages to display correctly is by going through a proxy using TOR. It's not the browser or the DNS but I believe it's TRUE's fault. The common thread I am seeing from everyone is that TRUE is their ISP. When I route the traffic through a proxy then everything loads just fine. This all points to the caching that TRUE does as the culprit. I'm not sure how to get them to solve this issue but I have TRUE techs coming tomorrow to swap out my modem and I will try and show them and see what they say.

Here's my tracert from TRUE

Tracing route to static.thaivisa.com [209.190.1.125]
over a maximum of 30 hops:

 1     1 ms    <1 ms     1 ms  router [192.168.1.1]
 2    38 ms    35 ms    36 ms  10.169.214.178
 3    46 ms    55 ms    34 ms  10.169.214.177
 4    34 ms     *        *     119-46-121-**.static.asianet.co.th [119.46.121.**]
 5    35 ms    44 ms    34 ms  61-91-210-66.static.asianet.co.th [61.91.210.66]

 6   108 ms    36 ms    48 ms  203-144-144-27.static.asianet.co.th [203.144.144.27]
 7   105 ms    40 ms    34 ms  61-91-210-1.static.asianet.co.th [61.91.210.1]
 8    36 ms    36 ms    35 ms  61.19.10.25
 9    37 ms    34 ms    35 ms  61.19.9.133
10    35 ms    43 ms    35 ms  61.19.9.38
11   258 ms   263 ms   251 ms  61.19.9.174
12   258 ms   251 ms   251 ms  ge-4-1.car4.SanJose1.Level3.net [4.71.114.41]
13   246 ms   245 ms   247 ms  vlan60.csw1.SanJose1.Level3.net [4.69.152.62]
14   272 ms   252 ms   256 ms  ae-61-61.ebr1.SanJose1.Level3.net [4.69.153.1]
15   340 ms   326 ms   328 ms  ae-2-2.ebr2.NewYork1.Level3.net [4.69.135.186]
16   338 ms   331 ms   409 ms  ae-6-6.ebr2.NewYork2.Level3.net [4.69.141.22]
17   322 ms   328 ms   322 ms  ae-1-100.ebr1.NewYork2.Level3.net [4.69.135.253]

18   347 ms   343 ms   332 ms  ae-3-3.ebr2.Washington1.Level3.net [4.69.132.89]

19   331 ms   323 ms   331 ms  ae-72-72.csw2.Washington1.Level3.net [4.69.134.150]
20   332 ms   332 ms   354 ms  ae-24-70.car4.Washington1.Level3.net [4.69.149.70]
21   337 ms   327 ms   333 ms  ENET-INC.car4.Washington1.Level3.net [4.79.171.122]
22   318 ms   332 ms   318 ms  ten3-2.core-1.xlhost.com [206.222.25.126]
23   319 ms   317 ms   318 ms  vl4079.pe-11.xlhost.com [206.222.25.186]
24   325 ms   325 ms   325 ms  7d.1.be.static.xlhost.com [209.190.1.125]

Trace complete.

Link to comment
Share on other sites

True's fault, always appears to be this...... As I have said many times before Thaivisa mostly works fine at home, yes true and set as George advised....... Classified is a different matter has never loaded for me after all this time..

Due to floods and order to leave last months spend over 3 weeks around the south of Thailand many different PC's, and many different laptop Wi-Fi connections, Thaivisa was a very hit and miss affair.

Thursday and Friday last week was in K.L. only used different PC's at internet places, often would not load, or timed out, or simply would never completed loading.. So nothing to do with True.

As 2012 is just around the corner one hopes there will be a new format that will work for everyone on any PC anywhere, it is not possible to start resetting cafe or hotel internet PC's

As I say here at home works fine after making all the different settings

Edited by ignis
Link to comment
Share on other sites

Yes it's True's fault. Try to use 202.170.126.90 as primary DNS.

With the above DNS

Tracing route to thaivisa.com [175.41.131.133]
over a maximum of 30 hops:

 1     2 ms     3 ms     2 ms  192.168.1.1 
 2     *        *        *     Request timed out.
 3   465 ms   438 ms   465 ms  10.121.84.234 
 4     *        *        *     Request timed out.
 5   487 ms   546 ms   449 ms  mx-ll-110.164.0-210.static.3bb.co.th [110.164.0.210] 
 6   374 ms   398 ms   449 ms  mx-ll-110.164.1-63.static.3bb.co.th [110.164.1.63] 
 7   373 ms   403 ms   404 ms  mx-ll-110.164.1-11.static.3bb.co.th [110.164.1.11] 
 8   427 ms   397 ms   449 ms  182.50.84.217 
 9   389 ms   414 ms   478 ms  182.50.84.186 
10   542 ms   421 ms   330 ms  p38895.sgw.equinix.com [202.79.197.87] 
11   346 ms   312 ms   308 ms  203.83.223.8 
12   566 ms   578 ms   472 ms  203.83.223.31 
13     *        *        *     Request timed out.
14   437 ms   317 ms   389 ms  ec2-175-41-128-42.ap-southeast-1.compute.amazonaws.com [175.41.128.42] 
15   404 ms   385 ms   436 ms  ec2-175-41-128-10.ap-southeast-1.compute.amazonaws.com [175.41.128.10] 
16   453 ms   447 ms   475 ms  ec2-175-41-128-29.ap-southeast-1.compute.amazonaws.com [175.41.128.29] 
17   167 ms   399 ms   315 ms  ec2-175-41-128-203.ap-southeast-1.compute.amazonaws.com [175.41.128.203] 
18   355 ms   445 ms   482 ms  ec2-175-41-131-133.ap-southeast-1.compute.amazonaws.com [175.41.131.133] 

Trace complete.

Link to comment
Share on other sites

Yes it's True's fault. Try to use 202.170.126.90 as primary DNS.

With the above DNS

Tracing route to thaivisa.com [175.41.131.133]
over a maximum of 30 hops:

 1     2 ms     3 ms     2 ms  192.168.1.1 
 2     *        *        *     Request timed out.
 3   465 ms   438 ms   465 ms  10.121.84.234 
 4     *        *        *     Request timed out.
 5   487 ms   546 ms   449 ms  mx-ll-110.164.0-210.static.3bb.co.th [110.164.0.210] 
 6   374 ms   398 ms   449 ms  mx-ll-110.164.1-63.static.3bb.co.th [110.164.1.63] 
 7   373 ms   403 ms   404 ms  mx-ll-110.164.1-11.static.3bb.co.th [110.164.1.11] 
 8   427 ms   397 ms   449 ms  182.50.84.217 
 9   389 ms   414 ms   478 ms  182.50.84.186 
10   542 ms   421 ms   330 ms  p38895.sgw.equinix.com [202.79.197.87] 
11   346 ms   312 ms   308 ms  203.83.223.8 
12   566 ms   578 ms   472 ms  203.83.223.31 
13     *        *        *     Request timed out.
14   437 ms   317 ms   389 ms  ec2-175-41-128-42.ap-southeast-1.compute.amazonaws.com [175.41.128.42] 
15   404 ms   385 ms   436 ms  ec2-175-41-128-10.ap-southeast-1.compute.amazonaws.com [175.41.128.10] 
16   453 ms   447 ms   475 ms  ec2-175-41-128-29.ap-southeast-1.compute.amazonaws.com [175.41.128.29] 
17   167 ms   399 ms   315 ms  ec2-175-41-128-203.ap-southeast-1.compute.amazonaws.com [175.41.128.203] 
18   355 ms   445 ms   482 ms  ec2-175-41-131-133.ap-southeast-1.compute.amazonaws.com [175.41.131.133] 

Trace complete.

Thanks, did this improve your experience while browsing Thaivisa?

Link to comment
Share on other sites

  • 2 weeks later...

My problem sorted itself out a few weeks ago, only to return the next day. Thai Visa worked normally for one day last week and then the problem returned, it affects both my laptops and the wi-fi on my phone. I wish I knew how to correct it, I'm scared that if I altered any settings, even if I knew how, it would affect everything else, which work perfectly.

Link to comment
Share on other sites

My problem sorted itself out a few weeks ago, only to return the next day. Thai Visa worked normally for one day last week and then the problem returned, it affects both my laptops and the wi-fi on my phone. I wish I knew how to correct it, I'm scared that if I altered any settings, even if I knew how, it would affect everything else, which work perfectly.

In support we see that most problems arise from not using Thai ISP's DNS settings. Try to revert to default DNS settings.

Link to comment
Share on other sites

It seems to have to do with True routing to Akamai edge servers. True doesn't like to route to some Akamai servers outside its domain (most likely at competitors sites...)

In a multi-homed environment you can't really use 'local' DNS servers as they don't respond to request outside their domain.

I've solved this locally by routing static.thaivisa.com through a backup link (3BB). But the problem indeed seems to lie with True.

Link to comment
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.








×
×
  • Create New...