Trouble accessing TCC site

Pucci

Speeding Up
Jul 12, 2006
283
1
38
Yokohama
#1
Since January or so I have been unable to access TCC from my three home computers (Itscom and eMobile both NG) but have no trouble from the OCN connection in my office.

Itscom says that they are getting slow responses from the interim servers on one of the hops, but do not know the cause.

This is making it very difficult to keep up with things TCC.

Does anyone else have this prolem?

Aaron
 

StuInTokyo

Maximum Pace
Dec 3, 2010
1,662
62
78
#2
Since January or so I have been unable to access TCC from my three home computers (Itscom and eMobile both NG) but have no trouble from the OCN connection in my office.

Itscom says that they are getting slow responses from the interim servers on one of the hops, but do not know the cause.

This is making it very difficult to keep up with things TCC.

Does anyone else have this prolem?

Aaron
We use Yahoo FLETS at home and KDDI ASDL at the L shop and have had no problem at all.
 

thomas

The Crank Engine
Nov 1, 2005
1,799
203
93
多摩区
#5
Since January or so I have been unable to access TCC from my three home computers (Itscom and eMobile both NG) but have no trouble from the OCN connection in my office.
Other than what Pete suggested have you checked your firewall? Happened to my home PC (J:com) after we had migrated to the new server in January.

Also, could you send me a traceroute from your home box to tokyocycle.com?


If I try and access with Mozilla I have severe problems. Pages typically take a long time to load then crash.
I'm using FF and have no such problems. Which add-ons have you installed? Do you use the latest version (3.6.13)?
 

trad

Maximum Pace
Dec 4, 2006
393
30
48
Tokyo
#7
i have the same issue with Pucci. I'm using IE 7 from my laptop. From the office, no problems, but from anywhere else (cable based internet, data card, etc...), pages take about 1 min to load and end up with garbled screen or crash. I can access OK from a different PC at home and also my iphone, but something changed soon after the server upgrade in Jan.

I've deleted all cookies and all other types of internet history (several times), but no change.:eek:uch:
 

thomas

The Crank Engine
Nov 1, 2005
1,799
203
93
多摩区
#8
Todor, could you please send me a traceroute from the work station in question via PM? I will then check with my hosting company.


Sent via iPhone using Tapatalk
 

Pucci

Speeding Up
Jul 12, 2006
283
1
38
Yokohama
#9
I have exactly the symptoms Trad described. From home the top page takes several minutes 5 load and finally comes up without graphics or formatting. Attempts to actually view threads almost always fail completely.

Tried clearing the cache, purging the DNS resolver cache and clearing cookies, but no improvement.
 

trad

Maximum Pace
Dec 4, 2006
393
30
48
Tokyo
#10
how to get trace routes? I can do tracert from c:/ prompt and runs a trace, but the screen disappears before I can copy down what it did.. How do you get results of c prompt command to not close?
 

Pucci

Speeding Up
Jul 12, 2006
283
1
38
Yokohama
#11
how to get trace routes? I can do tracert from c:/ prompt and runs a trace, but the screen disappears before I can copy down what it did.. How do you get results of c prompt command to not close?
Type cmd at the RUN prompt and then run tracert in the DOS window.

This is from my office where I can access TCC:

Tracing route to tokyocycling.com [69.93.100.41]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms . [192.168.1.1]
2 3 ms 3 ms 3 ms 122.1.212.137
3 3 ms 3 ms 8 ms 122.1.212.129
4 5 ms 6 ms 4 ms 221.184.12.189
5 4 ms 3 ms 4 ms 122.28.168.73
6 3 ms 3 ms 3 ms 118.23.168.27
7 13 ms 12 ms 13 ms ae-11.r21.tokyjp01.jp.bb.gin.ntt.net [129.250.12
.201]
8 12 ms 13 ms 15 ms ae-3.r21.osakjp01.jp.bb.gin.ntt.net [129.250.4.2
14]
9 128 ms 128 ms 128 ms as-1.r21.snjsca04.us.bb.gin.ntt.net [129.250.3.1
97]
10 176 ms 179 ms 169 ms ae-5.r21.dllstx09.us.bb.gin.ntt.net [129.250.4.2
4]
11 167 ms 167 ms 167 ms ae-5.r07.dllstx09.us.bb.gin.ntt.net [129.250.2.1
74]
12 169 ms 170 ms 161 ms xe-0-5-0-4.r07.dllstx09.us.ce.gin.ntt.net [157.2
38.224.182]
13 169 ms 174 ms 166 ms te9-1.dsr01.dllstx3.networklayer.com [70.87.253.
6]
14 * * * Request timed out.
15 168 ms 179 ms 169 ms po1.car08.dllstx2.networklayer.com [70.87.254.13
0]
16 171 ms 160 ms 169 ms 29.64.5d45.static.theplanet.com [69.93.100.41]

Trace complete.


This next one is from home where TCC times out:

Tracing route to tokyocycling.com [69.93.100.41]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms . [192.168.11.1]
2 * * * Request timed out.
3 5 ms 5 ms 5 ms 219.110.7.133
4 5 ms 6 ms 6 ms 219.110.0.45
5 5 ms 5 ms 5 ms brtkote11.bb.itscom.jp [219.110.0.245]
6 5 ms 6 ms 6 ms Te4-4-403.gw2.nrt2.asianetcom.net [203.192.150.1
25]
7 6 ms 6 ms 6 ms gi0-0-0.cr1.nrt1.asianetcom.net [202.147.1.62]
8 109 ms 109 ms 110 ms po7-0-0.gw1.sjc1.asianetcom.net [202.147.0.34]
9 111 ms 111 ms 111 ms eq-sanjose-10G.theplanet.com [206.223.116.148]
10 150 ms 150 ms 150 ms e8-1.ibr04.dllstx3.networklayer.com [70.87.253.1
94]
11 151 ms 151 ms 163 ms te7-2.dsr01.dllstx3.networklayer.com [70.87.253.
10]
12 * * * Request timed out.
13 151 ms 151 ms 151 ms po1.car08.dllstx2.networklayer.com [70.87.254.13
0]
14 151 ms 150 ms 150 ms 29.64.5d45.static.theplanet.com [69.93.100.41]

Trace complete.
 

thomas

The Crank Engine
Nov 1, 2005
1,799
203
93
多摩区
#12
Aaron, you still seem to be caching the DNS info of our old server (theplanet.com).

Here's a tracert from my box:

Tracing route to tokyocycle.com [72.11.141.66]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.11.1
2 * * * Request timed out.
3 9 ms 12 ms 12 ms 10.202.107.3
4 11 ms 11 ms 9 ms 172.25.108.29
5 10 ms 14 ms 11 ms c1-t0-2-0-0.kdd1.nap.home.ad.jp [220.152.42.161]

6 16 ms 27 ms 15 ms c5-t0-6-0-0.kdd1.nap.home.ad.jp [203.165.0.110]

7 * * * Request timed out.
8 126 ms 128 ms 123 ms 10gigabitethernet3-3.core1.sjc2.he.net [72.52.92
.237]
9 136 ms 131 ms 136 ms 10gigabitethernet3-1.core1.lax2.he.net [184.105.
213.6]
10 131 ms 124 ms 125 ms 216.218.230.86
11 133 ms 127 ms 127 ms lax6-r2.quadranet.com [216.144.225.242]
12 129 ms 125 ms 125 ms koto.japanref.com [72.11.141.66]

Trace complete.
 

Pucci

Speeding Up
Jul 12, 2006
283
1
38
Yokohama
#13
Thomas, what is really odd is that I am getting theplanet.com from the office where I can access TCC fine. Also I still get theplanet.com after flushing my DNS resolver cache.

This means that the caching is not local. I wonder if your provider has messed up the DNS entries somehow.

Aaron
 

trad

Maximum Pace
Dec 4, 2006
393
30
48
Tokyo
#14
ok with Pucci's suggestion, I can get the trace results to stay up in a window, but cannot copy the text (yes I'm pretty ignorant when it comes to PC).

For what ever its worth, my trace goes like this:
1-4 hops around rosenet sites (my ISP)
6 otejbb204.kddnet.ad.jp
7 pacbb002.kddnet.ad.jp
8 ix-sj1.kddnet.ad.jp
9 ae0-9.sjc10.ip.tiscali.net
10 xe-9-0-0.lax20.ip4.timenet.net
11 quadranet-gw.ip4.timenet.net12 96.44.180.38
13 koto.japanref.com


as for flushing cache, this makes no difference and neither does rebooting
 

Pucci

Speeding Up
Jul 12, 2006
283
1
38
Yokohama
#16
Bumping this back up. TCC remains almost impossible for me, since I can only access it at work.

Can anything be done? Anyone else having this issue since the server move (three reported so far.)
 

Newton

Senior Cyclist
Feb 15, 2006
127
0
36
Tokyo
www.fotolog.com
#17
Hello guys!
I am back after long time. :)

Hi Pucci,
It's looks like the problem is the DNS client that you are using. Somethimes the administrators does not set the TTL (time to live) into the DNS server and the old domain names never release from their the cache.
Just try to use different DNS client into your PC, you can set this manually.
Try to use 8.8.8.8 or 4.2.2.2.

Newton
 

Newton

Senior Cyclist
Feb 15, 2006
127
0
36
Tokyo
www.fotolog.com
#19
Newton, I have reduced the SOA Expire from 3600000 to 86400. Not sure if it's made any difference so far.
Hi Thomas,
humm interesting...I thought it was already at 86400. so the original value was 3600000 seconds. so that means 41 days. :confused:
so we have to wait 41 days to clear completely from all DNS Server. Some DNS server ignore this value and it always reflesh the DNS cache but some NOT.
So that why some users can access and some have issue.

Your Service Provider should have warned about this and change this value to "86400" 41 days before you move to new location.

Anyway, I think we have few more days to reach 41 days. so after 42 days all access should be fine. :rolleyes:

When did you change the SOA value?

Newton
 

trad

Maximum Pace
Dec 4, 2006
393
30
48
Tokyo
#20
problem stil there. flushing dns cache does not seem to help either

my trace tonight was
1-4 hops around rosenet sites (my ISP)
6 otejbb204.kddnet.ad.jp
7 pacbjbb002.kddnet.ad.jp
8 ix-sj1.kddnet.ad.jp
9 ae0-9.sjc10.ip.tiscali.net
10 xe-9-0-0.lax20.ip4.timenet.net
11 quadranet-gw.ip4.timenet.net12 96.44.180.38
13 koto.japanref.com