Solving FTP Connectivity Issues with IE

[russ_watters]

I'm running an FTP server at work on a pretty basic network: the server is really just a file server running Win2k Pro and GuildFTP for the FTP server. We have Comcast Cable and a Belkin router. I have ports 20 and 21 forwarded, but can't (usually) access the FTP server through IE. I get a timeout error. I can access the FTP server though an FTP client - its called SmartFTP. Strangely, once connected via the client, I can then connect through IE. Switching in and out of passive mode doesn't seem to help anything. The client shows the same timeout error but is still able to connect.

I need to be able to connect through IE because I have clients I want to give access and it has to be idiot-proof (a link to the ftp server in an email).

If it helps, the FTP is: ftp://68.42.21.94/[/URL] (read, but no write access).

Any ideas?

 

[dduardo]

Is your firewall setup correctly?

http://www.landfield.com/wu-ftpd/mail-archive/wuftpd-questions/2001/Nov/0202.html

 

[russ_watters]

Is your firewall setup correctly?

My firewall (the belkin router) doesn't have much in the way of options. I already set up port forwarding for ports 20 and 21 (virtual server), but don't see how to allow port commands (though since the error is a timeout error, I'm doubting that's it). Any ideas? And for the port forwarding, TCP or UDP (what are they?)? And I'd rather not put the server outside the hardware firewall with a software firewall (but I might)...

Thanks for the help...

 

[dduardo]

For passive connections you need these ports open:

60000-65000

 

[dduardo]

I just did an nmap scan of your ip and the ftp-data port 20 is closed. That might be your problem.

 

[russ_watters]

I just did an nmap scan of your ip and the ftp-data port 20 is closed. That might be your problem.

Hmm. I don't see how that could be - I have the port listed in the "virtual server" section of my router setup page. But then there's also the "Special Application Ports" section - what's the difference?

 

[dduardo]

I don't know the difference. Try adding the ports to that list to see what happens.

Another test you can do is to DMZ the machine and see if it works. If you still have problems then you know it is a server configuration problem and not the firewall.

 

[russ_watters]

Another test you can do is to DMZ the machine and see if it works. If you still have problems then you know it is a server configuration problem and not the firewall.

I'm going to work on it this weekend and if I can't get it to work any other way, I'll DMZ it and set-up a software firewall. Since I only need it for a project that is going to last about a month, I'm not too worried about security that way.