Re: 0.9.38 Can't connect to interface
Posted: 2011-06-06 19:39
Interesting. With the World IPv6 day coming in just two days, why do people still not have installed IPv6?
Welcome to the official discussion forums for FileZilla
https://forum.filezilla-project.org/
https://forum.filezilla-project.org/viewtopic.php?f=6&t=20724
Are you using FTPS in this scenario, normal connection does not give this error - by me, but the TLS version does.eyebex wrote:Even with that work-around, clients cannot connect anymore. The log says:MadMaverick9 wrote:Add the following line to "FileZilla Server.xml" to fix the problem:
<Item name="Disable IPv6" type="numeric">1</Item>
> 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.
Right, I'm using FTPS, so that is a different issue. Thanks for the link!markvt wrote:Are you using FTPS in this scenario, normal connection does not give this error - by me, but the TLS version does.
i am using TLS and bekam exact error message by connecting.eyebex wrote:Even with that work-around, clients cannot connect anymore. The log says:MadMaverick9 wrote:Add the following line to "FileZilla Server.xml" to fix the problem:
<Item name="Disable IPv6" type="numeric">1</Item>
> 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.
Yes - I had this problem on Windows Server 2003 Enterprise Edition - no ipv6 installed.botg wrote:If you have the problem that you cannot connect to the administration interface, does anybody of you NOT use Windows XP?
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.botg wrote:Please try http://filezilla-project.org/codesquid/ ... mental.exe
Same for me too. I have this problem on Windows Server 2003. No IPv6 support installed.MadMaverick9 wrote:Yes - I had this problem on Windows Server 2003 Enterprise Edition - no ipv6 installed.botg wrote:If you have the problem that you cannot connect to the administration interface, does anybody of you NOT use Windows XP?