I was finally know this because of you.I also was finally able to make use of IPv6 support on my systems around the time 4.1.9 was released and was really pleased to see WinSCP supported it. However as of 4.2.5, 4.2.6, and even the latest 4.2.7 release, it does not work at all.Thank you.

I found where I could download older 4.2.x series and the 4.2.4 beta does work...so does the 4.2.3 and the 4.2.2 betas. It stops cold on 4.2.5 which ironically is the first release in the 4.2.x series NOT considered beta...go figure.!!!!!!!!!!!!!!!!!!

This bug has been added to tracker.

Hi Martin,

That last link you sent me worked and appeared to fix the issue, I could successfully connect again to an IPv6 host. Thanks so much!

SlyM

:D

I've emailed you the trace file, thanks!

SlyM

Hi Martin,

I've sent the email...thanks for looking into this, I really appreciate it.

SlyM

Can you send me an email, so I can send you back a debug version of WinSCP to track the problem? Please include link back to this topic in your email. Also note in this topic that you have sent the email. Thanks.

I found where I could download older 4.2.x series and the 4.2.4 beta does work...so does the 4.2.3 and the 4.2.2 betas. It stops cold on 4.2.5 which ironically is the first release in the 4.2.x series NOT considered beta...go figure.

Hope this helps.

I was finally able to make use of IPv6 support on my systems around the time 4.1.9 was released and was really pleased to see WinSCP supported it. However as of 4.2.5, 4.2.6, and even the latest 4.2.7 release, it does not work at all. I simply get an error message upon attempting to connect to an IPv6 host via sftp or scp. The error message says: "gethostbyname: unknown error" and gives me the option to click ok, Reconnect (with an automatic 5 second count down timer), or help. If I install 4.1.9 it works again, so it appears to have something to do with the 4.2.x series only. The oldest 4.2.x series I could find to try was 4.2.5 and it doesn't work there, and the latest 4.2.7 doesn't work either. I was hoping this would get caught and fixed by now, but I guess IPv6 isn't yet that popular, so it probably doesn't get used/tested by many people at all. I would really appreciate a simple look into this, as it did previously work in the older 4.1.x series.