asked on

IIS 7 FTP on Windows Server 2008 R2 - ftp: connect :Unknown error number

Hi,

I'm having problems getting FTP to work on one of my Windows Server 2008 R2 boxes. When I try to connect I get ftp: connect :Unknown error number. If I do a putty session on the box I get an error "Network Error, Connection Refused".

This server is a physical box and I have two others which are virtual machines. The two VMs work fine and have the exact same configuration as the physical box. The Windows Firewall is turned off and we have a rule on our Cisco firewall to allow port 21 and 20 for the three servers.

I've tired creating the FTP site over again several times, uninstalled and reinstalled the FTP role, restarting the server, rebooting the box, etc.

Does anyone have any suggestions what can be done to troubleshoot this further?

Thanks

Brad Howe

Limit everything from Routers, firewalls and DNS and do the following.

1. Remote to the Server

2. Open CMD and try the following.
CMD> telnet internal.server.ip 21
CMD> telnet internal.server.ip 20

This should connect if your local server firewall is disabled OR properly configured to pass the ports. If not (connect denied....) Check that IIS services are on and the FTP site is STARTED and on the correct port.

3. Open CMD and try the following.
CMD> ftp internal.server.ip
Login with the local administrators id.

Let us know,
Hades666

COV-Webmaster

ASKER

I've remoted to the server and run telnet with port 21 and 20. The command window opens briefly and closes right away with no indication of what might be wrong. I did the same think on one of the servers that works. On that server I get 220 Microsoft FTP Service.

If I open a CMD prompt and ftp internal.server.ip I get ftp underneath and no options to log on. On the servers that work I get prompted for a userid and password the way I should. Both the FTP and IIS servers are stared on this server and it is configured for the correct port.

Any other suggestions?

Brad Howe

OK, if it doesn't work locally, then it is not a routing/DNS issue so far.

Test via TELNET
Did you install the "telnet Client" on the sever? If you did, then you should be able to do the following. This verifies that the service is running and the firewall is disabled.

1. Open a CMD prompt
2. Type "telnet"
C:\>telnet
Result show be
Welcome to Microsoft Telnet Client
Escape Character is 'CTRL+]'
Microsoft Telnet>
3. At the prompt, type
Microsoft Telnet>open internal.server.ip 21

You should see it connect or just fail at "Connecting To internal.server.ip ...Could not open connection to the host, on port 21: Connect failed"

FTP Command line from the server
If "ftp internal.server.ip" showed nothing and you are simply prompted with ftp>
type "ls"
Should say "not connected"

Then type "open"
ftp> open
To enter yout internal.server.ip or the servername

provide the command line screenshot of these actions please.

Cheers,
Hades666

ASKER CERTIFIED SOLUTION

COV-Webmaster

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Brad Howe

I'd be intrested in more detail as to what was wrong with your network adapter configuraiton. Could you please elaborate?

COV-Webmaster

ASKER

The issue was resolved by reconfiguring the network adaptor.