Once again I am retiring the old network performance thread and starting a new one.

All too frequently we see posts we would like to troubleshoot, but do not have all of the information.
Always post:
a) the exact source IP having trouble (client workstation?)
b) the exact destination IP (your server?)
c) an inbound traceroute from/to the source and destinations above

Also useful:
d) outbound traceroute from your server
e) your diagnostic output (ping tests, screenshots, logs, etc.)

We will 'field' the issues in this thread whenever possible, but remember that the OFFICIAL avenue to resolve network issues is the EV1servers trouble ticket system...

My sincere thanks,

Randy Williams, CTO

Source IP: 81.134.215.23
Destination 1: 64.246.36.31

Source to Destination 1:
=======
1 <10 ms <10 ms <10 ms 192.168.0.1
2 10 ms 20 ms 20 ms btdhg519-hg3.ealing.broadband.bt.net [217.47.133
.202]
3 10 ms 20 ms 20 ms 217.47.133.161
4 20 ms 20 ms 10 ms 217.47.133.238
5 70 ms 71 ms 20 ms inh3cs01-500.imsnet3.btopenworld.com [213.1.119.
61]
6 10 ms 20 ms 80 ms btfl03-gig8-7.imsnet3.btopenworld.com [213.1.119
.153]
7 20 ms 20 ms 20 ms core1-pos12-1.ealing.ukcore.bt.net [194.72.9.197
]
8 10 ms 20 ms 70 ms core1-pos10-0.redbus.ukcore.bt.net [194.74.65.25
4]
9 90 ms 100 ms 90 ms lndnuk1icx1.wcg.net [195.66.224.105]
10 130 ms 120 ms 140 ms nycmny2wcx2-pos15-3.wcg.net [64.200.87.61]
11 * * * Request timed out.
12 * * * Request timed out.
====

Traceroute from Destination 1 to source (bounced via another RS server) [note: different route avoiding WCG!]
==========
traceroute to 81.134.215.23 (81.134.215.23), 30 hops max, 38 byte packets
1 64.246.36.1 (64.246.36.1) 8.608 ms 0.727 ms 0.485 ms
2 ivhou-207-218-245-9.ev1.net (207.218.245.9) 0.563 ms 0.531 ms *
3 289.ge-3-2-0.mpr2.iah1.us.mfnx.net (216.200.251.51) 1.297 ms 1.263 ms 1.1
00 ms
4 pos-10-0.er1.atl4.us.above.net (64.125.29.65) 14.388 ms 14.344 ms *
5 pos14-0.pr1.atl4.us.above.net (64.125.30.242) 14.191 ms 14.155 ms 14.791
ms
6 so-5-0-0.cr2.dca2.us.mfnx.net (208.185.0.229) 25.942 ms 25.357 ms 25.303
ms
7 * so-6-0-0.cr1.lhr3.uk.above.net (64.125.31.185) 96.880 ms 97.162 ms
8 so-0-0-0.cr2.lhr3.uk.above.net (208.184.231.146) 96.926 ms 97.015 ms 96.8
69 ms
9 pos1-0.mpr2.lhr1.uk.above.net (208.185.156.1) 96.962 ms 96.958 ms 97.019
ms
10 core2-gig9-0.telehouse.ukcore.bt.net (208.185.156.218) 96.999 ms 97.071 ms
96.858 ms
11 core2-pos14-0.ealing.ukcore.bt.net (194.74.65.122) 97.653 ms 97.825 ms 97
.778 ms
12 * * *
13 inh3cs02-454.imsnet3.btopenworld.com (213.1.119.158) 105.524 ms 105.414 ms
106.129 ms
14 * * *
15 bthg519.imsnet3.btopenworld.com (213.1.119.19) 105.229 ms 105.166 ms 104.
810 ms
16 * * *
==========

Destination 2: 69.57.152.68

Traceroute from source to destination:
==========
1 <10 ms <10 ms <10 ms 192.168.0.1
2 10 ms 20 ms 21 ms btdhg519-hg3.ealing.broadband.bt.net [217.47.133
.202]
3 10 ms 20 ms 20 ms 217.47.133.130
4 20 ms 10 ms 10 ms 217.47.133.238
5 10 ms 20 ms 20 ms inh3cs01-500.imsnet3.btopenworld.com [213.1.119.
61]
6 50 ms 20 ms 20 ms ftip002613901.interconnect5.ealing.fixed-nte.bt.
net [213.1.119.161]
7 10 ms 10 ms 20 ms core1-pos4-3.ealing.ukcore.bt.net [194.72.9.241]

8 20 ms 20 ms 20 ms core1-pos5-0.telehouse.ukcore.bt.net [194.74.65.
129]
9 90 ms 100 ms 90 ms lndnuk1icx1.wcg.net [195.66.224.105]
10 90 ms 101 ms 90 ms nycmny2wcx2-oc12.wcg.net [64.200.87.149]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
==========

Problem appears to be in WCG somewhere.

Source: 82.133.123.12 [asunawa.gotadsl.co.uk] (Nildram UK, Static IP)
Destination: 216.40.217.24 [www.qshosting.com] (server)

Traceroute
1 2 10.0.0.2
2 53 81.6.205.65 (lon1-adsl9-2.nildram.net)
3 59 213.208.106.194 (lon1-9.nildram.net)
4 60 195.66.224.105 (lndnuk1icx1.wcg.net)
5 107 64.200.87.61 (nycmny2wcx2-pos15-3.wcg.net)
6 * 100 0.0.0.0
7 * 100 0.0.0.0
8 * 100 0.0.0.0
9 * 100 Unable to reach 216.40.217.24 (qshosting.com)

Same problem again:

Source IP: 81.134.215.23 [BTOpenWorld ADSL Dynamic IP]
Destination 1: 64.246.36.31 [server]
========
Tracing route to 64.246.36.31
over a maximum of 30 hops:

1 <10 ms 10 ms <10 ms 192.168.0.1
2 40 ms 20 ms 20 ms btdhg519-hg3.ealing.broadband.bt.net [217.47.13
.202]
3 10 ms 20 ms 20 ms 217.47.133.129
4 10 ms 20 ms 20 ms 217.47.133.238
5 10 ms 20 ms 20 ms inh3cs01-500.imsnet3.btopenworld.com [213.1.119
61]
6 10 ms 20 ms 20 ms btfl03-gig8-7.imsnet3.btopenworld.com [213.1.11
.153]
7 30 ms 70 ms 20 ms core1-pos12-1.ealing.ukcore.bt.net [194.72.9.19
]
8 20 ms 60 ms 20 ms core1-pos10-0.redbus.ukcore.bt.net [194.74.65.2
4]
9 90 ms 100 ms 90 ms lndnuk1icx1.wcg.net [195.66.224.105]
10 90 ms 90 ms 100 ms nycmny2wcx2-pos15-3.wcg.net [64.200.87.61]
11 * * * Request timed out.
12 * * * Request timed out.
========

Source IP: 81.134.215.23 [BTOpenWorld ADSL Dynamic IP]
Destination 2: 69.57.152.68 [server]
========
Tracing route to 64.246.36.31
1 <10 ms <10 ms <10 ms 192.168.0.1
2 50 ms 20 ms 20 ms btdhg519-hg3.ealing.broadband.bt.net [217.47.133
.202]
3 130 ms 180 ms 60 ms 217.47.133.162
4 * 10 ms 20 ms 217.47.133.234
5 20 ms 20 ms 20 ms inh3cs01-500.imsnet3.btopenworld.com [213.1.119.
61]
6 20 ms 20 ms 20 ms ftip002613901.interconnect5.ealing.fixed-nte.bt.
net [213.1.119.161]
7 10 ms 20 ms 20 ms core1-pos4-3.ealing.ukcore.bt.net [194.72.9.241]

8 20 ms 20 ms 20 ms core1-pos5-0.telehouse.ukcore.bt.net [194.74.65.
129]
9 90 ms 100 ms 90 ms lndnuk1icx1.wcg.net [195.66.224.105]
10 90 ms 101 ms 90 ms nycmny2wcx2-oc12.wcg.net [64.200.87.149]
11 * * * Request timed out.
12 * * * Request timed out.
=========

Funny thing: going through BT's Proxy server (IP address 194.72.9.37 ) allows me to reach Destination1 but not Destination2.

We've got 2 other servers in EV1 and (207.218.250... and 64.246.11...) and they aren't affected.

richyc, Serevinus -

Thank you for the data.

Although it does not explain all of your symptoms, I just dropped the inbound routing from Williams.

Wait a few minutes for routing to converge and then give me another round of inbound traceroutes and source addresses.

Thanks,

Randy Williams, CTO


edit:

It would appear to be an inbound problem. Outbound takes two diverse paths:

223.36#trace 82.133.123.12
Type Control-c to abort
Tracing the route to IP node 82.133.123.12 from 1 to 30 hops

1 <1 ms <1 ms <1 ms ivhou-207-218-245-5.ev1.net [207.218.245.5]
2 <1 ms <1 ms <1 ms ivhou-207-218-223-49.ev1.net [207.218.223.49]
3 6 ms 5 ms 6 ms hstntx1wce2-gige5-0.wcg.net [65.77.93.53]
4 6 ms 6 ms 6 ms dllstx1wcx2-pos5-0.wcg.net [64.200.240.73]
5 6 ms 6 ms 6 ms dllstx1wcx3-oc48.wcg.net [64.200.110.74]
6 47 ms 47 ms 47 ms drvlga1wcx1-pos6-0.wcg.net [64.200.240.22]
7 48 ms 48 ms 48 ms drvlga1wcx2-oc48.wcg.net [64.200.127.30]
8 47 ms 48 ms 47 ms hrndva1wcx3-pos.wcg.net [64.200.210.58]
9 48 ms 48 ms 48 ms hrndva1wcx2-oc48.wcg.net [64.200.95.73]
10 54 ms 54 ms 54 ms nycmny2wcx2-pos0-0.wcg.net [64.200.210.98]
11 121 ms 121 ms 121 ms lndnuk1lcx1-oc12.wcg.net [64.200.87.150]
12 111 ms 117 ms 106 ms lon1-9.nildram.net [195.66.224.59]
13 110 ms 108 ms 106 ms lon1-adsl9-2.nildram.net [213.208.106.206]
14 * * * ?
15 * * * ?



223.42#trace 81.134.215.23
Type Control-c to abort
Tracing the route to IP node 81.134.215.23 from 1 to 30 hops

1 <1 ms <1 ms <1 ms ivhou-207-218-245-32.ev1.net [207.218.245.32]
2 <1 ms <1 ms <1 ms ivhou-207-218-223-9.ev1.net [207.218.223.9]
3 <1 ms <1 ms <1 ms 289.ge-4-2-0.mpr2.iah1.us.mfnx.net [216.200.251.27]
4 13 ms 13 ms 13 ms pos-10-0.er1.atl4.us.above.net [64.125.29.65]
5 13 ms 13 ms 13 ms pos14-0.pr1.atl4.us.above.net [64.125.30.242]
6 24 ms 24 ms 24 ms so-3-1-0.cr1.dca2.us.above.net [64.125.29.38]
7 96 ms 96 ms 96 ms so-6-0-0.cr1.lhr3.uk.above.net [64.125.31.185]
8 96 ms 96 ms 96 ms so-0-0-0.cr2.lhr3.uk.above.net [208.184.231.146]
9 96 ms 96 ms 96 ms pos1-0.mpr2.lhr1.uk.above.net [208.185.156.1]
10 96 ms 96 ms 96 ms core2-gig9-0.telehouse.ukcore.bt.net [208.185.156.218]
11 98 ms 98 ms 97 ms core2-pos14-0.ealing.ukcore.bt.net [194.74.65.122]
12 96 ms 96 ms 96 ms interconnect6-pos8-0.ealing.fixed.bt.net [194.72.9.254]
13 97 ms 97 ms 97 ms inh3cs02-454.imsnet3.btopenworld.com [213.1.119.158]
14 97 ms 97 ms 97 ms 172.16.95.219
15 97 ms 97 ms 97 ms bthg519.imsnet3.btopenworld.com [213.1.119.19]
16 * * * ?
17 * * * ?
18 * * * ?
19 * * * ?

Cheers TechieSurfer - that's done the trick.

Here's the new (working) traceroutes for your references

Source IP: 81.134.215.23 [BTOpenWorld ADSL Dynamic IP]
Destination 1: 64.246.36.31 [server]
========
1 <10 ms <10 ms <10 ms 192.168.0.1
2 110 ms 70 ms 140 ms btdhg519-hg3.ealing.broadband.bt.net [217.47.133
.202]
3 30 ms 20 ms 90 ms 217.47.133.129
4 20 ms 20 ms 20 ms 217.47.133.234
5 10 ms 10 ms 20 ms inh3cs01-500.imsnet3.btopenworld.com [213.1.119.
61]
6 10 ms 10 ms 20 ms btfl03-gig8-7.imsnet3.btopenworld.com [213.1.119
.153]
7 20 ms 10 ms 20 ms core2-pos12-1.ealing.ukcore.bt.net [194.72.9.201
]
8 10 ms 20 ms 20 ms core2-pos4-0.telehouse.ukcore.bt.net [194.74.65.
121]
9 20 ms 20 ms 20 ms ge9-1.mpr2.lhr1.uk.above.net [208.185.156.217]
10 20 ms 20 ms 20 ms so-4-1-0.cr2.lhr3.uk.above.net [208.185.156.2]
11 10 ms 20 ms 10 ms so-0-0-0.cr1.lhr3.uk.above.net [208.184.231.145]

12 270 ms 120 ms 91 ms so-7-0-0.cr1.dca2.us.above.net [64.125.31.186]
13 100 ms 110 ms 110 ms pos2-0.pr1.atl4.us.mfnx.net [208.184.232.50]
14 100 ms 100 ms 100 ms so-0-0-0.cr1.atl2.us.mfnx.net [208.185.0.217]
15 110 ms 120 ms 110 ms so-3-1-0.mpr2.iah1.us.above.net [64.125.29.62]
16 110 ms 120 ms 110 ms 216.200.251.61.ev1.net [216.200.251.61]
17 120 ms 120 ms 140 ms ivhou-207-218-245-37.ev1.net [207.218.245.37]
18 * * * Request timed out.
[traceroutes blocked at server]
==========

Source IP: 81.134.215.23 [BTOpenWorld ADSL Dynamic IP]
Destination 2: 69.57.152.68 [server]
========
1 <10 ms <10 ms <10 ms 192.168.0.1
2 10 ms 20 ms 20 ms btdhg519-hg3.ealing.broadband.bt.net [217.47.133
.202]
3 10 ms 30 ms 10 ms 217.47.133.130
4 10 ms 20 ms 20 ms 217.47.133.238
5 20 ms 20 ms 20 ms inh3cs01-500.imsnet3.btopenworld.com [213.1.119.
61]
6 180 ms 20 ms 20 ms ftip002613901.interconnect5.ealing.fixed-nte.bt.
net [213.1.119.161]
7 240 ms 331 ms 340 ms core2-pos4-3.ealing.ukcore.bt.net [194.72.9.245]

8 20 ms 10 ms 20 ms core2-pos5-0.telehouse.ukcore.bt.net [194.74.65.
181]
9 20 ms 20 ms 20 ms ge9-1.mpr2.lhr1.uk.above.net [208.185.156.217]
10 20 ms 20 ms 20 ms so-4-1-0.cr2.lhr3.uk.above.net [208.185.156.2]
11 20 ms 20 ms 20 ms so-0-0-0.cr1.lhr3.uk.above.net [208.184.231.145]

12 90 ms 90 ms 90 ms so-7-0-0.cr1.dca2.us.above.net [64.125.31.186]
13 231 ms 100 ms 100 ms pos11-0.pr1.atl4.us.above.net [64.125.29.37]
14 100 ms 100 ms 110 ms pos13-0.er1.atl4.us.above.net [64.125.30.237]
15 430 ms 170 ms 261 ms so-4-0-0.mpr2.iah1.us.above.net [64.125.29.70]
16 120 ms 121 ms 110 ms 216.200.251.29.ev1.net [216.200.251.29]
17 110 ms 120 ms 111 ms ivhou-207-218-245-42.ev1.net [207.218.245.42]
18 *
[traceroutes blocked at server]
========

The first trace is the new one, the bottom trace is older

Should of put them the other way round I guess
Figured its easier to read as an image

richyc -

Thank you for the data and your guidance in the other thread (now 16 posts without any useable data) to post here.

Apparently Williams is having some trouble in NYC...

Sincerely,

Randy Williams, CTO

Serevinus -

If I read that correctly it appears your problem has been resolved as well.

Thank you for your data.

Randy Williams, CTO

Yup, thanks, I was about to edit my post and say all seems to be working so far
Thanks again, its been annoying me most most of the day

Hello:

I opened a trouble ticket a while ago, however, the reply I received was that it's being looked into and was closed.... I thought I might try here to see if anyone has any input.

I'm currently experiencing a very high amount of latency when traffic enters the EV1 network. Here's a trace:

C:>tracert mercury.mcwhosting.us

Tracing route to mercury.mcwhosting.us [207.44.236.9]
over a maximum of 30 hops:

1 10 ms 20 ms 10 ms adsl-68-74-72-254.dsl.emhril.ameritech.net [68.7
4.72.254]
2 20 ms 20 ms 10 ms dist1-vlan50.emhril.ameritech.net [68.22.72.66]

3 10 ms 10 ms 20 ms bb2-g1-0-1.emhril.ameritech.net [68.22.73.36]
4 10 ms 10 ms 20 ms ex1-p8-0.eqchil.sbcglobal.net [151.164.240.146]

5 20 ms 10 ms 20 ms ex1-p11-0.eqchil.sbcglobal.net [151.164.191.249]

6 20 ms 10 ms 20 ms asn174-cogent.eqchil.sbcglobal.net [151.164.248.
94]
7 20 ms 10 ms 20 ms p12-0.core01.ord01.atlas.cogentco.com [154.54.2.
237]
8 20 ms 10 ms 10 ms p15-0.core02.ord01.atlas.cogentco.com [66.28.4.6
2]
9 40 ms 40 ms 30 ms p12-0.core01.mci01.atlas.cogentco.com [66.28.4.3
3]
10 31 ms 90 ms 80 ms p5-0.core02.dfw01.atlas.cogentco.com [66.28.4.37
]
11 30 ms 40 ms 30 ms p15-0.core01.dfw01.atlas.cogentco.com [66.28.4.2
5]
12 30 ms 50 ms 40 ms p13-0.core01.iah01.atlas.cogentco.com [66.28.4.9
8]
13 40 ms 40 ms 41 ms EveryonesInternet.demarc.cogentco.com [38.112.12
.178]
14 1913 ms 2213 ms 1943 ms ivhou-207-218-245-41.ev1.net [207.218.245.41]
15 1572 ms 1552 ms 1552 ms mercury.mcwhosting.us [207.44.236.9]

Trace complete.


It looks like it's only from the 207.218.245.41 router/switch. Here's another trace that doesn't go through it and it appears fine.

C:>tracert forums.ev1servers.net

Tracing route to forums.ev1servers.net [207.218.223.169]
over a maximum of 30 hops:

1 20 ms 10 ms 10 ms adsl-68-74-72-254.dsl.emhril.ameritech.net [68.7
4.72.254]
2 11 ms 10 ms 10 ms dist1-vlan50.emhril.ameritech.net [68.22.72.66]

3 10 ms 10 ms 10 ms bb2-g1-3-0.emhril.ameritech.net [68.22.72.228]
4 11 ms 20 ms 10 ms ex1-p8-1.eqchil.sbcglobal.net [151.164.240.18]
5 10 ms 10 ms 20 ms ex1-p11-0.eqchil.sbcglobal.net [151.164.191.249]

6 10 ms 10 ms 20 ms asn174-cogent.eqchil.sbcglobal.net [151.164.248.
94]
7 10 ms 30 ms 10 ms p12-0.core01.ord01.atlas.cogentco.com [154.54.2.
237]
8 20 ms 10 ms 20 ms p15-0.core02.ord01.atlas.cogentco.com [66.28.4.6
2]
9 30 ms 30 ms 40 ms p12-0.core01.mci01.atlas.cogentco.com [66.28.4.3
3]
10 40 ms 30 ms 40 ms p5-0.core02.dfw01.atlas.cogentco.com [66.28.4.37
]
11 30 ms 40 ms 50 ms p15-0.core01.dfw01.atlas.cogentco.com [66.28.4.2
5]
12 40 ms 40 ms 40 ms p13-0.core01.iah01.atlas.cogentco.com [66.28.4.9
8]
13 70 ms 60 ms 50 ms EveryonesInternet.demarc.cogentco.com [38.112.12
.178]
14 40 ms 40 ms 41 ms ivhou-207-218-223-8.ev1.net [207.218.223.8]
15 40 ms 40 ms 40 ms forum.ev1servers.net [207.218.223.169]

Trace complete.

My source IP is 68.74.65.1

Perhaps I'm the only one experiencing this? Please let me know if you require any additional information from me.

Thanks!!

Looks like the latency problem I was experiencing has been resolved!

MCW -

Thank you for the data.

The latency was in the ALGX #2 link. The issue was almost certainly created by the transport carrier as they performed scheduled maintenance immediately before the latency appeared. We have been working towards a resolution with both parties.

I am sorry for any problems that this may have caused you.

Randy Williams, CTO

Isolated network issue... I think it's only my ISP.

My IP: 68.196.85.166
RS Server IP: 207.44.220.12

Traceroute loses packets after 207.218.245.41 which is an EV1 server.

----------------------------------------------------------------
| 2 | | 67.83.249.161 | dstswr1-vlan-2.rh.rndhnj.cv.net |
| 3 | | 67.83.249.129 | r1-ge-9-2.mhe.prnynj.cv.net |
| 4 | | 65.19.112.17 | r1-srp13-0.wan.prnynj.cv.net |
| 5 | | 167.206.12.147 | r1-srp13-0.in.nycmny83.cv.net |
| 6 | | 167.206.8.154 | pos5-2.pr1.lga1.us.mfnx.net |
| 7 | | 64.125.30.185 | so-4-3-0.cr1.lga1.us.above.net |
| 8 | | 208.184.233.61 | so-1-0-0.cr1.iad1.us.above.net |
| 9 | | 208.184.233.125 | so-1-0-0.cr1.dca2.us.above.net |
| 10 | | 208.184.232.50 | pos2-0.pr1.atl4.us.above.net |
| 11 | | 64.125.30.241 | pos14-0.er1.atl4.us.above.net |
| 12 | | 64.125.29.62 | so-3-1-0.mpr2.iah1.us.above.net |
| 13 | | 216.200.251.29 | 216.200.251.29.ev1.net |
| 14 | 100 | ?207.218.245.41 | |
| 15 | 100 | ?207.44.220.12 | |
----------------------------------------------------------------

Any idea what might be wrong?

Thanks,
Michael

Nevermind, it's backup... down for 25 minutes though.

Traza a la dirección www.algoespecial.com [207.218.250.102]
sobre un máximo de 30 saltos:

1 <1 ms <1 ms <1 ms 192.168.123.254
2 12 ms 39 ms 14 ms localhost [127.0.0.1]
3 10 ms 12 ms 10 ms 10.3.1.4
4 34 ms 13 ms 12 ms 200.77.160.133
5 13 ms 13 ms 20 ms 200.77.226.226
6 20 ms 22 ms 25 ms na-148-245-34-89.na.avantel.net.mx [148.245.34.8
9]
7 * 33 ms 30 ms pos5/0.rr1.reyixt.avantel.net.mx [200.33.208.254
]
8 45 ms 45 ms 44 ms POS2-0.IH1.HOU7.ALTER.NET [157.130.133.205]
9 45 ms 45 ms 45 ms 0.so-0-2-0.XL2.HOU7.ALTER.NET [152.63.3.6]
10 59 ms 55 ms 54 ms 0.so-7-0-0.CL2.DFW13.ALTER.NET [152.63.103.222]

11 56 ms 55 ms 52 ms POS7-0.GW2.DFW13.ALTER.NET [152.63.103.229]
12 61 ms 66 ms 72 ms wcgGigE-gw3.customer.alter.net [157.130.30.250]

13 77 ms 61 ms 61 ms dllstx1wcx2-oc48.wcg.net [64.200.110.81]
14 65 ms * 68 ms hstntx1wce2-pos4-0.wcg.net [64.200.240.74]
15 * * * Tiempo de espera agotado para esta solicitud.
16 * * * Tiempo de espera agotado para esta solicitud.
17 * * * Tiempo de espera agotado para esta solicitud.
18 * * * Tiempo de espera agotado para esta solicitud.
19 * * * Tiempo de espera agotado para esta solicitud.
20 *

I don't know the soruce IP since it's cable without public IP.
The destination IP is 207.218.250.102

Thanks

http://forums.ev1servers.net/showthread.ph...&threadid=42173

Randy, it has nothing to do with that, since at the same time I could access the site from another connection from another ISP.

(I could via prodigy, but not via cablevision)

Thanks

My apologies if this isn't the proper thread (though I believe it is)

Starting IP: 130.89.160.1
Destination IP: 69.57.158.6

Tracert: (may be a tracert to ev1's main site, or the destination IP listed above -- both have been unreachable for the past week for this person)


1 6 ms <1 ms <1 ms if-campus.routing.utwente.nl
[130.89.160.1]
2 <1 ms <1 ms <1 ms Gi6-0.AR5.Enschede1.surf.net
[145.145.4.1]
3 6 ms 5 ms 5 ms PO2-0.CR2.Amsterdam1.surf.net
[145.145.163.13]
4 6 ms 5 ms 5 ms PO0-0.BR2.Amsterdam1.surf.net
[145.145.166.6]
5 6 ms 6 ms 6 ms core01.ams01.atlas.cogentco.com
[195.69.144.234]
6 7 ms 7 ms 8 ms p1-0.core01.ams02.atlas.cogentco.com
[130.117.1.5]
7 12 ms 12 ms 11 ms p1-0.core01.lcy01.atlas.cogentco.com
[130.117.1.1]
8 94 ms * 95 ms p13-0.core02.jfk02.atlas.cogentco.com
[130.117.1.18]
9 95 ms 94 ms 94 ms p15-0.core01.jfk02.atlas.cogentco.com
[66.28.4.13]
10 95 ms 95 ms 95 ms p4-0.core02.dca01.atlas.cogentco.com
[66.28.4.81]
11 106 ms 106 ms 106 ms p14-0.core01.atl01.atlas.cogentco.com
[66.28.4.161]
12 113 ms 112 ms 112 ms p15-0.core01.jax01.atlas.cogentco.com
[66.28.4.137]
13 116 ms 116 ms 116 ms p14-0.core01.mco01.atlas.cogentco.com
[66.28.4.153]
14 117 ms 117 ms 117 ms p14-0.core01.tpa01.atlas.cogentco.com
[66.28.4.142]
15 129 ms 129 ms 130 ms p5-0.core01.iah01.atlas.cogentco.com
[66.28.4.45]
16 128 ms 124 ms 124 ms EveryonesInternet.demarc.cogentco.com
[38.112.12.178]
17 124 ms 124 ms 124 ms ivhou-207-218-245-42.ev1.net
[207.218.245.42]
18 * * * Request timed out.


Thanks in advance for any assistance.

-Jason

Do the switches / routers get reset every so often?

If I leave an ssh connection open eventually i loose it. Log back into server only to discovered that the session is still going.. (ie i have to kill it .. i can view it via ps)

today i decided to run a game server.. server is running fine.. then i go play elsewhere come back to the game server cannot connect.. flip to the ssh window noticed i lost connection.. and since the game was not running in the background it seems it stopped running

I have noticed this for quite a while (ie. months now) before this.. it didnt used to be like this.. i could be logged into the server for hours / days

???

charlottezwebb -

There was nothing being blocked, and at this time I can reach the remote host:

223.42#ping 130.89.160.1 source 69.57.158.1
Sending 1, 16-byte ICMP Echo to 130.89.160.1, timeout 5000 msec, TTL 64
Type Control-c to abort
Reply from 130.89.160.1 : bytes=16 time=128ms TTL=242
Success rate is 100 percent (1/1), round-trip min/avg/max=128/128/128 ms.

If you are still experiencing problems, try pinging 69.57.158.5 and 69.57.158.7 from the remote host. If those work then either the server is specifically blocking the remote host, or the remote host is blocking the server...

Randy Williams, CTO

Seeker -

The last time our monitoring software missed a poll of the switch to which your server is documented here:

20040225 0841 DOWN 207.44.156.247 207.44.156.247 Timed Out
20040225 0842 UP 207.44.156.247 207.44.156.247 missed 1

Another single poll was missed more than a week earlier...

Randy Williams, CTO

Thanks Randy, I'll pass that on.

What's strange is, he's not able to access my server, nor ev1's site without using a proxy server. It's not just a matter of my server alone -- it appears to be anything in the datacenter.

charlottezwebb -

According to the trace he can access the router: ivhou-207-218-245-42.ev1.net [207.218.245.42] .

edit: I was able to ping that IP from one of the www.ev1servers.net web servers.

Randy Williams, CTO

Please disregard this post.
I found the problem, It was on my end.

Having Issues on my server:

Inbound:



I have noticed a drop in traffic to day and yesterday.

Mostly UK based traffic luckly for me my connection is dutch based...

johnwards-

I cannot troubleshoot this issue without all the information - specifically the exact public source IP address.

From what I can tell nothing appears to be blocked, and the source makes it the router immediately above the server

I can reach the first public IP from your trace:

223.51#trace 213.208.106.112 num
Type Control-c to abort
Tracing the route to IP node 213.208.106.112 from 1 to 30 hops

1 <1 ms <1 ms <1 ms 207.218.245.48
2 <1 ms <1 ms <1 ms 207.218.223.49
3 <1 ms <1 ms 1 ms 65.77.93.53
4 5 ms 5 ms 5 ms 64.200.240.73
5 5 ms 6 ms 6 ms 64.200.110.78
6 23 ms 23 ms 23 ms 64.200.240.22
7 23 ms 23 ms 23 ms 64.200.127.50
8 34 ms 34 ms 34 ms 64.200.232.126
9 34 ms 34 ms 34 ms 64.200.95.77
10 40 ms 41 ms 40 ms 64.200.240.45
11 112 ms 112 ms 112 ms 64.200.87.62
12 111 ms 111 ms 111 ms 195.66.224.59
13 112 ms 112 ms 112 ms 213.208.106.112

From this data I would guess the server is blocking the source, or the source (or their ISP) is specifically blocking the server.

Sincerely,

Randy Williams, CTO

Traza a la dirección www.algoespecial.com [207.218.250.102]
sobre un máximo de 30 saltos:

1 <1 ms <1 ms <1 ms 192.168.123.254
2 12 ms 39 ms 14 ms localhost [127.0.0.1]
3 10 ms 12 ms 10 ms 10.3.1.4
4 34 ms 13 ms 12 ms 200.77.160.133
5 13 ms 13 ms 20 ms 200.77.226.226
6 20 ms 22 ms 25 ms na-148-245-34-89.na.avantel.net.mx [148.245.34.8
9]
7 * 33 ms 30 ms pos5/0.rr1.reyixt.avantel.net.mx [200.33.208.254
]
8 45 ms 45 ms 44 ms POS2-0.IH1.HOU7.ALTER.NET [157.130.133.205]
9 45 ms 45 ms 45 ms 0.so-0-2-0.XL2.HOU7.ALTER.NET [152.63.3.6]
10 59 ms 55 ms 54 ms 0.so-7-0-0.CL2.DFW13.ALTER.NET [152.63.103.222]

11 56 ms 55 ms 52 ms POS7-0.GW2.DFW13.ALTER.NET [152.63.103.229]
12 61 ms 66 ms 72 ms wcgGigE-gw3.customer.alter.net [157.130.30.250]

13 77 ms 61 ms 61 ms dllstx1wcx2-oc48.wcg.net [64.200.110.81]
14 65 ms * 68 ms hstntx1wce2-pos4-0.wcg.net [64.200.240.74]
15 * * * Tiempo de espera agotado para esta solicitud.
16 * * * Tiempo de espera agotado para esta solicitud.
17 * * * Tiempo de espera agotado para esta solicitud.
18 * * * Tiempo de espera agotado para esta solicitud.
19 * * * Tiempo de espera agotado para esta solicitud.
20 *

The source IP is 200.77.160.133 (the client has 10.3.1.4 but the gateway is 200.77.160.133)
The destination IP is 207.218.250.102

Still the same result, no tracing to EV1....

jca -

I can reach that remote IP - is it working now?

223.41#ping 200.77.160.133
Sending 1, 16-byte ICMP Echo to 200.77.160.133, timeout 5000 msec, TTL 64
Type Control-c to abort
Reply from 200.77.160.133 : bytes=16 time=58ms TTL=244
Success rate is 100 percent (1/1), round-trip min/avg/max=58/58/58 ms.

Randy Williams, CTO

Randy,

I have more info and would like to revisit this. The user is still unable to hit EV1 (or any server with you including the main ev1 site).

Here's his exact IP since the one I gave you before was apparently right above him: 130.89.162.211

Here is a tracert from the user to www.aquaxp.com (a site on my box):

my tracert results for aquaxp:

Tracing route to aquaxp.com [69.57.158.6]
over a maximum of 30 hops:

1 6 ms <1 ms <1 ms if-campus.routing.utwente.nl [130.89.160.1]
2 1 ms <1 ms <1 ms Gi6-0.AR5.Enschede1.surf.net [145.145.4.1]
3 6 ms 6 ms 6 ms PO2-0.CR2.Amsterdam1.surf.net
[145.145.163.13]
4 6 ms 6 ms 6 ms PO0-0.BR2.Amsterdam1.surf.net
[145.145.166.6]
5 99 ms 99 ms 98 ms core01.ams01.atlas.cogentco.com
[195.69.144.234]
6 98 ms 98 ms 98 ms p1-0.core01.ams02.atlas.cogentco.com
[130.117.1.5]
7 99 ms 98 ms 98 ms p1-0.core01.lcy01.atlas.cogentco.com
[130.117.1.1]
8 98 ms 98 ms 98 ms p13-0.core02.jfk02.atlas.cogentco.com
[130.117.1.18]
9 98 ms 98 ms 98 ms p15-0.core01.jfk02.atlas.cogentco.com
[66.28.4.13]
10 99 ms 98 ms 98 ms p4-0.core02.dca01.atlas.cogentco.com
[66.28.4.81]
11 110 ms 110 ms 110 ms p14-0.core01.atl01.atlas.cogentco.com
[66.28.4.161]
12 119 ms 119 ms 119 ms p14-0.core01.mco01.atlas.cogentco.com
[66.28.4.153]
13 121 ms 121 ms 121 ms p14-0.core01.tpa01.atlas.cogentco.com
[66.28.4.142]
14 133 ms 133 ms 134 ms p5-0.core01.iah01.atlas.cogentco.com
[66.28.4.45]
15 127 ms 128 ms 127 ms EveryonesInternet.demarc.cogentco.com
[38.112.12.178]
16 128 ms 128 ms 128 ms ivhou-207-218-245-42.ev1.net
[207.218.245.42]
17 * * * Request timed out.

Somewhere within ev1 his connection seems to be getting blocked, at least from what knowledge I have of the error.

Any further information would be greatly appreciated...he's unable to ftp in to admin his account (though he can obviously browse through a proxy connection).

Thanks!
Jason

charlottezwebb -

It appears your server is blocking the remote host. The next hop of your trace would be your server...

I can trace to the remote host from with a source IP from your subnet without issue:

223.42#trace 130.89.162.211 source 69.57.158.1
Type Control-c to abort
Tracing the route to IP node 130.89.162.211 from 1 to 30 hops

1 <1 ms <1 ms <1 ms ivhou-207-218-245-32.ev1.net [207.218.245.32]
2 <1 ms <1 ms <1 ms ivhou-207-218-223-7.ev1.net [207.218.223.7]
3 <1 ms <1 ms <1 ms 289.ge-3-2-0.mpr1.iah1.us.mfnx.net [216.200.251.50]
4 1 ms 1 ms 1 ms so-0-0-0.mpr2.iah1.us.above.net [64.125.31.62]
5 13 ms 13 ms 13 ms pos2-0.er1.atl4.us.above.net [64.125.31.26]
6 13 ms 13 ms 13 ms pos14-0.pr1.atl4.us.above.net [64.125.30.242]
7 24 ms 24 ms 24 ms so-6-1-0.cr1.dca2.us.above.net [64.125.28.229]
8 96 ms 96 ms 96 ms so-6-0-0.cr1.lhr3.uk.above.net [64.125.31.185]
9 96 ms 96 ms 96 ms so-0-0-0.cr2.lhr3.uk.above.net [208.184.231.146]
10 104 ms 104 ms 104 ms pos9-0.cr2.ams2.nl.above.net [64.125.31.158]
11 104 ms 104 ms 104 ms pos1-0.mpr2.ams1.nl.above.net [208.184.231.253]
12 122 ms 121 ms 121 ms Gi5-0.BR2.Amsterdam1.surf.net [195.69.144.34]
13 121 ms 121 ms 120 ms PO12-0.CR2.Amsterdam1.surf.net [145.145.166.5]
14 130 ms 126 ms 126 ms PO0-0.AR5.Enschede1.surf.net [145.145.163.14]
15 246 ms 145 ms 143 ms utwente-router.Customer.surf.net [145.145.4.2]
16 127 ms 127 ms 126 ms ruler.student.utwente.nl [130.89.162.211]


If you cannot figure out why your server is blocking the remote host then have the remote client ping servers on the same subnet like 69.57.158.5 and 69.57.158.7 and post those results here.

Randy Williams, CTO

If the problem was only my server, why can he not view ev1servers.net?

Regards,
Jason

charlottezwebb -

Good question, I forgot that from the last post...

However I can ping that remote host from all of the www.ev1servers.net servers.

Please have the remote host ping www.ev1servers.net and 69.57.158.5 and 69.57.158.7 and post those results here.

Randy Williams, CTO

[edit] Have them ping 69.57.158.6 also. [/edit]

[edit x2] This is looking like they use a proxy or transparrent proxy. It would be useful for them to check their http source address also. Have the remote station browse to http://www.whatismyip.com/ to see if their IP differs from their http request IP number. [/edit x2]

It works now, thanks a lot. We were also talking to his ISP to check this issue, thanks Randy

Source: 216.190.230.226

/usr/sbin/traceroute 216.40.244.1
traceroute to 216.40.244.1 (216.40.244.1), 30 hops max, 38 byte packets
1 gateway.office.com (10.0.0.1) 0.359 ms 0.235 ms 0.224 ms
2 208.187.35.81 (208.187.35.81) 1.855 ms 2.918 ms 2.430 ms
3 s10-0-0--123.gw02.slkc.eli.net (216.190.238.97) 9.235 ms 8.871 ms 8.678 ms
4 srp2-0.cr02.slkc.eli.net (208.186.20.50) 8.738 ms 8.773 ms 8.983 ms
5 p9-0.cr01.bois.eli.net (207.173.114.65) 17.463 ms 18.502 ms 16.600 ms
6 srp3-0.cr02.bois.eli.net (208.186.20.178) 17.048 ms 17.074 ms 16.681 ms
7 p9-0.cr01.ptld.eli.net (207.173.115.37) 28.321 ms 27.617 ms 28.631 ms
8 srp3-0.cr01.tkwl.eli.net (208.186.21.3) 31.975 ms 31.764 ms 32.444 ms
9 so-0-0-0--0.er02.sttl.eli.net (207.173.114.146) 33.015 ms 32.667 ms 32.664 ms
10 sttlwablhx1-gige1.7.paix.wcg.net (198.32.134.15) 35.552 ms 70.020 ms 34.364 ms
11 sttlwa2wce2-pos4-0.wcg.net (64.200.135.121) 32.980 ms 32.703 ms 32.979 ms
12 dnvrco1wcx3-pos10-0-oc48.wcg.net (64.200.240.13) 67.219 ms 68.700 ms 66.564 ms
13 dllstx1wcx3-pos1-0.wcg.net (64.200.240.213) 77.957 ms 77.926 ms 78.207 ms
14 * * *

Been down for about 2 hours now.

kicker -

You traced to an IP that is not a server and will not allow a UDP trace. However there is more to the problem as the trace stopped in Dallas.

No IPs around 216.190.230.226 respond to pings from 216.40.244.1:

223.36#ping 216.190.230.226 source 216.40.244.1
Sending 1, 16-byte ICMP Echo to 216.190.230.226, timeout 5000 msec, TTL 64
Type Control-c to abort
Request timed out.
No reply from remote host.

223.36#ping 216.190.230.225 source 216.40.244.1
Sending 1, 16-byte ICMP Echo to 216.190.230.225, timeout 5000 msec, TTL 64
Type Control-c to abort
Request timed out.
No reply from remote host.

223.36#ping 216.190.230.227 source 216.40.244.1
Sending 1, 16-byte ICMP Echo to 216.190.230.227, timeout 5000 msec, TTL 64
Type Control-c to abort
Request timed out.
No reply from remote host.


They also do not respond to pings from 216.40.245.1:

223.36#ping 216.190.230.227 source 216.40.245.1
Sending 1, 16-byte ICMP Echo to 216.190.230.227, timeout 5000 msec, TTL 64
Type Control-c to abort
Request timed out.
No reply from remote host.

223.36#ping 216.190.230.226 source 216.40.245.1
Sending 1, 16-byte ICMP Echo to 216.190.230.226, timeout 5000 msec, TTL 64
Type Control-c to abort
Request timed out.
No reply from remote host.

223.36#ping 216.190.230.225 source 216.40.245.1
Sending 1, 16-byte ICMP Echo to 216.190.230.225, timeout 5000 msec, TTL 64
Type Control-c to abort
Request timed out.
No reply from remote host.


But other ranges of sources ping fine:

223.36#ping 216.190.230.226 source 216.40.233.1
Sending 1, 16-byte ICMP Echo to 216.190.230.226, timeout 5000 msec, TTL 64
Type Control-c to abort
Reply from 216.190.230.226 : bytes=16 time=89ms TTL=55
Success rate is 100 percent (1/1), round-trip min/avg/max=89/89/89 ms.

223.36#ping 216.190.230.227 source 216.40.233.1
Sending 1, 16-byte ICMP Echo to 216.190.230.227, timeout 5000 msec, TTL 64
Type Control-c to abort
Reply from 216.190.230.227 : bytes=16 time=88ms TTL=119
Success rate is 100 percent (1/1), round-trip min/avg/max=88/88/88 ms.

223.36#ping 216.190.230.225 source 216.40.233.1
Sending 1, 16-byte ICMP Echo to 216.190.230.225, timeout 5000 msec, TTL 64
Type Control-c to abort
Reply from 216.190.230.225 : bytes=16 time=89ms TTL=247
Success rate is 100 percent (1/1), round-trip min/avg/max=89/89/89 ms.


And 216.40.244.1 is reachable from all looking glass servers I tested, so the problem is not fundamental:

route-views.oregon-ix.net>ping 216.40.244.1

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 216.40.244.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 200/208/216 ms

route-server.as5388.net>ping 216.40.244.1

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 216.40.244.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 112/112/112 ms

cerf.net:
route-server>ping 216.40.244.1

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 216.40.244.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 40/40/44 ms

glbx:
route-server.phx1>ping 216.40.244.1

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 216.40.244.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 72/72/72 ms

att:
route-server>ping 216.40.244.1

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 216.40.244.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 200/200/200 ms


Now the traces:

223.36#trace 216.190.230.226 source 216.40.244.1
Type Control-c to abort
Tracing the route to IP node 216.190.230.226 from 1 to 30 hops

1 <1 ms <1 ms <1 ms ivhou-207-218-245-5.ev1.net [207.218.245.5]
2 <1 ms <1 ms <1 ms ge-1-1-0.r02.hstntx01.us.bb.verio.net [129.250.10.65]
3 7 ms 7 ms 6 ms p16-1-0-3.r20.dllstx09.us.bb.verio.net [129.250.5.40]
4 47 ms 47 ms 47 ms p16-0-3-0.r20.asbnva01.us.bb.verio.net [129.250.5.35]
5 46 ms 30 ms 46 ms p16-7-0-0.r02.asbnva01.us.bb.verio.net [129.250.2.83]
6 48 ms 40 ms 47 ms p16-1-0-2.r20.asbnva01.us.bb.verio.net [129.250.2.48]
7 47 ms 46 ms 46 ms p16-7-0-0.r02.asbnva01.us.bb.verio.net [129.250.2.83]
8 56 ms 40 ms 40 ms ashburn-ibx.eli.net [206.223.115.46]
9 41 ms * * p7-3.cr01.mcln.eli.net [207.173.114.129]
10 54 ms * * p11-3.cr01.chcg.eli.net [207.173.115.89]
11 * * * ?
12 * * * ?
13 * * * ?
14 * * * ?
15 * * * ?



trace 216.190.230.226 source 216.40.233.1
Type Control-c to abort
Tracing the route to IP node 216.190.230.226 from 1 to 30 hops

1 <1 ms <1 ms <1 ms ivhou-207-218-245-5.ev1.net [207.218.245.5]
2 <1 ms <1 ms <1 ms ge-1-1-0.r02.hstntx01.us.bb.verio.net [129.250.10.65]
3 9 ms 9 ms 9 ms p16-0-3-0.r21.dllstx09.us.bb.verio.net [129.250.5.100]
4 30 ms 30 ms 30 ms p16-0-0-0.r01.atlnga03.us.bb.verio.net [129.250.4.195]
5 46 ms 30 ms 45 ms p16-7-0-0.r02.asbnva01.us.bb.verio.net [129.250.2.83]
6 47 ms 47 ms 47 ms p16-1-0-2.r20.asbnva01.us.bb.verio.net [129.250.2.48]
7 42 ms 46 ms 46 ms p16-7-0-0.r02.asbnva01.us.bb.verio.net [129.250.2.83]
8 43 ms 59 ms 43 ms ashburn-ibx.eli.net [206.223.115.46]
9 79 ms 79 ms 43 ms p7-3.cr01.mcln.eli.net [207.173.114.129]
10 59 ms 80 ms 80 ms srp0-0-0.gw02.slkc.eli.net [208.186.20.54]
11 80 ms 87 ms 80 ms p10-0.cr02.slkc.eli.net [207.173.115.53]
12 80 ms 80 ms 80 ms srp0-0-0.gw02.slkc.eli.net [208.186.20.54]
13 88 ms 88 ms 87 ms gw-cust-IOMATION-COM.slkc.eli.net [216.190.238.98]
14 89 ms 87 ms 88 ms gw-cust-IOMATION-COM.slkc.eli.net [216.190.238.98]
15 89 ms 89 ms 89 ms romeo.qwerks.com [216.190.230.226]
16 88 ms 89 ms 93 ms romeo.qwerks.com [216.190.230.226]


I then found a looking glass that goes inbound through wcg ( telnet://route-server-eu.exodus.net ) :

route-server-eu>trace 216.40.244.1

Type escape sequence to abort.
Tracing the route to 216.40.244.1

1 dcr04-p9-0.lndn01.exodus.net (212.62.2.73) 0 msec 0 msec 0 msec
2 bcr2-so-0-2-0.London.cw.net (166.63.161.129) 0 msec 0 msec 0 msec
3 bcr2-so-7-0-0.Thamesside.cw.net (166.63.209.205) 0 msec 0 msec 4 msec
4 dcr2-loopback.NewYork.cw.net (206.24.194.100) 72 msec 72 msec 68 msec
5 agr4-so-2-0-0.NewYork.cw.net (206.24.207.190) 68 msec
agr3-so-2-0-0.NewYork.cw.net (206.24.207.186) 72 msec 72 msec
6 acr2-loopback.NewYork.cw.net (206.24.194.62) 72 msec 72 msec 72 msec
7 206.24.193.206 72 msec 72 msec 68 msec
8 nycmny2wcx3-pos11-0.wcg.net (64.200.87.85) [AS 7911] 68 msec 72 msec 72 msec
9 nycmny2wcx2-oc48.wcg.net (64.200.87.73) [AS 7911] 68 msec 72 msec 72 msec
10 hrndva1wcx2-oc48.wcg.net (64.200.240.46) [AS 7911] 84 msec 88 msec 84 msec
11 hrndva1wcx3.oc48.wcg.net (64.200.95.78) [AS 7911] 88 msec 84 msec 84 msec
12 drvlga1wcx2-pos4-0.wcg.net (64.200.232.125) [AS 7911] 100 msec 96 msec 100 m
sec
13 drvlga1wcx1-oc48.wcg.net (64.200.127.29) [AS 7911] 96 msec 96 msec 100 msec
14 dllstx1wcx3-pos6-0.wcg.net (64.200.240.21) [AS 7911] 268 msec 116 msec 116 m
sec
15 dllstx1wcx2-oc48.wcg.net (64.200.110.77) [AS 7911] 116 msec 116 msec 116 mse
c
16 hstntx1wce2-pos4-0.wcg.net (64.200.240.74) [AS 7911] 120 msec 120 msec 124 m
sec
17 hstntx1wce2-everyonesinternet-gige.wcg.net (65.77.93.54) [AS 7911] 120 msec
124 msec 120 msec
18 ivhou-207-218-223-11.ev1.net (207.218.223.11) [AS 13749] !A !A !A

This suggests the inbound path is good to 216.40.244.1 through wcg, but on a hunch I decided to turn off that prefix inbound through wcg and then retest. Sure enough removing that prefix from wcg inbound seemed to fix the problem:

@223.36#ping 216.190.230.226 source 216.40.244.1
Sending 1, 16-byte ICMP Echo to 216.190.230.226, timeout 5000 msec, TTL 64
Type Control-c to abort
Reply from 216.190.230.226 : bytes=16 time=67ms TTL=48
Success rate is 100 percent (1/1), round-trip min/avg/max=67/67/67 ms.

Then I turned it back on and it was still fixed:

223.36#ping 216.190.230.226 source 216.40.244.1
Sending 1, 16-byte ICMP Echo to 216.190.230.226, timeout 5000 msec, TTL 64
Type Control-c to abort
Reply from 216.190.230.226 : bytes=16 time=70ms TTL=48
Success rate is 100 percent (1/1), round-trip min/avg/max=70/70/70 ms.

So I would conclude that something inbound in the wcg network needed to be toggled. I hope it does not resurface, because it was somewhat difficult to get a clear picture of the problem.

Finally I would like to see another inbound trace. I cannot help but to wonder if it still takes wcg inbound...

Sincerely,

Randy Williams, CTO

Okay, here's your requested info:




What's strange is that it seems he can ping ev1, yet he states he can't view the ev1servers.net site. He's timing out completely for my server.

Regards,
Jason

Thanks for the fix...

Here is an inbound for today, still going through WCG:

traceroute 216.40.244.53
traceroute to 216.40.244.53 (216.40.244.53), 30 hops max, 38 byte packets
1 gateway.office.com (10.0.0.1) 0.324 ms 0.226 ms 0.217 ms
2 208.187.35.81 (208.187.35.81) 1.832 ms 1.455 ms 1.592 ms
3 s10-0-0--123.gw02.slkc.eli.net (216.190.238.97) 9.038 ms 8.925 ms 8.849 ms
4 srp2-0.cr02.slkc.eli.net (208.186.20.50) 8.918 ms 9.164 ms 8.734 ms
5 p9-0.cr01.bois.eli.net (207.173.114.65) 17.561 ms 30.527 ms 17.370 ms
6 srp3-0.cr02.bois.eli.net (208.186.20.178) 29.803 ms 42.497 ms 22.826 ms
7 p9-0.cr01.ptld.eli.net (207.173.115.37) 33.007 ms 29.386 ms 29.889 ms
8 srp3-0.cr02.tkwl.eli.net (208.186.21.4) 32.169 ms 31.768 ms 32.362 ms
9 so-0-0-3--0.er02.sttl.eli.net (207.173.115.46) 32.830 ms 41.594 ms 32.809 ms
10 sttlwablhx1-gige1.7.paix.wcg.net (198.32.134.15) 33.013 ms 32.676 ms 32.801 ms
11 sttlwa2wce2-pos4-0.wcg.net (64.200.135.121) 33.304 ms 32.654 ms 33.463 ms
12 dnvrco1wcx3-pos10-0-oc48.wcg.net (64.200.240.13) 67.095 ms 66.683 ms 66.211 ms
13 dllstx1wcx3-pos1-0.wcg.net (64.200.240.213) 77.952 ms 78.312 ms 77.845 ms
14 dllstx1wcx2-oc48.wcg.net (64.200.110.77) 78.856 ms 98.056 ms 78.228 ms
15 hstntx1wce2-pos4-0.wcg.net (64.200.240.74) 82.880 ms 85.517 ms 83.232 ms
16 hstntx1wce2-everyonesinternet-gige.wcg.net (65.77.93.54) 88.340 ms 84.237 ms 85.026 ms
17 ivhou-207-218-245-36.ev1.net (207.218.245.36) 71.477 ms 71.095 ms 71.704 ms
18 216.40.244.53 (216.40.244.53) 70.464 ms 71.799 ms 72.977 ms

If the problem resurfaces, I will post inbound and outbound and an IP address on our network you can ping. Thanks again!

From Belgium's biggest ADSL provider to all servers in the ev1 network:

source: 80.200.241.198
destination: www.ev1servers.net




Trace doesn't complete from the same isp @ home to ev1 (source ip: home.tomsworld.be )



Avarage loss between 20 and 25 %


This is started 6 hours ago.

charlottezwebb -

I cannot think of a reasonable set of circumstances which would explain the data.

Are you sure the remote client cannot browse to www.ev1servers.net ? Please double check the url and have them try again.

Randy Williams, CTO

I honestly can't either, but I have a pending email from when I last posted this morning asking him to verify this for me again...

Jason

Tomsworld -

We can reach 194.78.255.33 (hop 3 from your trace) well:

223.17#ping 194.78.255.33 co 100
Sending 100, 16-byte ICMP Echo to 194.78.255.33, timeout 5000 msec, TTL 64
Success rate is 100 percent (100/100), round-trip min/avg/max=113/113/116 ms.

The trace:

223.17#trace 194.78.255.33
Type Control-c to abort
Tracing the route to IP node 194.78.255.33 from 1 to 30 hops

1 <1 ms <1 ms <1 ms ivhou-207-218-223-1.ev1.net [207.218.223.1]
2 7 ms 7 ms 7 ms 209.44.32.205
3 6 ms 6 ms 6 ms interconnect-eng.Dallas1.Level3.net [64.158.168.81]
4 6 ms 6 ms 6 ms so-4-1-0.bbr2.Dallas1.Level3.net [4.68.112.173]
5 50 ms 50 ms 50 ms so-0-1-0.bbr2.Washington1.Level3.net [64.159.0.230]
6 116 ms 116 ms 116 ms so-0-0-0.mp2.London2.Level3.net [212.187.128.133]
7 120 ms 120 ms 120 ms so-3-0-0.mp1.Brussels1.Level3.net [212.187.128.6]
8 122 ms 121 ms 120 ms so-10-0.hsa2.Brussels1.Level3.net [212.3.239.162]
9 * * * ?
10 113 ms 113 ms 113 ms 194.78.255.33

But we cannot reach 80.200.38.1 (hop 2 from your trace) well:

223.17#ping 80.200.38.1 co 10
Sending 10, 16-byte ICMP Echo to 80.200.38.1, timeout 5000 msec, TTL 64
Success rate is 40 percent (4/10), round-trip min/avg/max=130/130/130 ms.

The trace:

223.17#trace 80.200.241.198
Type Control-c to abort
Tracing the route to IP node 80.200.241.198 from 1 to 30 hops

1 1 ms <1 ms <1 ms ivhou-207-218-223-1.ev1.net [207.218.223.1]
2 <1 ms <1 ms <1 ms ivhou-207-218-223-9.ev1.net [207.218.223.9]
3 <1 ms 1 ms <1 ms 289.ge-3-2-0.mpr2.iah1.us.mfnx.net [216.200.251.51]
4 13 ms 13 ms 13 ms pos11-0.er1.atl4.us.above.net [64.125.29.61]
5 13 ms 13 ms 13 ms pos14-0.pr1.atl4.us.above.net [64.125.30.242]
6 24 ms 24 ms 24 ms so-6-1-0.cr1.dca2.us.above.net [64.125.28.229]
7 96 ms 96 ms 96 ms so-6-0-0.cr1.lhr3.uk.above.net [64.125.31.185]
8 113 ms 113 ms 113 ms pos2-0.mpr1.fra2.de.above.net [64.125.29.78]
9 113 ms 113 ms 113 ms so-1-0-0.cr2.fra1.de.above.net [216.200.115.245]
10 113 ms 113 ms 113 ms pos2-0.er1a.fra1.de.mfnx.net [216.200.116.133]
11 121 ms 121 ms 121 ms fe-1-1-2-r2-DCX.de.cw.net [62.208.252.153]
12 * 122 ms 120 ms ge-0-1-0-crj1-FFM1.de.cw.net [62.208.240.226]
13 * 120 ms 122 ms ge-0-3-0-bcr3.fra.cw.net [195.2.3.49]
14 * 137 ms 136 ms bcr1.Brussels.cw.net [206.24.146.61]
15 135 ms * * belgacom-sa.Brussels.cw.net [206.24.147.154]
16 126 ms 127 ms 126 ms g0-0.ipopsbnc1.skynet.be [194.78.0.185]
17 * * * ?
18 144 ms 141 ms 146 ms 198.241-200-80.adsl-fix.skynet.be [80.200.241.198]

Notice the outbound path switches to CW. Along the outbound path through CW, the loss begins between hops 12 and 13 of the above trace:

We are good to hop 12:

@223.17#ping 62.208.240.226 co 100
Sending 100, 16-byte ICMP Echo to 62.208.240.226, timeout 5000 msec, TTL 64
Success rate is 100 percent (100/100), round-trip min/avg/max=121/121/131 ms.

And the loss starts at 13:

223.17#ping 195.2.3.49 co 20
Sending 20, 16-byte ICMP Echo to 195.2.3.49, timeout 5000 msec, TTL 64
Success rate is 85 percent (17/20), round-trip min/avg/max=122/124/154 ms.

The trace from www.ev1servers.net to the original source address takes the CW path:

223.17#trace 80.200.241.198
Type Control-c to abort
Tracing the route to IP node 80.200.241.198 from 1 to 30 hops

1 <1 ms <1 ms <1 ms ivhou-207-218-223-1.ev1.net [207.218.223.1]
2 <1 ms 1 ms <1 ms ivhou-207-218-223-9.ev1.net [207.218.223.9]
3 1 ms <1 ms <1 ms 289.ge-3-2-0.mpr2.iah1.us.mfnx.net [216.200.251.51]
4 13 ms 13 ms 13 ms pos-11-0.er1.atl4.us.above.net [64.125.29.61]
5 13 ms 13 ms 13 ms pos14-0.pr1.atl4.us.above.net [64.125.30.242]
6 24 ms 24 ms 24 ms so-6-1-0.cr1.dca2.us.above.net [64.125.28.229]
7 96 ms 96 ms 96 ms so-6-0-0.cr1.lhr3.uk.above.net [64.125.31.185]
8 113 ms 113 ms 113 ms pos2-0.mpr1.fra2.de.above.net [64.125.29.78]
9 113 ms 113 ms 113 ms so-1-0-0.cr2.fra1.de.above.net [216.200.115.245]
10 113 ms 113 ms 113 ms pos2-0.er1a.fra1.de.mfnx.net [216.200.116.133]
11 119 ms 119 ms * fe-1-1-2-r2-DCX.de.cw.net [62.208.252.153]
12 122 ms 121 ms 121 ms ge-0-1-0-crj1-FFM1.de.cw.net [62.208.240.226]
13 122 ms 120 ms 115 ms ge-0-3-0-bcr3.fra.cw.net [195.2.3.49]
14 135 ms 136 ms 134 ms bcr1.Brussels.cw.net [206.24.146.61]
15 134 ms 137 ms * belgacom-sa.Brussels.cw.net [206.24.147.154]
16 126 ms 125 ms 123 ms g0-0.ipopsbnc1.skynet.be [194.78.0.185]
17 * * * ?
18 136 ms 145 ms 142 ms 198.241-200-80.adsl-fix.skynet.be [80.200.241.198]

Therefore I would conclude the loss is along the outbound path in the cable and wireless network between hops 12 and 13.

Finally the first linux trace that did not reach www.ev1servers.net used UDP, and the trace you did from windows used ICMP and worked. We do not allow UDP traces.

Sincerely,

Randy Williams, CTO

My apologies, he wasn't clear because I've asked that since the beginning. He CAN reach ev1servers.net but not my box. My techs repeatedly tell me nothing was done to block anyone on the day that an outtage occurred (which this has occurred ever since). Is this something I need to open a trouble ticket for?

Thanks for all your help and patience!
Jason

charlottezwebb -

I would still guess your server is blocking that source address. Try double checking your firewall. If necessary drop the firewall for a brief testing period.

If that does not help, post an outbound trace from your server.

Randy Williams, CTO

Randy,

It appears he was blocked on the server level. My techs found it today as being blocked months ago for some suspicious activity. Regardless, I was repeatedly told by another person that he couldn't access ev1servers.net so I want to apologize for wasting your time. Had I known it was only my box, I would've focused my troubleshooting that way.

Thanks again for all your efforts on this matter. A+!

-Jason

Im having problem accessing one server right now.
I can see that it is up by accessing it from another EV1 server

Source IP: 83.70.64.76
Destination IP: 66.98.176.92

>tracert 66.98.176.92

Tracing route to server4.hostultra.com [66.98.176.92] over a maximum of 30 hops:

1 53 ms 52 ms 55 ms 83-70-64-1.bas2.srl.dublin.eircom.net [83.70.64.1]
2 51 ms 53 ms 122 ms ge0-1.edge1.srl.dublin.eircom.net [159.134.155.65]
3 69 ms 119 ms 80 ms pos0-0.corea.thn.london.eircom.net [159.134.191.234]
4 66 ms 65 ms 66 ms lndnuk1icx1.wcg.net [195.66.224.105]
5 138 ms 138 ms 142 ms nycmny2wcx2-oc12.wcg.net [64.200.87.149]
6 143 ms 146 ms 146 ms hrndva1wcx2-pos5-0.wcg.net [64.200.210.97]
7 164 ms 147 ms 141 ms hrndva1wcx3-oc48.wcg.net [64.200.95.74]
8 155 ms 156 ms 154 ms drvlga1wcx2-pos4-0.wcg.net [64.200.232.125]
9 157 ms 156 ms 155 ms drvlga1wcx1-oc48.wcg.net [64.200.127.49]
10 172 ms 211 ms 171 ms dllstx1wcx3-pos6-0.wcg.net [64.200.240.21]
11 170 ms 174 ms 173 ms dllstx1wcx2-oc48.wcg.net [64.200.110.73]
12 177 ms 180 ms 178 ms hstntx1wce2-pos4-0.wcg.net [64.200.240.74]
13 176 ms 178 ms 180 ms hstntx1wce2-everyonesinternet-gige.wcg.net [65.77.93.54]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
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.

It just came back after i posted this, for 10 mins it was down.


I have another issue with a different server:
IP 67.15.18.47
I submitted a ticket and it was closed but the problem is still not fixed.

The server is having a lag effect caused by packet loss which can be seen by pinging the IP.
This also happens when pinged internally from another EV1 server.
I have tried pinging other IPs which are similar to mine and those servers have the same problems!

Eric -

Thank you for the data. There was an uplink problem on 2 of the switches on the 67.15.18.xx subnet. This problem now appears resolved.

I am sincerely sorry for our failure to recognize this earlier and do appreciate you bringing this to my attention.

Randy Williams, CTO

Hi! (sorry my bad ensglish)

I cant access to www.ev1servers.net
I cant access to mi server in 207.XXX.XXX.XXX
I cant login in ev1 members section to open a trouble ticket(https)
I cant read mail (can login pop server but do timeout)
I cant use ssh (can login ssh, but it hangs)
I cant use ensim (port 19638)

I only can access this forums using a proxy.

Customers that using telefonica ADSL have same problem, but others customers with other providers not have problem.

what can i do??

Thanks in advance!

I done a tracert:

source IP: XXX.XXX.XXX (ADSL telefonica Spain)
destination IP: XXX.XXX.XXX (mi server in ev1)

This is tracert output:

[PHP]
tracert XXX.XXX.XXX

Traza a la dirección ns1.alacid.net [XXX.XXX.XXX]
sobre un máximo de 30 saltos:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 56 ms 55 ms 57 ms 10.3.86.1
3 56 ms 67 ms 57 ms 20.Red-80-58-40.pooles.rima-tde.net [80.58.40.20]
4 88 ms 92 ms 344 ms 209.Red-80-58-86.pooles.rima-tde.net [80.58.86.209]
5 199 ms 180 ms 261 ms 161.Red-81-46-0.pooles.rima-tde.net [81.46.0.161]
6 104 ms 73 ms 92 ms 78.Red-80-58-72.pooles.rima-tde.net [80.58.72.78]
7 * * * Tiempo de espera agotado para esta solicitud.
8 137 ms 67 ms 102 ms GE4-1-0-0-grtmadpe1.red.telefonica-wholesale.net [213.140.50.145]
9 90 ms 70 ms 125 ms So6-1-0-0-grtmadrr1.red.telefonica-wholesale.net [213.140.36.126]
10 90 ms 135 ms 100 ms So6-0-0-0-grtlontl1.red.telefonica-wholesale.net [213.140.38.26]
11 203 ms 354 ms 110 ms GE3-2-0-0-grtlontl4.red.telefonica-wholesale.net [213.140.37.214]
12 420 ms 87 ms 89 ms ge9-0.mpr2.lhr1.uk.above.net [195.66.226.76]
13 89 ms 133 ms 90 ms so-4-1-0.cr2.lhr3.uk.above.net [208.185.156.2]
14 110 ms 137 ms 121 ms so-0-0-0.cr1.lhr3.uk.above.net [208.184.231.145]
15 166 ms 168 ms 183 ms so-7-0-0.cr1.dca2.us.above.net [64.125.31.186]
16 184 ms 178 ms 347 ms pos1-0.pr1.atl4.us.above.net [64.125.29.41]
17 178 ms 178 ms 191 ms pos13-0.er1.atl4.us.above.net [64.125.30.237]
18 194 ms 198 ms 416 ms so-4-3-0.mpr2.iah1.us.above.net [64.125.31.25]
19 276 ms 251 ms 193 ms 216.200.251.29.ev1.net [216.200.251.29]
20 201 ms 479 ms 220 ms ivhou-207-218-245-40.ev1.net [207.218.245.40]
21 * * * Tiempo de espera agotado para esta solicitud.
22 * * * Tiempo de espera agotado para esta solicitud.
23 * * * Tiempo de espera agotado para esta solicitud.
24 * * * Tiempo de espera agotado para esta solicitud.
25 * * * Tiempo de espera agotado para esta solicitud.
26 * * * Tiempo de espera agotado para esta solicitud.
27 * * * Tiempo de espera agotado para esta solicitud.
28 * * * Tiempo de espera agotado para esta solicitud.
29 * * * Tiempo de espera agotado para esta solicitud.
30 * * * Tiempo de espera agotado para esta solicitud.

Traza completa.[/PHP]

Nailuj -

I can ping 80.32.199.48 from all of the www.ev1servers.net servers.

I can ping the 80.32.199.48 from an IP on that subnet:

223.40#ping 80.32.199.48 source 207.44.212.1
Sending 1, 16-byte ICMP Echo to 80.32.199.48, timeout 5000 msec, TTL 64
Type Control-c to abort
Reply from 80.32.199.48 : bytes=16 time=277ms TTL=237
Success rate is 100 percent (1/1), round-trip min/avg/max=277/277/277 ms.

The server does not respond to UDP or ICMP traces so the trace does not tell me anything other than both IP numbers (the source and destination) are not blocked:

ivhou-jun8# run traceroute 207.44.212.23 no-resolve
traceroute to 207.44.212.23 (207.44.212.23), 30 hops max, 40 byte packets
1 207.218.223.40 1.140 ms 1.708 ms 0.948 ms
2 * * *
3 * * *

223.34#trace 207.44.212.23 num
Type Control-c to abort
Tracing the route to IP node 207.44.212.23 from 1 to 30 hops

1 <1 ms <1 ms <1 ms 207.218.223.40
2 * * * ?
3 * * * ?

Can you ping 207.44.212.22 and 207.44.212.234 ?

Can you ping www.ev1servers.net ?

Can you ssh and/or check mail (or anything except browse) ?

What is the output from: http://www.whatismyip.com/ ?

Randy Williams, CTO

yes, i can

QUOTE

 
Can you ping www.ev1servers.net ?

yes, i can

QUOTE

 

Can you ssh and/or check mail (or anything except browse) ?

yes, i can, but, when i execute any command with output is more tan 3 or 4 lines, ssh hangs. Is like i only can receive a few packets.

Whith mail is same thing, connect to mail server sucessfully, get numbers of messages, but is hang triying first message.

QUOTE

Oputput is "Your IP is 80.58.40.107 "
but this otput is because mi isp is using a transparent proxy in port 80
mi real ip is 80.XXX.XXX.XXX.

note that problem is only for clients wich ISP is spain adsl telefonica (like me)

i have no idea about this problem

thanks in advance and sorry my bad english