Cant administer filezilla - Windows 10 Pro rtm 10240

[nn2015]

Hi!

I have a problem with the latest version of Filezilla Server 0.9.53 and Windows 10 Pro rtm 10240.

I can't administer Filezilla server in Windows 10.

Setting up groups and users works fine, and there is no problem using the server with default settings.

But admin does not work in windows 10, can't change settings because Filezilla thinks that I am behind a NAT router. Works in windows 8.1.

I am connecting from the same computer so I am not behind a NAT router.

Any suggestions?

Thanks!


Connecting to server 127.0.0.1:14147...
Connected, waiting for authentication
Logged on
You appear to be behind a NAT router. Please configure the passive mode settings and forward a range of ports in your router.
Warning: FTP over TLS is not enabled, users cannot securely log in.
Connection to server closed.

[nn2015]

SOLVED.

I have manually edited FileZilla Server.xml.

Edited settings for the admin interface to allow connections from any ip.

Now I can use the admin interface.

[boco]

The warnings are actually unrelated to the connection abort. The first warning shows if the OS reports only a LAN IP (indicating a NATed environment). The second one comes up if TLS is disabled.

The dev will most surely wait until GA of Windows 10 (2015-07-29).

[botg]

I'm not observing any problems running and administrating FileZilla Server on a recent Windows 10 preview build.

[nn2015]

I'm not observing any problems running and administrating FileZilla Server on a recent Windows 10 preview build.

I connected with remote desktop to my server and did the installation from that.

Could that have anything to do with:

"You appear to be behind a NAT router. Please configure the passive mode settings and forward a range of ports in your router"

[nn2015]

The warnings are actually unrelated to the connection abort. The first warning shows if the OS reports only a LAN IP (indicating a NATed environment). The second one comes up if TLS is disabled.

The dev will most surely wait until GA of Windows 10 (2015-07-29).

Yes I know that they are unrelated to connection abort. I disconnected manually. TLS is disabled in default settings so I understood that too.

"You appear to be behind a NAT router. Please configure the passive mode settings and forward a range of ports in your router"

The problem is that if Filezilla Server thinks that you are behind a NAT you can't save your admin setting because only localhost is able to do that in default settings.

I connected from localhost.

But thanks for your input .

Everythings is solved know by edited server settings manually..

Works perfect with TLS enabled now.

[boco]

Yes, there could be a problem here. TS (Terminal Services) redirect a good portion of the OS to the connecting OS, that's why it only works on Windows . The problem is if the TS also redirect the network stack, then localhost, 127.0.0.0/8 and [::1] might redirect to the connecting machine instead of the target one. That edge case would indeed make saving admin settings impossible, as the FZ Server service would see a translated LAN/WAN IP instead of localhost. XML editing works but is hardly comfortable. Other methods like VNC do not have that problem.

Might as well install the server locally and produce an XML that you can then upload to the target machine. Finally, issue "FileZilla Server.exe /reload-config" to load the new XML.

[botg]

The problem is that if Filezilla Server thinks that you are behind a NAT you can't save your admin setting

That's not the case.

because only localhost is able to do that in default settings.

Only localhost can ever change admin interface settings, this is nonconfigurable.