NO FTP from clients behind Routing and Remote Access NAT

[Guest dwadles@gmail.com]

I have a feeling I'm just overlooking the obvious, but this is driving

me nuts.

 

Clients on a Windows Server 2003 R2 Domain cannot connect to FTP

sites. The server itself CAN.

 

Server is 2003R2 64bit, running 2 nics with Routing and Remote Access.

Basic Firewall is off.

 

When any machine behind the NAT tries to access any FTP site I get

"Connection closed by remote host."

 

I have done some digging and if I run the command "netsh routing ip

nat delete ftp" then I have slightly more communication. At this point

I am able to log in, go through user name and password, but when I try

to do a directory listing, it hangs, until the connection drops.

 

Any help is appreciated.

[Guest Baboon]

RE: NO FTP from clients behind Routing and Remote Access NAT

 

Do you know if it's using active or passive FTP? If you can find a site the

you know uses passive, you might want to see what sort of luck you have in

that case. Active FTP requires that some unsolicited connections are made

back to the client, so I am not sure what you would need to do in RRAS to

allow this. Also, does RRAS have a built-in filter for FTP? I don't believe

it does. I'm not too familiar with RRAS alone as a solution. I use ISA so I

can't be of much help beyond this.

 

"dwadles@gmail.com" wrote:

> I have a feeling I'm just overlooking the obvious, but this is driving

> me nuts.

>

> Clients on a Windows Server 2003 R2 Domain cannot connect to FTP

> sites. The server itself CAN.

>

> Server is 2003R2 64bit, running 2 nics with Routing and Remote Access.

> Basic Firewall is off.

>

> When any machine behind the NAT tries to access any FTP site I get

> "Connection closed by remote host."

>

> I have done some digging and if I run the command "netsh routing ip

> nat delete ftp" then I have slightly more communication. At this point

> I am able to log in, go through user name and password, but when I try

> to do a directory listing, it hangs, until the connection drops.

>

> Any help is appreciated.

>

[Guest dwadles]

Re: NO FTP from clients behind Routing and Remote Access NAT

 

>I have a feeling I'm just overlooking the obvious, but this is driving

>me nuts.

>Clients on a Windows Server 2003 R2 Domain cannot connect to FTP

>sites. The server itself CAN.

>Server is 2003R2 64bit, running 2 nics with Routing and Remote Access.

>Basic Firewall is off.

>When any machine behind the NAT tries to access any FTP site I get

>"Connection closed by remote host."

>I have done some digging and if I run the command "netsh routing ip

>nat delete ftp" then I have slightly more communication. At this point

>I am able to log in, go through user name and password, but when I try

>to do a directory listing, it hangs, until the connection drops.

>Any help is appreciated

 

_______________________________________________________

 

I have tried using CuteFTP in PASV mode, I cannot successfully create

a connection to the domain controller running IIS. The domain

controller is also the gateway. A Windows Server 2003 R2 64 bit Intel

whitebox server. I AM, however, able to set up an ftp server on

another client inside the network and access THAT machine from another

client in the network, so I know the network hardward isn't limiting

it.

 

I have ruled out everything except the 2003 box, this is my first

experience with an x64 server, and I've already seen that IIS must be

running in 64 bit mode to support exchange 2007, but that should have

no bearing on routing and remote access acting as a gateway on the

network.

 

So I am left not being able to not successfully connect to any FTP

server outside of the network, OR the gateway itself.

 

Is there a possibility of the Intel Management software running on the

mainboard and feeding to the NICs having anything to do with this?