Any computer techies out there?

[ChrisHill]

I upload files to my website via CuteFTP Pro.

Suddenly I have been unable to login, unable to get beyond the password and then it timesout.

I contacted Cuteftp (Globalscape) after double checking all login details were correct. They suggested I try connect via Windows Command Prompt and if I could NOT connect here, it was NOT a Cuteftp software problem. I tried... and could NOT connect this way.

I then connected my website host who suggested I download Filezilla, because they could connect to my server via this software. I tried this and still could not connect.

I have tried disabling the Kaspersky Firewall (Windows firewall also off) and still cannot connect.

However.... I have tried to connect via my home computer and the connection works, so the problem is with my PC 

I have uninstalled the last Windows update and IE update but still no luck, but SOMETHING has changed in the last few days and is blocking my connection to FTP.

Anyone able to suggest a possible solution please.

Thanks,

Chris.

[Peachy]

Have you tried a system restore to a time that you know it worked?

[BillyH]

what was the exact error messaged from Filezilla and cute?

[ChrisHill]

what was the exact error messaged from Filezilla and cute?

Cuteftp:
   [30/10/2008 14:02:11] 331 Please specify the password.
COMMAND:>   [30/10/2008 14:02:11] PASS *****
ERROR:>      [30/10/2008 14:03:12] Timeout (60000 ms) occurred on receiving server response.


Filezilla:
Response:   331 Please specify the password.
Command:   PASS *********
Error:   Connection timed out
Error:   Could not connect to server


Command Prompt:
331 Please specify the password.
Password:
Connection closed by remote host.


Oh dear Peachy, not sure where/when my last system restore was 

[Peachy]

You should be able to see when it was if you go into Control Panel | Performance and Maintenance. When the calendar comes up the days with restore points will be in bold. Your computer will have done some automatically. Hopefully there will be one you can restore to. You won't lose any data by doing it and you can always go back again if needed.

[BillyH]

The most common reason this happens is because you may be behind a proxy or firewall, to overcome this make sure that passive mode is turned on in your ftp client (it will be under settings).

in core i think its the PASV sheckbox

[Alan Mooney]

Hi Chris,
Can you log into your router interface?
You need to make an exception for port 20 & 21 as these are the ports cuteftp allows for ftp connections.
HTH
Alan

[Peachy]

I had terrible trouble connecting via ftp for a while. I tried all sorts of thing, at home, at work, no luck. I knew the username and password but it still wouldn't let me do it. So I rang the help desk. They could do it so they said they couldn't help me further.

Guess what the problem was?






The password was case sensitive. DOH! How embarrassing.

[ChrisHill]

Hi Chris,
Can you log into your router interface?
You need to make an exception for port 20 & 21 as these are the ports cuteftp allows for ftp connections.
HTH
Alan

Thanks for all the replies so far.

Ok, quick update. I have come to the conclusion it PROBABLY IS a router problem.
 
If I take my laptop into the house I CAN login to Filezilla via the network there (identical model of router), but returning the laptop to the studio, I cannot.

The router is connected to my main PC. Neither PC or laptop can connect to CuteFTP, Filezilla, or windows cmd prompt ftp via this network.

I have reset router settings to factory default and reconfigured again but still no change. Internet/email etc is fine, I just cannot connect to ftp. This had been working perfectly for months until 4-5 days ago.

I have tried adding a new rule to outbound services (allow FTP ports 20, 21) but the existing one seems to 'always allow all' anyway. Unfortunately I am not techie enough to know what doors I am actually opening if I get carried away trying other changes!

Any more help really appreciated.

Chris.

[Alan Mooney]

Hi Chris,
Given that they are both identical routers, can you back up the settings from the one that actually works for you? and then copy them to the new router.
If that doesnt work, go into the interface of the router that does work and write down all settings, then go to the router that doesnt and make sure the settings all match. Im certain its a port setting, what I think you actually need to do is route ports 20 & 21 to your own ip, but try copying the settings first, see how that works for you.
Alan

[ChrisHill]

Thanks Alan, I'll give it a go.