|
| | | Forum Newbie
Group: Forum Members
Last Login: 8/1/2007 2:14:32 AM
Posts: 2, Visits: 5 |
| I've been using WS_FTP Server for quite some time now with great results. I also use the dynamic IP forwarding service probided by NO-IP.com. But for some reason it simply stopped working and I cannot figure out for the life of me what happened. Everything makes me think that everything is working properly until I try to connect. This is what happens:
Finding Host xxx.no-ip.com ...
Connecting to xxx.xxx.xxx.xxx:21
Connected to xxx.xxx.xxx.xxx:21 in 0.000000 seconds, Waiting for Server Response
Failed to receive response after connect
Host type (1): Automatic Detect
By connecting through Firefox (ftp://login:pass@xxx.no-ip.com or ftp://login:pass@xxx.xxx.xxx.xxx) it acts as if it's loading a page, but nothing EVER comes up or EVER times out. Just continual loading.
That's what happens if I try to use my external IP, either the one provided by no-ip.com or my normal IP. Then I go and use 127.0.0.1 or router provided internal IP and it connects immediately and shows me a list of my folders. So that means that my no-ip service works, and ws_ftp server is functioning because it displays my folders and asks for login/password properly. I've tried various methods of port forwarding, and have even enabled DMZ to point to the server computer. I've shut off my software firewall (ZoneAlarm) and disabled the Windows firewall.
I can ping both forms of my external IP and both are found to be valid.
Does anyone have a clue as to why this is happening?
Any information is much appreciated.
Thank you
~Void |
| |
| | | Forum Newbie
Group: Forum Members
Last Login: 8/1/2007 2:14:32 AM
Posts: 2, Visits: 5 |
| Anyone have any ideas at all?
~Void |
| |
| | | 
Time Traveler
Group: Forum Members
Last Login: 10/4/2011 10:35:05 AM
Posts: 265, Visits: 339 |
| | Hi, I think everyone's problem is that no one wants to just state the obvious: Some device (Cable/DLS router, Firewall, IDS) or some software (Windows firewall, personal firewall, even the virus scanners that now include port-blocking) is obviously interfering with packets addressed to your public IP on port 21 - or, they are not being forwarded through NAT from your public IP to your private IP space. Problem is - none of this will really help you. You (or someone) needs to get a full understanding of how TCP/IP packets flow from your Internet connection to your WS-FTP server, what devices/systems are involved, what software/utiltities might be installed, etc. - and then determine how to "track" the progress of the packets through those systems to identify where they get "stuck". Keep in mind, the problem might not even be "inbound" - it's possible that your connection request actually REACHES the WS-FTP server, but that you have some block in place that prevents the reponse packet to be translated back to the public IP address and then passed through to that address.
Best Regards,
Andy Schmidt |
| |
|
|