...

...

I have 3 suse 9.0 boxes here. I have openssh version 3.7.1p2-1 on one of them. I can connect to that one from a windows machine just fine an from another linux box too. On the other two I have openshh 3.7.1p2.18 on them. I can not connect from a windows machine to either of them. Funny thing is from a linux machine i can connect to them with ssh. Anyone else having/had this problem an know what to do to solve it. I think openssh might have gotten updated on the other two machines an not on the one I can conect to from a windows machine.

I've noticed the exact same problem on a 9.0 machine when I try to access it from my Windows box with F-Secure SSH Client v5.3 build 25. I get an error saying that:

Server responded "No further authentication methods available." No more authentication methods available.

If I access the same machine via PuTTY, X-Win32 6.0beta or Reflection-X it works perfectly well!

I've no idea how to fix it, perhaps it's a bug in the F-Secure client?

Anders.

Try use SSH2 in clients.

Nope, that didn't work. F-Secure SSH client do try ssh2 before ssh1, but even when I disabled ssh2 it didn't work. I copied the help F-Secure provides for this problem, but that wasn't of much help to me either. I use only static addresses on my connections. Just to give you a hint, the F-Secure help is pasted below. Anders. --------------- The error message "Disconnected; Authentication Error (No further authentication methods available.)" indicates that any of the methods that have been used to authenticate you to the server have not been successful. A relatively common situation is one where the remote host computer is expecting public key authentication to be used and you have not sent your public key to the host. This error is also produced if the system's name server is not doing reverse lookups correctly. Ask your system administrator to configure the name server so that it does reverse lookups properly. If this is not possible, the system administrator has to edit the file /etc/ssh2/sshd2_config on the SSH server and change the RequireReverseMapping setting to no. This is a common problem for modem connections. Typical modem connections use dynamic IP addresses. This means that the IP address changes from one connection to another, and these dynamic IP addresses have no permanent name server entries in the Domain Name System (DNS). If this is the case, you will have to ask your service provider to edit the sshd2_config file on the SSH server.

On Wednesday 10 March 2004 01.58, Örn Hansen wrote:

onsdag 10 mars 2004 00:47 skrev Anders Norrbring:

...

Nope, that didn't work. F-Secure SSH client do try ssh2 before ssh1, but even when I disabled ssh2 it didn't work.

I copied the help F-Secure provides for this problem, but that wasn't of much help to me either. I use only static addresses on my connections. Just to give you a hint, the F-Secure help is pasted below.

Point is, that SuSE 9.0 has disabled the passing of passwords in the clear, as well as SSH version 1.

The relevant entry in sshd_config, is:

# To disable tunneled clear text passwords, change to no here! PasswordAuthentication no

No, that's irrelevant. The really relevant entry is # Set this to 'yes' to enable PAM authentication (via challenge-response) # and session processing. Depending on your PAM configuration, this may # bypass the setting of 'PasswordAuthentication' UsePAM yes Also note the word "tunneled". The passwords aren't sent 'in the clear'. With password authentication turned off, you can't log in with passwords *at all*. You'll need to create ssh keys to authenticate with

On Wednesday 10 March 2004 06.01, Örn Hansen wrote:

onsdag 10 mars 2004 03:04 skrev Anders Johansson:

...

# Set this to 'yes' to enable PAM authentication (via challenge-response) # and session processing. Depending on your PAM configuration, this may # bypass the setting of 'PasswordAuthentication' UsePAM yes

This is already set, per default ...

I know it is, that's what I said. That's why you are allowed to log in using passwords even though PasswordAuthentication is set to 'no'