- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm trying to FTP into my website server and I'm getting a connection timeout error. When I called GoDaddy about this we ran a traceroute and discovered that the problem appears to be on Verizon's end. Here's the trace.
1 10.0.1.1 (10.0.1.1) 1.575 ms 1.403 ms 1.311 ms
2 lo0-100.nrflva-vfttp-320.verizon-gni.net (96.225.134.1) 5.561 ms 4.631 ms 5.383 ms
3 t1-4-0-11.nrflva-lcr-22.verizon-gni.net (100.41.9.62) 9.071 ms 7.386 ms 9.185 ms
4 * * *
5 0.ae4.br1.iad8.alter.net (140.222.227.9) 17.245 ms 17.832 ms 17.428 ms
6 * * *
7 * * *
8 * * *
9 * * *
10 ae-7-7.ebr3.dallas1.level3.net (4.69.134.21) 79.594 ms 79.147 ms 82.118 ms
11 ae-3-3.ebr2.losangeles1.level3.net (4.69.132.77) 80.336 ms 76.548 ms 77.434 ms
12 ae-92-92.csw4.losangeles1.level3.net (4.69.137.30) 75.439 ms 75.758 ms 75.454 ms
13 ae-4-90.edge1.losangeles9.level3.net (4.69.144.202) 75.234 ms 74.674 ms 77.912 ms
14 4.53.228.238 (4.53.228.238) 81.555 ms 82.520 ms 80.463 ms
15 be39.trmc0215-01.ars.mgmt.phx3.gdg (184.168.0.73) 88.507 ms 88.341 ms 88.372 ms
16 be39.trmc0215-01.ars.mgmt.phx3.gdg (184.168.0.73) 90.139 ms 89.391 ms 89.174 ms
17 ip-97-74-255-129.ip.secureserver.net (97.74.255.129) 88.162 ms 271.402 ms 88.117 ms
I then spent 1.5 hours on the phone trying to resolve this issue with no success. One thing that was rather strange is I suggested that we break the lease to my Apple router to test whether my assigned IP address is part of the problem. The tech support rep tried several times to break the lease and even resorted to an ONT reset and FIOS would not reassign me a new IP Address. That has never happened before, and no, I do not have a static IP address.
I need to fix this becasue I cannot access my website. Where do I go from here?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Mot sure what ip address you are trying to FTP to.
Ignore the **** in the middle of a traceroute.
There are times when a device is configured to not respond to pings as part of the traceroute.
If #17 is the destination you are trying to get to, then it is not a netowrk problem on Verizon.
Have you checked your apple rotuer to make sure it isn't blocking FTP?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Are you using a TLS secured FTP server? Could be an MTU issue, just a thought.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have EXACTY the same problem. Lowering the MTU has no effect. This is a connection that has worked fine for 14 years with no changes. It jsut stopped working between Verizon and GoDaddy's servers. Same time out / route around from verizon-gni.net to the level3 server via one of Verizon's alter.net server. I have tried calling Verizon - but after being on hold for an hour gave up. This is not something their automated system can handle either 😕
Here's my traceroute:
traceroute to 68.178.254.200 (68.178.254.200), 64 hops max, 52 byte packets
1 wireless_broadband_router (192.168.1.1) 0.964 ms 0.574 ms 0.546 ms
2 lo0-100.nycmny-vfttp-314.verizon-gni.net (108.30.14.1) 7.952 ms 7.953 ms 6.996 ms
3 b3314.nycmny-lcr-22.verizon-gni.net (100.41.219.203) 9.597 ms 8.623 ms 8.418 ms
4 * * *
5 0.ae7.br3.nyc4.alter.net (140.222.226.209) 9.076 ms
0.ae1.br3.nyc4.alter.net (140.222.229.97) 9.088 ms
0.ae8.br3.nyc4.alter.net (140.222.226.211) 7.027 ms
6 * * *
7 ae-0-11.bar2.phoenix1.level3.net (4.69.148.114) 72.062 ms 71.548 ms 72.401 ms
8 4.28.83.74 (4.28.83.74) 72.627 ms 71.951 ms 72.396 ms
9 ip-184-168-0-117.ip.secureserver.net (184.168.0.117) 74.993 ms
I really have no idea what we are going to do. I know I can connect via other ISPs (comcast) - it is a Verizon specific problem. Is the strike over? Is there anyone there who can fix this?