ftp

[Guest]

I cannot to other ftp servers.
I'm trying to connect from a Windows 2000 server (domain controller).The FTP server is configured to accept connections from the IP address of the local firewall. My local server & PCs are all behind the same firewall.
I tried to connect from a command prompt (ftp xxx.xxx.xxx.xxx); I enter the user ID & password when prompted; I was connected but as soon as I enter a DIR sub-command I got nothing & the session eventually closes.
I know I can connect to this ftp server, I did so from a Windows XP Pro PC from this domain.

Thanks in advance for the help

 

[Wadester]

Sam [[email protected]] posted:

I cannot to other ftp servers.
I'm trying to connect from a Windows 2000 server (domain
controller).The FTP server is configured to accept connections from
the IP address of the local firewall. My local server & PCs are all
behind the same firewall. I tried to connect from a command prompt
(ftp xxx.xxx.xxx.xxx); I enter the user ID & password when prompted;
I was connected but as soon as I enter a DIR sub-command I got
nothing & the session eventually closes.
I know I can connect to this ftp server, I did so from a Windows XP
Pro PC from this domain.

Thanks in advance for the help

You most likely need to use passive mode, which is not supported by the
FTP.EXE command-line utility.

Google on "ftp passive mode" for more details. You may either need to:

1. Reconfigure your firewall to allow incoming connections from your FTP
server using any port, or
2. Use FTP software that supports PASV mode transfers.

ws

 

[Guest]

Passive mode doesn't help
I've also tried connecting through IE 6 & RoboFTP
Why can I connect from a Win XP but not Windows server, both behind the same firewall

Sam

 

[Wadester]

Passive mode doesn't help.
I've also tried connecting through IE 6 & RoboFTP.
Why can I connect from a Win XP but not Windows server, both behind
the same firewall?

Not sure - are you sure the firewall is NATing everything to the same
address? Maybe there are specific FW rules for the server that you aren't
taking into account?

You could also run a packet sniffer at the client and server, and get a
better idea of what's going on.

ws