Weird FTP Issue

So, for a long while now, I've been using FireFTP to access my employer's FTP to update the website with images and such. And there wasn't any problem. But, now, I have a strange issue, in that if I attempt to connect to that same FTP, the connection times out repeatedly. So I tried another FTP program, FileZilla, to see if that will work, but no, it times out as well. The kicker of this problem is that this seem to be isolated with only my computer in my sig, while if I try with another computer (like a Debian Unix desktop with FileZilla), it connects just fine.

So, what could be the issue be? Is there something I can try on my computer to allow it connect again? Or should I contact the host that controls the FTP?

 

You firewall may be causing the problem. I did an update on my av/fw and it changed the order of the fw rules which prevented me from accessing my servers.

 

I use Norton 360 with its own firewall. So I went into the firewall section and changed the programs from Auto to Allow. Unfortunately, that still didn't seem to fix the problem, this one computer is timing out while others go through fine.

I asked the host if perhaps I got blacklisted somehow, if they have such a feature, and try and get them to fix it if they do. Otherwise, I'm not certain what else it could be.

 

Norton has never behaved right for me, and I will NEVER load it on another pc. Disable it completely, reboot then try again.

FireFTP does not work with one of my servers but FileZilla does with all. So try a different FTP program to confirm.

Years ago I found that one of MS network services was causing a conflict but I don't remember which one.

 

I've used a couple of FTP programs, none work with this particular server I want to connect to. And disabling Norton entirely does nothing. It's like my computer is being denied access to this server via FTP in the form of timing out, but I have no idea why...

 

Can you ping the server from that computer?

Use a port scanner to see if the needed ports are open.

If going through a FW remember to use passive mode.

Shot in the dark; Did by chance did the needed services not be installed on that computer?

 

You can always use telnet to see if you're getting anything at all, telnet foo.com 21 and see if you get the login banner.

If that doesn't work you can always use a sniffer to see what is actually going over the line, but it could be something simple like a firewall problem.

 

Pinging to the IP address of the server in question works fine from this computer. I've tried both Passive and Active modes in all FTP programs and they both time out regardless. Telnet works fine.

The FTP to this server worked a couple of weeks ago, it only just started doing this, but perhaps I should do a port scan just in case something may have changed without my knowing. I also haven't changed anything with my computer services during this time, either.

 

So if you telnet to the FTP port (21) you get the login banner? Maybe you need to make an exclusion for your FTP program in your firewall settings.

I'm sort of confused tho. If your connection is timing out before you login, that's one thing, some sort of firewall problem or something. But if your connection is timing out AFTER you're logged in to the server, maybe you just need some keepalive packets, I know there's definitely a setting for that in filezilla. Good luck!

 

I assume you are using windows. Have you tried using "windows explorer" to access the server? My Computer/Computer --> Address Bar --> Enter: The web address (ei: ftp://youraddress.net/com/org/biz )--> Enter credentials. While being insecure, it might rule some possible causes.

 

According to Filezilla, it's timing out before logging in. It sets the IP address and tries to connect, but sits there for a while and times out. Using Windows Explorer for FTP to the same location failed to work, too.

As I said, I'm using Norton 360 and I have gone into the Firewall of it and set the FTP programs to allow, but it's still not working. It's really weird...

 

I understand you now, it does sound like the kind of thing that happens when your firewall restricts connections though. If you're using passive FTP, it shouldn't be a problem of incoming connections obviously. Maybe you need to add a specific exception for the filezilla .exe? I don't know exactly, it's been a long time since I had to fight with Mr. Norton.

 

Why not go to GRC.com and have them do a port scan with that pc. I suspect it's Norton.

 

I've never used Norton (Fortunately haha), but since it includes its own firewall, does that disable the pre-installed windows firewall? I assume it does, since no one mentioned checking that. If not, it might be worth a look to see if windows firewall is blocking port 21. I don't think it does that by default though. Also, just another wild guess. You aren't going through a proxy are you? (iexplore-->Internet Options-->Connections-->Lan Settings--> Proxy Server.) It should be unchecked under normal circumstances.

 

Norton 360 has overridden the Windows Firewall, as expected. No, no proxy is set on this computer.

Which program exactly from GRC does the port test? They have so many to choose from.

 

Shieldsup https://www.grc.com/x/ne.dll?bh0bkyd2

 

According to the All Ports scan, all ports except four were Stealthed, while those four I mentioned were open (25, 80, 81 and 443). This scan was done at work, maybe I'll try it again when I'm at home.

I tried again with a desktop that sits at work, and it says the same thing. But this desktop is one I know that can connect to the server in question via FTP just fine.

 

A port scan is only good for incoming connections, if you are using passive ftp that is not relevant. Active FTP vs. Passive FTP, a Definitive Explanation

I think norton keeps a log somewhere of blocked stuff. You might want to see if it's got anything in there for filezilla or whatever other FTP programs you've tried.

 

"The logs created by norton can not be read via notepad. You can read them this way:
1. Open NSS main window
2. Click on Tasks
3. Click on View Security History
4. On the new window you can select only the firewall history, and clicking on details you can read the full logs"
Original Source
It's for Norton Security Suite, but I'm sure 360 is pretty similar.

 

OK, you know what's even weirder now?

Finding out the problem has gone away. Filezilla on this machine in question now connects to the server just fine. I opened it up to try and get a new log in Norton 360 to view and report back here, but it's working fine all of a sudden.

I don't know what caused this in the first place, but I guess we can call this resolved for now. I have no idea how it got fixed, though...

 

Glad to hear it's working. Let us know if it starts acting up again.