why does VM GPL try to ftp using port 5674?

5 posts / 0 new
Last post
#1 Mon, 02/28/2011 - 12:27

why does VM GPL try to ftp using port 5674?

I'm setting up a VM GPL install to back up domains to a remote VM Pro ftp target. For some unknown reason I'm getting a message "no route to host xx.xx.xx.xx:5674" why port 5674??? manually ftping in without specifying a port works ok.


Tue, 03/01/2011 - 04:42

When and where exactly are you getting this message?

Tue, 03/01/2011 - 20:41 (Reply to #2)

I'm trying to set up a scheduled backup and testing immediately after setting it up by clicking on "backup now." In the time since I first posted I've tried several more times, the port number is apparently random, always high and the ftp fails, "no route to host."

Tue, 03/01/2011 - 20:47

This is how the FTP protocol works (unfortunately). It uses many ports ... Your ftp client probably uses a different mode (active vs passive)?

Sun, 03/13/2011 - 15:01

Yes, as helpmin says, FTP uses a control connection on port 21 (default) and randomly chosen data connection ports. Depending on network layout (router/firewalls) of client and server, that causes problems. Before I write a whole novel here :) about FTP and firewalls, you might check Google for information on active vs. passive mode, and configuring client/server to use only a specific port range which needs to then be allowed through the firewall.

When you have a basic understanding of the issue, check back and we can give some concrete hints on how to configure the related software.

Topic locked