FTP connect to remote VPS Server

G'day Folks,

Seems I am having no end of trouble trying to connect to my VPS Server in the UK, using the Directory Opus FTP option and Anonymous setting to port 21.

  • This either fails or times out.

I have no problem connection to other FTP sites as long as I use a User name and password.

Any tips on the FTP connect to a VPS Server please.

pcbugfixer - The Devil made me do it. :imp:

Can you connect to it with other FTP clients? Is this specific to Opus, or specific to the VPS server?

Have you looked at the FAQ on FTP connection issues?

G'day Leo,
Thanks for reply.
No I cannot FTP in from any FTP client.
I can RDP in on my KVM/VPS running Windows 2008 R2 Server.
I have allowed port 21 in the firewall, however when I do a "netstat -a -n" from the cmd, port 21 is not open, nor 22 and other common ports.

So what do I use to FTP into the windows 2008 R2 Server on the KVM/VPS ?

  • any ideas ? this would help y synchronization of my Tools folder.


If you can't FTP to the server from any client then there must be an issue with the server, network or firewall configurations. You'll need to talk to whoever set up the server and/or network for help.

G'day Leo,

I was hoping for a more definitive answer from Directory Opus, however so be it.

In the mean time, for those needing to configure a RDP on Win XP Pro SP3 (Must be XP Pro SP3) as XP does not have the ability unless you install the drivers for EDP.

Do the following,
Follow the instructions in step 1,
Step 1. - placeone.net/helpbox/2011/07/win ... on-client/
and re-boot when completed
After re-boot follow the instructions in step 2.
Step 2 - support.microsoft.com/kb/284931
and re-boot when completed
Step 3 - you will find a shortcut to the "Remote Desktop Connection" in the Programs -> Accessories menu, all you now need is the IP address or web site, User Name and password when asked.

As to allowing FTP on the Win 2008 R2 Server, you can try the following,

technet.microsoft.com/en-us/libr ... spx#bkmk_1

  • Yields the following information.
    How to Configure Windows Firewall for a Passive Mode FTP Server
    24 out of 46 rated this helpful - Rate this topic

Updated: January 20, 2009

Applies To: Windows 7, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, Windows Vista

Using the File Transfer Protocol (FTP) service on a server behind a firewall creates a set of challenges because of the way FTP works. A standard mode FTP client initiates a session to a server by opening a “command channel” connection to TCP port number 21. A file transfer is requested by the client by sending a PORT command to the server. The server then attempts to initiate a “data channel” connection back to the client on TCP port number 20. A typical firewall running on the client sees this data channel connection request from the server as unsolicited and drops the packets, causing the file transfer to fail. Windows Firewall with Advanced Security in Windows Vista and Windows Server 2008 support stateful FTP, which allows it match inbound connection requests on port 20 with previous outbound PORT commands from the client. However, if you use FTP over SSL to encrypt and secure the FTP traffic, then the firewall can no longer inspect the inbound connection requests from the server, and they are blocked.

To avoid this issue, FTP also supports a “passive” operational mode in which the client initiates the data channel connection. Instead of using the PORT command, the client sends a PASV command on the command channel. The server responds with the TCP port number to which the client should connect to establish the data channel. By default, the server uses an available port in the ephemeral range (1025 through 5000). To better secure the server, you can restrict the port range used by the FTP service, and then create a firewall rule that allows FTP traffic on only those allowed port numbers.

This topic discusses how to:

Configure the FTP service to only use a limited number of ports for passive mode FTP

Configure an inbound firewall rule to allow inbound FTP connections on only the allowed ports

The following procedure shows the steps for configuring the FTP service on Internet Information Services (IIS) version 7.0. If you are using a different FTP service, then consult that product’s documentation for appropriate steps. Configuring support for SSL is beyond the scope of this topic. For more information, see the IIS documentation.
Configure the FTP service to only use a limited number of ports for passive mode FTP

In the IIS 7.0 Manager, in the Connections pane, click the top node for your server.

In the details pane, double-click FTP Firewall Support.

Enter the range of port numbers that you want the FTP service to use. For example, 41000-41099 allows the server to support 100 passive mode data connections simultaneously.

Enter the external IPv4 address of the firewall through which the data connections arrive.

In the Actions pane, click Apply to save your settings.

You must also create a firewall rule on the FTP server to allow inbound connections on the ports you configured in the previous procedure. Although you could create a rule that specifies the ports by number, it is easier to create a rule that opens any port on which the FTP service is listening. You limit the ports on which FTP is listening by following the steps in the previous procedure.
Configure an inbound firewall rule to allow inbound FTP connections to only the ports on which FTP is listening

Open an Administrator command-prompt. Click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run as Administrator.

Run the following command:

netsh advfirewall firewall add rule name=”FTP Service” action=allow service=ftpsvc protocol=TCP dir=in

Finally, disable stateful FTP filtering so that the firewall does not block any FTP traffic.

netsh advfirewall set global StatefulFTP disable

OK that's it Folks.
pcbugfixer "The :smiling_imp: made me do it"