[
https://issues.apache.org/jira/browse/SSHD-786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16279761#comment-16279761
]
Goldstein Lyor commented on SSHD-786:
-------------------------------------
In the reference issue you specified it states
{quote}
I double checked the server set-up (Windows Server 2008 R2 (6.1)).
The only existing Ethernet interface is bound to IPv4 only, no IPv6 is
configured whatsoever.
{quote}
Makes me wonder though how can it be that the reported failing address is an
IPv6 one - can you double-check that you specify "0.0.0.0" as the listen
address for your SSH server (the one listening on port 29418) ? I do know that
SSHD code has a few issues with IPv6 - maybe this is one of them...
{code:java}
SshServer server = SshServer.setupDefaultServer();
server.setHost("0.0.0.0");
{code}
> Clients can't authenticate after unexpected exception in Nio2Acceptor
> ---------------------------------------------------------------------
>
> Key: SSHD-786
> URL: https://issues.apache.org/jira/browse/SSHD-786
> Project: MINA SSHD
> Issue Type: Bug
> Affects Versions: 1.2.0, 1.3.0, 1.4.0, 1.6.0
> Environment: Windows
> Reporter: masc
>
> {code}
> 2017-11-28 15:26:54,808 11566202 sshd-SshServer[434a2a10]-nio2-thread-4
> org.apache.sshd.common.io.nio2.Nio2Acceptor WARN - Caught IOException while
> accepting incoming connection from /0:0:0:0:0:0:0:0:13003: The specified
> network name is no longer available.
> java.io.IOException: The specified network name is no longer available.
> at sun.nio.ch.Iocp.translateErrorToIOException(Iocp.java:309)
> at sun.nio.ch.Iocp.access$700(Iocp.java:46)
> at sun.nio.ch.Iocp$EventHandlerTask.run(Iocp.java:399)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> As soon as this exception occurs once, clients can still connect but will
> fail to authenticate.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
