Can't connect to Server Interface from external IP

[zlyzwy]

Hi all,

I am trying to set up a FTP server. I installed the FileZilla server and it seems to be OK with FTP client.
But after that, I can only connect the Server Interface to "localhost" or "127.0.0.1".
I want to connect the server remotely so I tried to bind the IP to server and it doesn't work.
What I did are as followed:
1. In settings,bind the IP to my server's IP, eg : 192.168.1.110
2. In IP filter, set allow IP to "*"
3. disable the windows firewall


By all the settings above, I am not able to connect to the server with IP(192.168.1.110).

The error log:

Code: Select all

Connection to server closed.
Connecting to server...
Error, could not connect to server
Trying to reconnect in 5 seconds

System:
OS:Windows 2003 RC2
Filezilla:beta 0.9.40

Thanks for any reply in advance.

[botg]

Did you set a password? If no password is set, only localhost is allowed to connect.

[zlyzwy]

Did you set a password? If no password is set, only localhost is allowed to connect.

Thanks for your quick reply.

I didn't set the password for admin user. but even I set the password now, it still doesn't work.

The error is same.


Anything else I should do?

[boco]

OS:Windows 2003 RC2

Seriously? I hope you mean SP2.

[zlyzwy]

OS:Windows 2003 RC2

Seriously? I hope you mean SP2.

Sorry, my mistake. It should be Windows 2003 R2 Enterprise Edition with SP2.

[boco]

Did you try with a different admin port? There may be an issue with the default 14147. And, by ''remotely'' you mean LAN only, right?

PS. Did you change the admin binding to * also? By default the server only listens for admin interface on 127.0.0.1:14147 and [::1]:14147.

[zlyzwy]

First, thank for your help.

Did you try with a different admin port? There may be an issue with the default 14147.

Yes, I did try the 14148. But the result is no difference.

And, by ''remotely'' you mean LAN only, right?

yes, it's LAN. Actually I am trying to connect the Server Interface on the same server. I set up the FileZilla on the server which has the IP(192.168.1.110). If I connect to localhost/127.0.0.1, it's no problem. But with IP(192.168.1.110), it doesn't work.

Furthermore, I tried to connect from Internet. It gives me the same error.
I did the NAT for 14148 port to WAN address. And I am sure the NAT is working because other server is working properly.

[boco]

I edited my post, please note the PS.

@botg: As a side note a small possible bug: Changing (at least deleting) binding options seems to mess up the binding to ::1 until you restart the server.

[zlyzwy]

PS. Did you change the admin binding to * also? By default the server only listens for admin interface on 127.0.0.1:14147 and [::1]:14147.

I tired "*" , "192.168.1.*" , "*.*.*.*". but no luck...

[boco]

I just tested: Set both the ''binding'' and ''allow'' field to *, set a password (min 6 chars) and I was able to connect to my server using my LAN IP (10.0.0.3). Hmm...

A quick note: The admin settings on that page can only be changed when connected via localhost. Remember that once you get it working.

[zlyzwy]

I just tested: Set both the ''binding'' and ''allow'' field to *, set a password (min 6 chars) and I was able to connect to my server using my LAN IP (10.0.0.3). Hmm...

A quick note: The admin settings on that page can only be changed when connected via localhost. Remember that once you get it working.

e.... It's strange...

I am sure the settings get work here. I can see the changes if I login again.

Code: Select all

Done retrieving settings
Sending settings, please wait...
Done sending settings.
Admin listen port changed to 14148.

Are you using the same version as mine?
I am now using 0.9.40 beta.
Will you need to restart the system after the changes?
==================================================================

I uninstall the FileZilla server(delete settings) and re-install.
No difference..

===================================================================

There is one thing I don't it does matter? I've got three LAN cards on this server, however only one has the IP(192.168.1.110). The other two cards I disable all the protocols like Internet Protocol, Microsoft Network Client etc... So these two cards has no IP in windows 2003.
I can't disable them because I need them to work for a virtual machine inside windows 2003.
My idea is since these two cards has no IP so they will not effect the FileZilla...

Thanks.

[boco]

e.... It's strange...

I am sure the settings get work here. I can see the changes if I login again.

I think I'll have to clarify: If the Admin interface is connected to the server via localhost (localhost, 127.0.0.1 or ::1 is displayed in the title bar), you can change all settings. But once you'll connect to the LAN IP, changes to the admin page will be ignored. That's a security setting, to keep yourself/an attacker from locking you out when connected from abroad.

Are you using the same version as mine?

I'm using 0.9.41prebeta, but no changes between 0.9.40 and my version in that area.

Will you need to restart the system after the changes?

Nope, not required.

There is one thing I don't it does matter? I've got three LAN cards on this server, however only one has the IP(192.168.1.110). The other two cards I disable all the protocols like Internet Protocol, Microsoft Network Client etc... So these two cards has no IP in windows 2003.
I can't disable them because I need them to work for a virtual machine inside windows 2003.
My idea is since these two cards has no IP so they will not effect the FileZilla...

NICs without an IP won't provide any socket for FZ Server to be bound to, so they shouldn't matter. And since you have Server 2003, we do not need to speak about IPv6 at all, I guess (FZ Server is IPv6 ready if available).
Note that you can always use the dedicated IP for admin-binding instead of the asterisk. This would circumvent possible socket issues if they existed.

[botg]

@botg: As a side note a small possible bug: Changing (at least deleting) binding options seems to mess up the binding to ::1 until you restart the server.

Gonna have a look.

[zlyzwy]

Quote:
e.... It's strange...

I am sure the settings get work here. I can see the changes if I login again.
I think I'll have to clarify: If the Admin interface is connected to the server via localhost (localhost, 127.0.0.1 or ::1 is displayed in the title bar), you can change all settings. But once you'll connect to the LAN IP, changes to the admin page will be ignored. That's a security setting, to keep yourself/an attacker from locking you out when connected from abroad.

Thanks for your expliantion. I think it's now clear...
Only if I connect to Admin interface via localhost, all the changes I made will get work. Otherwise it's "read-only" mode?

If so, I will have to login in the server and do all the modification. but yes, it's more safety for server.

Quote:
There is one thing I don't it does matter? I've got three LAN cards on this server, however only one has the IP(192.168.1.110). The other two cards I disable all the protocols like Internet Protocol, Microsoft Network Client etc... So these two cards has no IP in windows 2003.
I can't disable them because I need them to work for a virtual machine inside windows 2003.
My idea is since these two cards has no IP so they will not effect the FileZilla...
NICs without an IP won't provide any socket for FZ Server to be bound to, so they shouldn't matter. And since you have Server 2003, we do not need to speak about IPv6 at all, I guess (FZ Server is IPv6 ready if available).

I am not using IPv6 yet. I think this is not the problem.

Note that you can always use the dedicated IP for admin-binding instead of the asterisk. This would circumvent possible socket issues if they existed.

Thanks, I got it...

[zlyzwy]

I had set up the FTP server and it's now running fine..)

Even I still can't read the setting in LAN, it's no longer to be problem anymore. I am now doing the setting through VNC.

I have feeling the trouble is from my side not about the FZ. If you would like to do more testing, you can just post it here and I will continue or we can close this ticket.

Many thanks for your patient and help!