Admin interface cannot connect after upgrade

Message

theTerran · #1 Post by **theTerran** » 2006-07-26 17:15

Hello all,

Upgraded FileZilla Server today from 0.9.10 to 0.9.18 (latest as of this date). Clients are able to connect just fine, but I cannot connect from the console with the Admin interface. Using default port 14147. Have stopped/started the FileZilla Server service with no improvement.

Server address: 127.0.0.1
Port: 14147

Here's the error message shown in the admin interface:

Code: Select all

FileZilla Server version 0.9.18 beta
Copyright 2001-2006 by Tim Kosse (tim.kosse@filezilla-project.org)
Connecting to server...
Error, could not connect to server
Trying to reconnect in 5 seconds
Reconnecting to server...
Trying to reconnect in 5 seconds
Error: Connection to server lost...
Reconnecting to server...
Error, could not connect to server
...etc.

netstat -a shows the server listening on this port:

Code: Select all

  TCP    servername:14147         servername.domain.net:0  LISTENING

Any suggestions?

Thanks,

Daniel

#2 Post by **botg** » 2006-07-26 22:22

Possibly a firewall that's blocking connection attempts.

theTerran · #3 Post by **theTerran** » 2006-07-26 22:58

This is on the local machine, and there is no firewall software running. The host is Windows 2000 Server with latest patches, no firewall; AV (Trend Micro OfficeScan) is set to ignore FileZilla (no realtime scan). Firewall to the world is another box and connections from outside are working fine.

Ah! Tried to ftp localhost (also as 127.0.0.1) and got this error (both ways):

Code: Select all

>ftp 127.0.0.1
Connected to 127.0.0.1.
550 No connections allowed from your IP
Connection closed by remote host.

Could this be blocking admin access also? I know the port is different, but does it look for a permitted IP to connect the Admin interface?

Thanks,

Daniel

#4 Post by **boco** » 2006-07-27 20:43

Open a command window (Start - Run... - Enter 'cmd')

now type netstat -a -b

Search for Filezilla server.exe and look what ports it is listening on.

boco

Nusz · #5 Post by **Nusz** » 2006-08-07 19:04

I think the problem I'm having is along the same lines... When I try to connect with the admin app to Local Host (127.0.0.1:14147) it works fine but if I try to access the admin using this boxes external IP on port 14147 it doesn't work.

NetStat shows FZ Server listening on the FTP port but the only way I can access the admin is to log in to that box and use the Local Host address instead of it's external address.

On the box in question I am connected directly to the internet with the Windows firewall from XP SP2 running. Port 14147 has been allowed and FileZillaServer.exe is also allowed. I'd really like to be able to access the admin portions of the server from my computer instead of having to remote desktop in so that I can actually log in to the ftp server app.

Any help would be greatly appreciated.

#6 Post by **boco** » 2006-08-08 12:45

Nusz wrote:I think the problem I'm having is along the same lines... When I try to connect with the admin app to Local Host (127.0.0.1:14147) it works fine but if I try to access the admin using this boxes external IP on port 14147 it doesn't work.

NetStat shows FZ Server listening on the FTP port but the only way I can access the admin is to log in to that box and use the Local Host address instead of it's external address.

On the box in question I am connected directly to the internet with the Windows firewall from XP SP2 running. Port 14147 has been allowed and FileZillaServer.exe is also allowed. I'd really like to be able to access the admin portions of the server from my computer instead of having to remote desktop in so that I can actually log in to the ftp server app.

Any help would be greatly appreciated.

1. Open Filezilla server options
2. Open Admin interface settings
3. Now type an asterisk (*) into Bind the admin interface to the following IP addresses
4. AFAIK if you want to REMOTELY access the server, you MUST have an admin password; you should specify one if you have no one yet.

boco

Nusz · #7 Post by **Nusz** » 2006-08-09 16:28

Thanks Boco, that worked like a champ. When I first made the change I was getting Auth Failed... but I went to lunch and came back and it's all working like it should.

Woo Hoo, no more having to RDP into the server to administer it.