Problem accessing FTP server

[Softbreeze]

I am replacing my LinkSys Firewall Router with a PC running Wingate. I'm using NAT. My Cable modem connects to my Wingate PC using a DHCP address and my internal Lan connects using 192.168.10.1. I have an FTP Server on 192.168.10.21 and a Webserver on 192.168.10.80.

Using the Linksys I would forward port 21 to 192.168.10.21 and port 80 to 192.168.10.80. I then could access both from some other location using ftp.mydomain.com and http://www.mydomain.com. This works.

Using WinGate I redirect port 21 to 192.168.10.21 (see attachment). I then run FTP from a command line from some other location and it connects and allows me to login. When I try to issue any ftp commands (ie. cd, ls, get, etc) I get the following error:

421 Service not available, closing control connection.

I am sure that this is something I have done in the set up of wingate but I'm not sure what.
I have started with a standard install, disabled DHCP and DNS since I'm using AD on my network and already provide both of these services. I have synchronized my AD users and added the port 21 redirection to 192.168.10.21. Verified that the Wingate FTP Proxy service is running.

I can FTP to my FTP server from behind Wingate and I can use ftp to get to other ftp sites as an ftp client.

Any ideas what I might have done wrong?

Attachments

Port21.png (7.95 KiB) Viewed 5182 times

[adrien]

Hi

I searched our codebase for "closing control connection" and came up with nothing, so it looks like that error is not coming from WinGate.

Did you check your FTP server logs?

Regards

Adrien

[Softbreeze]

Well I looked closer and the actual error fromthe command line is '500 Invlid Port Command'. I also found an article http://support.microsoft.com/?id=281193

I'm sure this is something I have done. The article suggests that the problem may occur when the request tried to open up other ports for the return.

BTW: the log file only showed a successful login and CWD commands

I'm still looking....

[Softbreeze]

If anyone has setup an FTP server on their internal network behind a WinGate server using port redirection, could you share the steps you used? I'm stuck.

[adrien]

Hi

I think some of the problem is that you only have 1 NIC in WinGate.

I think you might have more luck if you use the FTP proxy, and set server requests settings to connect through to your other FTP server.

Is there any reason why you don't just forward port 21 directly to the FTP server from your DSL/NAT if it's on the local network?

Adrien

[Softbreeze]

>>I think some of the problem is that you only have 1 NIC in WinGate.

Actually I have two nics in the WinGate PC. One connects to the Cable Modem and the second connects to a hub for my internal lan. All my PC's are then attached to this hub.

>> I think you might have more luck if you use the FTP proxy, and set server requests settings to connect through to your other FTP server.

I tried removing the entry I created under port security to redirect the port and configuring the FTP Proxy as you suggested. I don't get the login then.

>> Is there any reason why you don't just forward port 21 directly to the FTP server from your DSL/NAT if it's on the local network?

My Cable modem is esentially a bridge. I was using WinGate for my firewall and NAT.

They only difference between this configuration and my previous one is that I replaced my Linksys firewall router with a WinGate PC. My end objective is to use Puresight. My first testing is to get WinGate working (which it does), then get my FTP Site working, and then get my website working. After which I'll test PureSight.

I want to be able to 'put' files on my FTP server from the internet. I thought that using NAT and Port redirecting would do it.


Here is my network:

Attachments

nsw.jpg (16.68 KiB) Viewed 5135 times

[adrien]

OK sorry, didn't read your first post properly.

I'd try the ENS redirect again, but check the option "Don't translate source IP".

Regards

Adrien

[Softbreeze]

That fixed the prolem. I'll remember this when I set up my website.

Thank you!