05-27-2016 07:51 AM - edited 05-27-2016 07:53 AM
There's a timeout happening between verizon-gni.net servers and Verizon's nyc4.alter.net servers - then another timeout between alter.net and the level3.net server in Phoenix (see 4 and 6 below). Here's the route:
Solved! Go to Solution.
06-24-2016 02:27 PM
Got the answer!!!! After being on the telephone with Verizon and GoDaddy for hours for two days, even though GoDaddy says it's Verizon's fault, and Verizon says it's GoDaddy's fault....turns out, it IS GoDaddy's fault. Their one particular hosting server was blocking me. (we looked over and over at the "traceroute"). By moving me to another GoDaddy server (which took about a minute, without me needing to upload the files again), all works fine! It's getting GoDaddy to do it, at no charge. They fought me, at first, wanting to charge me, to change to an "newer" server, but finally, they did it for free. Now, life is good again! and I can FTP to my heart's content. Yah gotta push GoDaddy. and not Verizon.
05-31-2016 11:38 AM - edited 05-31-2016 11:39 AM
Thanks for the suggestion. Just tried that... it had no effect.
Just to reiterate - if I log in to a different network (like Comcast or AT&T) - I can FTP into the account fine. It's the pathway between Verizon's servers and GoDaddy's that are not working. The reroute/blocking is on Verizon's side.
06-07-2016 06:16 AM
Just FYI - it's been weeks and I still can't access my hosting account via Verizon. I was hoping that with the strike over that some competent techs would be back and fix the peering issue between verizon-gni.net and the nyc4.alter.net servers.
. I am now noticing LONG lags at connecting via http to some sights and services now at other IP addresses - so clearly something is happening at Verizon. HELP!
06-07-2016 10:18 AM
Asking a Tier 1 agent on phone is probably going run you through the basic troubleshooting steps.
but has the issue been taken up with a NT ? normally 4 is always going to time out as its the transition between verizon actually network and to the outside and if it fails immediately and keeps failing then a NT could possible call it a network issue but if it times out at 4 as normal and then does not time out after that but later down the trace it would be consider outside of the verizon network by a NT
06-07-2016 12:43 PM
I got a really good tech who has taken the issue up to the NT guys. They admitted that they have known about the issue between Verizon and GoDaddy connectivity for a couple of months and are trying to fix it. I have a support ticket... we will see what happens. They ran a traceroute from my local machine and it is, indeed, a Verizon problem between the local Verizon servers and the NYC.alter.net (also Verizon) connection. They also confirmed that it is unusual and "weird".
06-08-2016 06:37 PM
06-09-2016 06:51 AM
The only way you can get a support ticket started...and I HIGHLY recommend you do... is to call them. I put off calling for a while because of the strike and tried online methods - but this is such a high level and unusual problem - that you simply have to talk to someone there. I called from my home phone - which is where the account is - so the steps mighyt be differfent if you are calling from another line.
Call 1-800-837-4966 - you will start the phone tree. Proceed as follows -
1. choose TECH SUPPORT
2. choose FIOS SERVICES
3. choose INTERNET
4. say "I'm calling about something else" after they give you choices.
After listening to a disclaimer message - you will then be transferred to either a lavel 1 tech support person or be on hold for a while first. I called at 10:00AM on a tuesday and got right in. Be prepared to wait a really long time, though...or to at least be on the phone for a while with tech support (get the bathroom break out of the way beforehand, get something to occupy yourself, and get comfy!)
They will need to run a traceroute from a computer connected to the account in question - so be prepared to let them remotely take over your machine. Macs have a problem with this - I switched to a windows machine for their tests. State clearly what the issue is and what you've done to see that it's an issue for Verizon - not GoDaddy.
The more people who let them know that this is an issue and give them trace routes will undoubtedly help them fix the issue sooner.
06-16-2016 05:59 PM
It looks like one of the nodes along the route is blocking traffic on port 21. I'm assuming you are using the old original FTP, which uses TCP port 21. You can't find where the block is on port 21 by running a traceroute, since the trace uses ICMP packets. You are experiencing a block on TCP protocol packets on port 21, which are treated differently from ICMP packets. When you see a blank row on the traceroute report it only means that one specific node is not responding to echo back a report on the trace packets but may well be sending them forward, letting you see the rows below it on the trace.
If your GoDaddy account is for Managed Workpress hosting, you might try using SFTP, a secure version of FTP, which uses different ports. GoDaddy supposedly supports SFTP, but only for Managed Wordpress hosting.
While you are waiting for a network fix, you might be able to reach your FTP site successfully by using an access point located in a different geographic area. This can be accomplished by using one of the free shell accounts available on the internet. There were formerly a great many available, but now you should still be able to use such sites as grex.com or freeshell.com.
Also, if you can use cpanel on the GoDaddy hosting site, you should be able to use a direct upload/download feature that uses port 80 HTTP instead of FTP.
06-16-2016 08:15 PM
The * does not mean dropped packets.
In this case it just means that the device is configured to not respond to ICMP packets.
Not a problem.