Cannot establish an ftp connection from win2003 servers

[theotokatos]

When I am trying to open an ftp connection (eg to ftp.microsoft.com) from win2k, win2k server or winXP it works perfect. BUT when I am trying from my servers (win2003 all versions) the connection closing after I type the user "anonymous" without asking me for password.

Do you have any idea?

[gunderstone]

Unless it is a personal firewall (or edge firewall that the other mentioned boxes are not subjected to) setting that is blocking the response this is not the expected behavior.

Can you repro this on another W2K3 system in your environment?

When I attempted to open an FTP session from the command line (which is where I am assuming you tried it) on a W2K3 virtual system here as a test I was able to get to the point of entering a password.

The text is below (I don't have anonymous access permitted so my attempt failed)


C:\Documents and Settings\Administrator>ver

Microsoft Windows [Version 5.2.3790]

C:\Documents and Settings\Administrator>ftp
ftp> open
To systems.net
Connected to systems.net.
220 ProFTPD 1.2.9 Server (ProFTPD)
User (systems.net:(none)): anonymous
331 Password required for anonymous.
Password:
530 Login incorrect.
Login failed.
ftp> systems.net

[theotokatos]

Thak you gunderstone

I believe that you are right. I have several servers running under win2003 and some of them are running under win2003 64 bit without antivirus but they all seems to have the same behavior.
I have a firewall in front but all the servers are under the same rule. I can't understand why the win2k servers and the workstations are connecting properly.
Actually I found out today that there is one win2003 server that is working properly!!!
Is it possible to be an Active Directory problem?
Is it possible to be a windows componet difference?

[gunderstone]

Without some additional investigating I wouldn't be able to tell you for sure (I do not currently have access to 64 bit versions of the OS)

What I can tell you is that W2K systems are less secure be default than W2K3 and that is probably the reason why you can make the connections with the 2000 boxes.

I don't think it is an Active Directory issue as FTP should not come in to play. You could try hitting the remote systems by their IP address (that would take DNS out of the issue)