FileZilla Forums

Interesting. With the World IPv6 day coming in just two days, why do people still not have installed IPv6?

eyebex wrote:

MadMaverick9 wrote:Add the following line to "FileZilla Server.xml" to fix the problem:

<Item name="Disable IPv6" type="numeric">1</Item>

Even with that work-around, clients cannot connect anymore. The log says:

> Could not get peer name
> 421 Refusing connection. Could not get peer name.
> disconnected.

It seems the IP lookup in the PASV mode settings is broken. I'm running on Windows XP without IPv6 support.

Are you using FTPS in this scenario, normal connection does not give this error - by me, but the TLS version does.

Btw in this case ipv6 support is on.

if ftps see this thead: http://forum.filezilla-project.org/view ... =6&t=20729

If you have the problem that you cannot connect to the administration interface, does anybody of you NOT use Windows XP?

markvt wrote:Are you using FTPS in this scenario, normal connection does not give this error - by me, but the TLS version does.

Right, I'm using FTPS, so that is a different issue. Thanks for the link!

Please mind the topic title. This topic is about not being able to connect to the administration interface. Mixing topics only makes things harder for all of us.

eyebex wrote:

MadMaverick9 wrote:Add the following line to "FileZilla Server.xml" to fix the problem:

<Item name="Disable IPv6" type="numeric">1</Item>

Even with that work-around, clients cannot connect anymore. The log says:

> Could not get peer name
> 421 Refusing connection. Could not get peer name.
> disconnected.

It seems the IP lookup in the PASV mode settings is broken. I'm running on Windows XP without IPv6 support.

i am using TLS and bekam exact error message by connecting.
btw, i have windows 7 ultimate x64 and IPV6 is installed !

botg wrote:If you have the problem that you cannot connect to the administration interface, does anybody of you NOT use Windows XP?

Yes - I had this problem on Windows Server 2003 Enterprise Edition - no ipv6 installed.

Windows Server 2003 is (almost) the same kernel like XP. Full, proper IPv6 support was added to Vista and later only. There currently is an issue if you have no IPv6 support installed. Until a fix is available, you can use 0.9.37. There aren't much changes besides IPv6 support anyway.

http://sourceforge.net/projects/filezil ... er/0.9.37/

I have the problem as well on a Windows 2003 machine but as you say that has a kernel most similar to XP. In any event it certainly has no IPv6 support.

Any custom options in the admin interfaces admin interface settings page that were not default?

Please try http://filezilla-project.org/codesquid/ ... mental.exe

botg wrote:Please try http://filezilla-project.org/codesquid/ ... mental.exe

I tried to stop the original service to exchange the executables. However, stopping the service did not work properly, it hangs at the "stop pending" state. So I terminated the process, exchanged the executables, and tried to start the service again. This also does not work for me, I get "The service did not respond to start or control requests in a timely fashion". Using the original executable again I'm also able to start the service again.

MadMaverick9 wrote:

botg wrote:If you have the problem that you cannot connect to the administration interface, does anybody of you NOT use Windows XP?

Yes - I had this problem on Windows Server 2003 Enterprise Edition - no ipv6 installed.

Same for me too. I have this problem on Windows Server 2003. No IPv6 support installed.

Figured out what is causing this.

When creating a binding fails, the service tries to display a message box.

Services don't usually display message boxes, but some do. What then happens depends on the used operating system: On old systems (9x and in some configurations XP) the box appears. On new systems (e.g. Vista and up), nothing happens. Only on Windows 2003, the program freezes.

This also explains why it never appeared on my machine, I usually run the server in the debugger as normal program as opposed to service.

For now I'll just comment out the message box.

Note that the server service would have frozen also in 0.9.37 if creating one if its admin interface bindings would have failed, so it actually is an old problem which just now is being triggered.

The fixed 0.9.39 will be released before the World IPv6 day starts.