I have a customer who uses Pac Bell DSL for her ISP -- she is having trouble accessing her website (see the Pac Bell tracert) but I have been able to access the site using 4 different ISPs (tracerts below). Pac Bell denies they are having any network problems that would prevent her from accessing the site. Any ideas?


Pac Bell

C:\WINDOWS>tracert guileless.net

Tracing route to guileless.net [216.87.208.57]
over a maximum of 30 hops:


1 18 ms 31 ms 22 ms adsl-63-204-107-254.dsl.sndg02.pacbell.net[63.204.107.254]
2 16 ms 20 ms 18 ms core1-fe0-1-0.sndg02.pbi.net [63.200.206.193]
3 17 ms 19 ms 19 ms bb1-g6-0.sndg02.pbi.net [206.13.30.6]
4 21 ms 24 ms 22 ms sl-gw23-ana-2-1.sprintlink.net [160.81.103.9]
5 20 ms 22 ms 22 ms sl-bb20-ana-12-0.sprintlink.net [144.232.1.215]
6 23 ms 25 ms 23 ms sl-intsys-6-0-0.sprintlink.net [144.228.179.226]
7 22 ms 22 ms 24 ms pos4-0-622M.wr2.LAX1.gblx.net [206.132.112.101]
8 55 ms 55 ms 55 ms pos3-0-2488M.wr1.HOU1.gblx.net [206.132.114.81]
9 55 ms 56 ms 56 ms pos0-0-622M.cr1.HOU1.gblx.net [206.132.116.82]
10 100 ms 102 ms 102 ms pos0-0-155M.ar1.TPA1.gblx.net [206.132.116.98]
11 * 82 ms 85 ms cust.s4-0-0.ar1.TPA1.gblx.net [64.209.252.62]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.

AT&T

C:\WINDOWS>tracert guileless.net

Tracing route to guileless.net [216.87.208.57]
over a maximum of 30 hops:

1 170 ms 180 ms 160 ms 199.69.195.40
2 142 ms 159 ms 159 ms 1.detroit-06-07rs.mi.dial-access.att.net [12.76.
66.1]
3 146 ms 160 ms 154 ms br2-h30.cb1ma.ip.att.net [12.127.12.77]
4 180 ms 154 ms 160 ms gbr1-p70.dtrmi.ip.att.net [12.123.139.22]
5 170 ms 160 ms 180 ms gbr4-p30.cgcil.ip.att.net [12.122.2.194]
6 272 ms 174 ms 180 ms gbr3-p60.cgcil.ip.att.net [12.122.1.125]
7 198 ms 177 ms 167 ms gbr3-p10.n54ny.ip.att.net [12.122.2.1]
8 266 ms 174 ms 196 ms gbr3-p10.wswdc.ip.att.net [12.122.3.54]
9 235 ms 247 ms 182 ms gbr4-p60.wswdc.ip.att.net [12.122.1.130]
10 184 ms 200 ms 201 ms gbr4-p30.attga.ip.att.net [12.122.2.225]
11 240 ms 217 ms 340 ms gbr3-p60.attga.ip.att.net [12.122.1.141]
12 198 ms 220 ms 240 ms gbr4-p50.ormfl.ip.att.net [12.122.2.130]
13 205 ms 322 ms 214 ms gbr2-p100.ormfl.ip.att.net [12.122.5.134]
14 2232 ms 519 ms 1242 ms ar3-a300s2.ormfl.ip.att.net [12.127.3.37]
15 218 ms 220 ms 240 ms 12.126.159.94
16 742 ms 1161 ms 438 ms guileless.net [216.87.208.57]

Trace complete.

MICROSOFT NETWORK

C:\WINDOWS>tracert guileless.net

Tracing route to guileless.net [216.87.208.57]
over a maximum of 30 hops:

1 158 ms 160 ms 142 ms tnt50.det3.da.uu.net [204.177.254.2]
2 122 ms 142 ms 139 ms 207.76.49.2
3 158 ms 160 ms 160 ms 155.at-1-1-0.XR2.CHI4.ALTER.NET [152.63.65.190]

4 160 ms 160 ms 160 ms 160.at-5-0-0.XR1.CHI2.ALTER.NET [152.63.68.50]
5 158 ms 160 ms 160 ms 0.so-3-0-0.TR1.CHI2.ALTER.NET [152.63.15.86]
6 158 ms 160 ms 160 ms 126.at-5-1-0.TR1.ATL5.ALTER.NET [152.63.0.117]
7 178 ms 156 ms 160 ms 0.so-4-0-0.XR1.ATL5.ALTER.NET [152.63.9.226]
8 162 ms 174 ms 180 ms 193.ATM4-0.GW2.MIA4.ALTER.NET [146.188.233.177]

9 176 ms 240 ms 180 ms 157.130.85.230
10 177 ms 180 ms 180 ms guileless.net [216.87.208.57]

Trace complete.

AMERICA ONLINE

C:\WINDOWS>tracert guileless.net

Tracing route to guileless.net [216.87.208.57]
over a maximum of 30 hops:

1 224 ms 372 ms 865 ms ipt-mc05.proxy.aol.com [64.12.104.94]
2 1283 ms 380 ms 671 ms tot4-mc3-G4-0.proxy.aol.com [64.12.104.124]
3 * 1448 ms 1091 ms wc2-mc3-P4-1.aol.com [64.12.130.61]
4 1396 ms 2366 ms 191 ms pop2-mtc-P3-0.atdn.net [204.148.102.189]
5 170 ms 220 ms 220 ms bb1-mtc-P14-0.atdn.net [204.148.101.205]
6 208 ms 220 ms 220 ms bb1-rtc-P8-0.atdn.net [204.148.99.149]
7 194 ms 219 ms 220 ms pop2-rtc-P14-0.atdn.net [204.148.103.46]
8 194 ms 351 ms 198 ms tbd-att2.atdn.net [204.148.99.6]
9 180 ms 210 ms 220 ms gbr4-p100.wswdc.ip.att.net [12.122.5.198]
10 308 ms 214 ms 222 ms gbr4-p90.attga.ip.att.net [12.122.2.177]
11 202 ms 220 ms 220 ms gbr3-p60.attga.ip.att.net [12.122.1.141]
12 220 ms 261 ms 222 ms gbr4-p50.ormfl.ip.att.net [12.122.2.130]
13 260 ms 216 ms 222 ms gbr1-p90.ormfl.ip.att.net [12.122.5.126]
14 212 ms 220 ms 217 ms ar3-a300s3.ormfl.ip.att.net [12.123.32.41]
15 205 ms 219 ms 222 ms 12.126.159.94
16 274 ms 219 ms 219 ms guileless.net [216.87.208.57]

Trace complete.

TELOCITY


C:\WINDOWS>tracert guileless.net

Tracing route to guileless.net [216.87.208.57]
over a maximum of 30 hops:

1 1 ms 2 ms 1 ms dsl-64-193-155-218.telocity.com [64.193.155.218]

2 43 ms 32 ms 32 ms route-64-193-187-1.telocity.com [64.193.187.1]
3 45 ms 33 ms 93 ms fe1-2-core1.chi.tlct.net [216.227.0.129]
4 84 ms 79 ms 68 ms pos8-1-hfr2.den.tlct.net [216.227.126.5]
5 81 ms 79 ms 68 ms ge-v5-hfr1.den.tlct.net [216.227.126.77]
6 218 ms 99 ms 97 ms pos8-1-hfr1.sjc.tlct.net [216.227.126.1]
7 109 ms 96 ms 98 ms pos2-1-paix.pao.tlct.net [216.227.126.210]
8 109 ms 95 ms 98 ms gblx-px.pao.tlct.net [64.192.16.14]
9 109 ms 95 ms 98 ms so1-0-0-622M.cr1.pao2.gblx.net [208.50.169.141]

10 160 ms 146 ms 141 ms pos1-0-622M.cr1.HOU1.gblx.net [206.132.116.126]

11 146 ms 128 ms 136 ms pos0-0-155M.ar1.TPA1.gblx.net [206.132.116.98]
12 158 ms 221 ms 262 ms cust.s4-0-0.ar1.TPA1.gblx.net [64.209.252.62]
13 188 ms 139 ms 136 ms guileless.net [216.87.208.57]

Trace complete.

Given that the first tracert ends at the last router before the destination (compare to the last tracert) I'd guess that she is being firewalled by the destination network. It certainly isn't a problem at pacbell.net since the requests get far out of that network.

I have a soltuion for your client. Email me at
j.ferro@cais.com

I am haveing the same problem. My server located in 4webspace. My customer in thailand could not call my server becaue there is a bug in Teleglobe hop

Below is a traceroute from 4webspace to an isp in thailand (ksc.net.th )

traceroute to www.ksc.net.th (203.155.240.237), 30 hops max, 40 byte packets
1 192.168.7.1 (192.168.7.1) 0.604 ms 0.398 ms 0.359 ms
2 cat6006-vlan27.edm.tera-byte.com (216.234.160.53) 1.020 ms 0.778 ms 0.649 ms
3 telus-gw.edm.tera-byte.com (216.234.160.21) 0.889 ms 1.169 ms 1.018 ms
4 209.115.219.237 (209.115.219.237) 1.605 ms 1.988 ms 1.894 ms
5 205.233.111.34 (205.233.111.34) 2.086 ms 2.481 ms 2.637 ms
6 205.233.111.221 (205.233.111.221) 9.013 ms 5.113 ms 5.187 ms
7 inetgw4-pos1.bctel.net (204.174.218.38) 20.734 ms 17.681 ms 18.325 ms
8 inetgw3-i4.bctel.net (209.53.75.61) 20.745 ms 20.856 ms 20.273 ms
9 if-1-0-3.bb2.Burnaby.Teleglobe.net (207.45.209.5) 51.061 ms 51.264 ms 50.364 ms
10 if-5-0.core1.Burnaby.Teleglobe.net (207.45.204.65) 51.054 ms 50.807 ms 50.837 ms
11 if-1-0.core2.LakeCowichan.Teleglobe.net (207.45.223.174) 53.629 ms 52.972 ms 53.078 ms
12 if-5-0-0.bb3.LakeCowichan.Teleglobe.net (64.86.83.40) 53.836 ms 53.978 ms 53.821 ms
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

I know hop 13 is ix-10-0-1.bb3.lakecowichan.teleglobe.net (64.86.84.62) . pinging to this hop show nothing strange. Anybody know what happen? Or only God knows ? Can i ask 4webspace or www.ksc.net.th to change routing table ?

I am currently encountering the same problem. Please let me know the workaround of this situation. Thanks