Having trouble connecting to my webspace via FTP. I've been back and forth with Charter. I haven't really got any good ideas from them. Everything they say will fix the problem... doesn't.
I have a Surfboard SB161 Modem through a Dlink router. I'm using a hardwire connection, not the wireless. I'm using the latest version of Filezilla and I cannot connect to my webspace. I have confirmed all the passwords and everything else in in order. I recently reset and reconfigured my router but I don't remember ever doing anything that would effect the FTP settings. I am using OpenDNS addresses.
wHEN I run the configuration wizard from within Filezilla everything comes back as it should and says everything is working properly. Filezilla has the proper setting to obtain my external IP address etc. It's just when I try to connect to my webspace it fails.
it keeps telling me "could not connect to server"
I'll take any help I can get.
Nothing but problems lately
Does the port to that IP appear "open" if you try connecting to it with the SG security scan on the main site ?
Does the FileZilla log give any hints at all?
What happens exactly ? For example, if you can make the connection but don't see a directory listing it is usually the passive mode setting.
FTP connections actually use more than one port... Defaults are port 21 and 20, but they can be changed (also 990 for FTP SSL connections)... Then there is a range of ports used for passive data connections...
If you had it working before though, it shouldn't be too hard to figure out. I'd try using a non-standard high port first, and passive mode. Your ISP can simply be blocking standard server ports.
The log should really help in determining the problem.
Does the FileZilla log give any hints at all?
What happens exactly ? For example, if you can make the connection but don't see a directory listing it is usually the passive mode setting.
FTP connections actually use more than one port... Defaults are port 21 and 20, but they can be changed (also 990 for FTP SSL connections)... Then there is a range of ports used for passive data connections...
If you had it working before though, it shouldn't be too hard to figure out. I'd try using a non-standard high port first, and passive mode. Your ISP can simply be blocking standard server ports.
The log should really help in determining the problem.
Thank you everyone... so far.
1. The SG Security Scan found no open ports.
2. When I run the configuration wizard in FileZilla it runs a test on one of it's own servers and shows that everything is configured properly.
3. When I try to connect to my personal webspace through FileZilla I get the following response...
Status: Resolving address of webpages.charter.net
Status: Connecting to XXX.XXX.X.XX:21...
Error: Connection timed out
Error: Could not connect to server
4. I've tried Passive mode using a named range of ports but I still get the same thing.
I'm going to try and bypass the router and I'll report back.
1. The SG Security Scan found no open ports.
2. When I run the configuration wizard in FileZilla it runs a test on one of it's own servers and shows that everything is configured properly.
3. When I try to connect to my personal webspace through FileZilla I get the following response...
Status: Resolving address of webpages.charter.net
Status: Connecting to XXX.XXX.X.XX:21...
Error: Connection timed out
Error: Could not connect to server
4. I've tried Passive mode using a named range of ports but I still get the same thing.
I'm going to try and bypass the router and I'll report back.