|
     |
This sections introduces workaround instructions for some problem situations.
When connecting from a Windows 5.x or 6.x client to a Windows 4.x server using
GSSAPI authentication, if authentication fails although GSSAPI has been correctly
configured, you may have to disable the LMHOSTS lookup on the client-side
computer. Follow these instructions:
Select Control Panel → Network Connections.
In Local Area Connection, right-click and select Properties.
In the Local Area Connection Properties dialog box, General tab, select Internet Protocol (TCP/IP) and click the Properties button.
In the Internet Protocol (TCP/IP) Properties dialog box, in the General tab, click the Advanced button.
In the Advanced TCP/IP Settings dialog box, in the WINS tab, clear the Enable LMHOSTS lookup check box.
Restart the client-side computer.
If there are multiple public-keys available either via external key providers or in the user-specific configuration directory, the server-side might refuse the connection if too many keys are attempted during publickey authentication. Typically the error shown when attempting to connect to an OpenSSH server that allows six attempts is "Connection open failed Protocol error (remote): too many authentication failures public_keys_tried: 7". If the server configuration cannot be changed to allow more attempts, the workaround on the client-side is to set the Connection profile to prompt the user for the specific key to use or with the sshg3, sftpg3 or scpg3 command-line clients use the -K option to specify the explicit key.
sshg3 -K <path_to_key> <profilename>
| |