Unable to visit certain websites (depending on IP address)

The_Unbeliever · Aug 11, 2011

Heyup

I've picked up an intermittent connection to chroniclesofgeorge.com

When connected with CellC I'm unable to access CoG 90% of the time, and get the dreaded "connection timed out" error.

Tracert from CellC connection :

Code:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\>ping chroniclesofgeorge.com

Pinging chroniclesofgeorge.com [184.72.224.251] with 32 bytes of data:

Control-C
^C

C:\>tracert chroniclesofgeorge.com

Tracing route to chroniclesofgeorge.com [184.72.224.251]
over a maximum of 30 hops:

  1    66 ms    39 ms    39 ms  41.48.20.20
  2    47 ms    39 ms    39 ms  41.48.23.25
  3    38 ms    39 ms    39 ms  10.228.221.43
  4    47 ms    49 ms    49 ms  10.228.223.70
  5    39 ms    39 ms    39 ms  41.48.16.1
  6    58 ms    39 ms    39 ms  41.48.0.3
  7   258 ms   260 ms   259 ms  83.231.233.141
  8   348 ms   329 ms   339 ms  as-0.r22.nycmny01.us.bb.gin.ntt.net [129.250.3.2
54]
  9   328 ms   339 ms   329 ms  ae-0.r23.nycmny01.us.bb.gin.ntt.net [129.250.3.7
3]
 10   334 ms   339 ms   338 ms  ae-1.r20.asbnva02.us.bb.gin.ntt.net [129.250.2.9
]
 11   342 ms   339 ms   339 ms  ae-1.r01.asbnva02.us.bb.gin.ntt.net [129.250.3.1
1]
 12   349 ms   358 ms   340 ms  xe-0-4-0-4.r01.asbnva02.us.ce.gin.ntt.net [168.1
43.232.46]
 13   348 ms   340 ms   349 ms  72.21.220.67
 14   348 ms   329 ms   329 ms  72.21.222.155
 15   338 ms   336 ms   339 ms  216.182.224.55
 16     *        *      337 ms  216.182.232.27
 17     *      367 ms   389 ms  216.182.232.131
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

But, when I'm connected via VPN (work) then I'm able to access it 100% of the time, no funny problems, or time outs.

Tracert from VPN connection to work :

Code:

C:\>ping chroniclesofgeorge.com

Pinging chroniclesofgeorge.com [184.72.224.251] with 32 bytes of data:

Request timed out.

Ping statistics for 184.72.224.251:
    Packets: Sent = 1, Received = 0, Lost = 1 (100% loss),
Control-C
^C
C:\>tracert chroniclesofgeorge.com

Tracing route to chroniclesofgeorge.com [184.72.224.251]
over a maximum of 30 hops:

  1    86 ms    59 ms    59 ms  192.168.50.149
  2    58 ms    59 ms    59 ms  192.168.50.250
  3    68 ms    59 ms    59 ms  192.168.50.252
  4   319 ms   129 ms    49 ms  196.211.108.65
  5    77 ms    69 ms    59 ms  196.211.229.113
  6   128 ms    89 ms    69 ms  cdsl1-rba-vl144.isdsl.net [196.35.63.65]
  7    88 ms    68 ms   129 ms  core1b-rba-te2-0-1.ip.isnet.net [168.209.1.181]

  8   308 ms   299 ms   299 ms  mi-za-rba-p5-gi2-0-2.ip.isnet.net [168.209.164.9
7]
  9   298 ms   300 ms   289 ms  mi-uk-dock-p3-gi3-1-1.ip.isnet.net [168.209.161.
80]
 10   298 ms   299 ms   299 ms  core1a-dock-gi1-0-17.ip.isnet.net [168.209.164.2
04]
 11   298 ms   289 ms   299 ms  168.209.246.66
 12   298 ms   309 ms   319 ms  195.50.124.33
 13   288 ms   290 ms   309 ms  ae-34-52.ebr2.London1.Level3.net [4.69.139.97]
 14   368 ms   360 ms   369 ms  ae-42-42.ebr1.NewYork1.Level3.net [4.69.137.70]

 15   377 ms   379 ms   360 ms  ae-4-4.ebr1.NewYork2.Level3.net [4.69.141.18]
 16   378 ms   372 ms   415 ms  ae-3-3.ebr2.Washington1.Level3.net [4.69.132.89]

 17   363 ms   359 ms   369 ms  ae-72-72.csw2.Washington1.Level3.net [4.69.134.1
50]
 18   358 ms   369 ms   379 ms  ae-2-70.edge3.Washington1.Level3.net [4.69.149.8
1]
 19   378 ms   369 ms   379 ms  AMAZON.COM.edge3.Washington1.Level3.net [4.59.14
4.86]
 20   368 ms   369 ms   359 ms  72.21.220.141
 21   378 ms   499 ms   389 ms  72.21.222.147
 22   378 ms   359 ms   370 ms  216.182.232.49
 23   389 ms   389 ms   379 ms  216.182.232.65
 24   368 ms   379 ms   369 ms  216.182.232.125
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

C:\>

Do let know what else I can do in order to provide more information.

Regards

Ook

ginggs · Aug 13, 2011

Working for me on Cell-C.

My traceroute looks much like your first one:

Code:

>tracert chroniclesofgeorge.com

Tracing route to chroniclesofgeorge.com [184.72.224.251]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
  2    89 ms    97 ms   109 ms  41.157.83.14
  3    96 ms    89 ms    59 ms  10.0.238.36
  4   139 ms    65 ms    77 ms  41.157.83.14
  5    77 ms    78 ms    79 ms  41.157.72.3
  6    79 ms   254 ms   140 ms  41.157.64.3
  7    93 ms   111 ms   135 ms  41.48.253.34
  8   325 ms   299 ms   330 ms  83.231.233.141
  9   406 ms   405 ms   389 ms  as-0.r22.nycmny01.us.bb.gin.ntt.net [129.250.3.254]
 10   528 ms   377 ms   409 ms  ae-0.r23.nycmny01.us.bb.gin.ntt.net [129.250.3.73]
 11   410 ms   399 ms   498 ms  ae-1.r20.asbnva02.us.bb.gin.ntt.net [129.250.2.9]
 12   390 ms   404 ms   389 ms  ae-1.r01.asbnva02.us.bb.gin.ntt.net [129.250.3.11]
 13   406 ms   405 ms   405 ms  xe-0-4-0-5.r01.asbnva02.us.ce.gin.ntt.net [168.143.232.50]
 14   405 ms   405 ms   405 ms  72.21.220.63
 15   406 ms   420 ms   406 ms  72.21.222.149
 16   405 ms   405 ms   405 ms  216.182.232.51
 17   389 ms   390 ms   404 ms  216.182.232.67
 18   406 ms   420 ms     *     216.182.232.131
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

The_Unbeliever · Aug 14, 2011

@ginggs - you haven't got any issues connecting to CoG on your side?

Weird.

ginggs · Aug 14, 2011

The_Librarian said:
@ginggs - you haven't got any issues connecting to CoG on your side?

Weird.

Just tried again now, still working.

GreGorGy · Aug 21, 2011

Current Profile - Cell C
MCC (Country): 655
MNC (Network): 07
RSSI (Raw / dBm) 10 / -93dBm
LAC: 50
Cell ID: 0-19863

ME Profile - huawei

For like a week now, Cell C connection cannot see www.freeverse.com

Try it on any other, no problem.

GreGorGy · Aug 24, 2011

GreGorGy said:
Current Profile - Cell C
MCC (Country): 655
MNC (Network): 07
RSSI (Raw / dBm) 10 / -93dBm
LAC: 50
Cell ID: 0-19863

ME Profile - huawei

For like a week now, Cell C connection cannot see www.freeverse.com

Try it on any other, no problem.

SERIOUSLY!

This persists - any other connection (MTN, Voda, ADSL) all see that site - just not Cell C. Any ideas rep?

ginggs · Aug 24, 2011

GreGorGy said:
SERIOUSLY!

This persists - any other connection (MTN, Voda, ADSL) all see that site - just not Cell C. Any ideas rep?

Would you believe it? I have no problems accessing that site either.
Cell ID: 40541
Device: Nokia N900

edit: chroniclesofgeorge.com still working for me too

w1z4rd · Aug 24, 2011

Im on cellc and can access chroniclesofgeorge.com but not freeverse.com.

Glipsie · Aug 24, 2011

ghoti said:
Im on cellc and can access chroniclesofgeorge.com but not freeverse.com.

Ditto

The_Unbeliever · Aug 25, 2011

I still have the issue with CoG.

What happens is that I'm able to browse normally, but when I reply to a post, or post a reply, then I get a timeout error.

ginggs · Aug 25, 2011

The_Librarian said:
What happens is that I'm able to browse normally, but when I reply to a post, or post a reply, then I get a timeout error.

I only browsed the site, I didn't try posting or replying.

Cell_C · Aug 25, 2011

The_Librarian said:
I still have the issue with CoG.

What happens is that I'm able to browse normally, but when I reply to a post, or post a reply, then I get a timeout error.

Hi The_Librarian

Are you on unrestricted ?

Regards
~AM~

The_Unbeliever · Aug 26, 2011

Cell_C said:
Hi The_Librarian

Are you on unrestricted ?

Regards
~AM~

I will test this weekend when things are not rushed. Will do a lot of tests etc then post them here.

If you want me to do some tests, please do let me know so that I can include these as well

Thanks

ajax · Sep 10, 2011

freeverse.com not working on 197 IP range

I'm on Cell C prepaid 5 GB with a normal APN using the E1820 and MR3420 router.

Did a few tests just now. By manually disconnecting and reconnecting a few times the IP address can be "changed". The status page of my router shows my IP address.
(Those without routers, you can use whatismyip.com)

With IP address starting with 197.171.xx.xx I could NOT access freeverse.com
With IP address starting with 41.xx I was able to access freeverse.com

I repeated the test to be sure.

With IP address in the 197 range:
Tracing route to freeverse.com [216.220.102.10]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.6
2 * * * Request timed out.
3 92 ms 99 ms 99 ms 41.157.83.14
4 98 ms 99 ms 99 ms 10.0.238.42
5 97 ms 99 ms 100 ms 41.157.83.14
6 99 ms 99 ms 99 ms 41.157.72.3
7 97 ms 129 ms 99 ms 41.157.64.3
8 118 ms 99 ms 109 ms 41.48.253.34
9 318 ms 339 ms 319 ms 83.231.233.141
10 327 ms 319 ms 319 ms ae-1.r02.londen03.uk.bb.gin.ntt.net [129.250.5.25]
11 297 ms 289 ms 310 ms xe-0.level3.londen03.uk.bb.gin.ntt.net [129.250.8.138]
12 289 ms 279 ms 319 ms ae-34-52.ebr2.London1.Level3.net [4.69.139.97]
13 387 ms 359 ms 359 ms ae-44-44.ebr1.NewYork1.Level3.net [4.69.137.78]
14 374 ms 369 ms 369 ms ae-71-71.csw2.NewYork1.Level3.net [4.69.134.70]
15 418 ms 399 ms 369 ms ae-24-70.car4.NewYork1.Level3.net [4.69.155.70]
16 378 ms 359 ms 379 ms CO-LOCATION.car4.NewYork1.Level3.net [4.53.92.74]
17 * * * Request timed out.
[[ further time-outs truncated by me ]]

Using a 41 IP range I get:

Tracing route to freeverse.com [216.220.102.10]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.6
2 * * * Request timed out.
3 95 ms 109 ms 99 ms 41.48.23.25
4 108 ms 100 ms 99 ms 10.228.221.47
5 98 ms 129 ms 99 ms 10.228.223.70
6 108 ms 149 ms 99 ms 41.48.16.1
7 98 ms 99 ms 99 ms 41.48.0.3
8 308 ms 319 ms 319 ms 83.231.233.141
9 318 ms 319 ms 319 ms ae-1.r02.londen03.uk.bb.gin.ntt.net [129.250.5.25]
10 326 ms 339 ms 319 ms xe-0.level3.londen03.uk.bb.gin.ntt.net [129.250.8.138]
11 307 ms 299 ms 299 ms ae-34-52.ebr2.London1.Level3.net [4.69.139.97]
12 388 ms 389 ms 388 ms ae-44-44.ebr1.NewYork1.Level3.net [4.69.137.78]
13 407 ms 399 ms 399 ms ae-71-71.csw2.NewYork1.Level3.net [4.69.134.70]
14 397 ms 389 ms 399 ms ae-24-70.car4.NewYork1.Level3.net [4.69.155.70]
15 408 ms 399 ms 399 ms CO-LOCATION.car4.NewYork1.Level3.net [4.53.92.74]
16 * * * Request timed out.
17 * * * Request timed out.

[[ truncated ]]

Not sure why I get a time-out on the 2nd hop. Nevertheless, I can't spot much a difference in the tracert's for the 2 IP ranges.

Anyone with more insight?

ginggs · Sep 10, 2011

Tcptraceroute works on a similar principle to a regular traceroute except it uses TCP packets (port 80 by default) instead of ICMP packets. I was unable to find a working equivalent for Windows, below are the results running on Ubuntu:

Code:

$ tcptraceroute freeverse.com
Selected device ppp0, address 41.54.14.202, port 47240 for outgoing packets
Tracing the path to freeverse.com (216.220.102.10) on TCP port 80 (www), 30 hops max
 1  * * *
 2  41.48.23.25  86.869 ms  95.961 ms  89.944 ms
 3  10.228.223.70  89.915 ms  89.890 ms  139.919 ms
 4  41.48.16.1  109.971 ms  72.121 ms  79.908 ms
 5  41.48.0.3  79.906 ms  1982.165 ms  179.804 ms
 6  83.231.233.141  309.916 ms  305.982 ms
    41.48.0.3  79.928 ms
 7  83.231.233.141  317.132 ms  316.087 ms  319.901 ms
 8  ae-1.r02.londen03.uk.bb.gin.ntt.net (129.250.5.25)  314.538 ms  309.856 ms  309.907 ms
 9  xe-0.level3.londen03.uk.bb.gin.ntt.net (129.250.8.138)  369.894 ms  409.964 ms  309.826 ms
10  ae-34-52.ebr2.London1.Level3.net (4.69.139.97)  299.938 ms  289.891 ms  289.889 ms
11  ae-44-44.ebr1.NewYork1.Level3.net (4.69.137.78)  389.926 ms  399.902 ms  379.831 ms
12  ae-91-91.csw4.NewYork1.Level3.net (4.69.134.78)  409.951 ms  399.877 ms  399.911 ms
13  ae-44-90.car4.NewYork1.Level3.net (4.69.155.198)  569.932 ms  529.867 ms  409.910 ms
14  CO-LOCATION.car4.NewYork1.Level3.net (4.53.92.74)  399.969 ms  389.871 ms  389.910 ms
15  www.freeverse.com (216.220.102.10) [open]  380.150 ms  379.841 ms  389.909 ms

Code:

$ tcptraceroute freeverse.com
Selected device ppp0, address 197.173.233.32, port 43098 for outgoing packets
Tracing the path to freeverse.com (216.220.102.10) on TCP port 80 (www), 30 hops max
 1  * * *
 2  41.157.83.14  98.770 ms  85.944 ms  89.888 ms
 3  41.157.83.14  99.933 ms  86.999 ms  79.876 ms
 4  41.157.72.3  89.967 ms  1955.968 ms  99.918 ms
 5  41.157.64.3  99.892 ms  115.962 ms  99.898 ms
 6  41.48.253.34  99.970 ms  87.247 ms  99.910 ms
 7  83.231.233.141  319.912 ms  2115.038 ms  319.944 ms
 8  ae-1.r02.londen03.uk.bb.gin.ntt.net (129.250.5.25)  319.923 ms  319.880 ms  309.905 ms
 9  xe-0.level3.londen03.uk.bb.gin.ntt.net (129.250.8.138)  339.914 ms  319.884 ms  319.877 ms
10  ae-34-52.ebr2.London1.Level3.net (4.69.139.97)  299.949 ms  299.840 ms  299.903 ms
11  ae-42-42.ebr1.NewYork1.Level3.net (4.69.137.70)  389.902 ms  389.857 ms  379.902 ms
12  ae-61-61.csw1.NewYork1.Level3.net (4.69.134.66)  409.888 ms  399.868 ms  389.878 ms
13  ae-14-60.car4.NewYork1.Level3.net (4.69.155.6)  399.917 ms  389.850 ms  389.921 ms
14  CO-LOCATION.car4.NewYork1.Level3.net (4.53.92.74)  399.919 ms  389.845 ms
    ae-14-60.car4.NewYork1.Level3.net (4.69.155.6)  389.920 ms
15  CO-LOCATION.car4.NewYork1.Level3.net (4.53.92.74)  389.881 ms  389.821 ms  389.945 ms
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
Destination not reached

ajax · Sep 10, 2011

@Ginggs, is it correct to say then you also can't access freeverse on the 197 IP range?

ginggs · Sep 10, 2011

ajax said:
@Ginggs, is it correct to say then you also can't access freeverse on the 197 IP range?

Yes, I should have made that clear.

When my IP address was 41.54.14.202 I could access http://freeverse.com, when my IP address was 197.173.233.32 the connection timed out.

It seems tracetcp in conjunction with WinPcap is a suitable equivalent of tcptraceroute for Windows, although only if you are using a router. Not sure if it doesn't like the Huawei modem drivers or the RAS connection.

ginggs · Sep 11, 2011

Cell-C are investigating.

Cell_C · Sep 12, 2011

Hi all

first, thank you all for the info and testing info.
ginggs has brought it to our attention, we are looking in to it.
thank you for your understanding.

Regards
~AM~

ginggs · Sep 18, 2011

I'm still unable to access http://freeverse.com if I get a 197.x address, it works fine if I get a 41.x address.

Are there any other sites that this happens with?

Unable to visit certain websites (depending on IP address)

Honorary Master

༼ つ ◕_◕ ༽つ

Honorary Master

༼ つ ◕_◕ ༽つ

BULLSFAN

BULLSFAN

༼ つ ◕_◕ ༽つ

Karmic Sangoma

Senior Member

Honorary Master

༼ つ ◕_◕ ༽つ

Cell C Representative

Honorary Master

Executive Member

༼ つ ◕_◕ ༽つ

Executive Member

༼ つ ◕_◕ ༽つ

༼ つ ◕_◕ ༽つ

Cell C Representative

༼ つ ◕_◕ ༽つ