celicynd
join:2005-05-24
Union City, NJ
| [OOL] SSH connection problem
We have Optimum Business here. I'm trying to use PuTTY to connect through SSH to the offsite server hosting our website. Every time I try and connect, I just get an error about "No supported authentication methods available." I actually thought it was our server, but tested the SSH connection from a different internet connection, and the connection works fine, so I'm assuming that OOL is somehow causing the error. The SSH connection is running though port 22, but I don't think it's actually blocking it since it does connect to the server, just can't authenticate. I've also tested it with 3 other SSH clients and they all do the same thing. Anyone else have issues like this?
I really wish I could access the OOL installed router or modems directly (like an admin console like my DSL had).
I'm posting the logs in case that helps (cutting out the IP and the key):
2008-05-08 10:04:29 Connecting to xxx.xxx.xxx.xxx port 22
2008-05-08 10:04:29 Server version: SSH-1.99-2.0.13 (non-commercial)
2008-05-08 10:04:29 We believe remote version has SSH-2 HMAC bug
2008-05-08 10:04:29 We claim version: SSH-2.0-PuTTY_Release_0.60
2008-05-08 10:04:29 Using SSH protocol version 2
2008-05-08 10:04:29 Using Diffie-Hellman with standard group "group1"
2008-05-08 10:04:29 Doing Diffie-Hellman key exchange with hash SHA-1
2008-05-08 10:04:30 Host key fingerprint is:
2008-05-08 10:04:30 ssh-dss 1024 xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx
2008-05-08 10:04:30 Initialised Blowfish-128 CBC client->server encryption
2008-05-08 10:04:30 Initialised HMAC-MD5 client->server MAC algorithm
2008-05-08 10:04:30 Initialised Blowfish-128 CBC server->client encryption
2008-05-08 10:04:30 Initialised HMAC-MD5 server->client MAC algorithm
2008-05-08 10:04:32 Disconnected: No supported authentication methods available |
|
jefe
Premium
join:2001-05-19
Northport, NY | FWIW, no, I don't have that issue. I connect to my web host using PuTTY and SSH (port 22) with no problem, both here at home and at my office.
I have Boost at both locations. Don't know if Boost vs. standard OOL would make any difference. |
|
efrem
join:2002-04-03
Westport, CT | reply to celicynd
FYI, I use a non-standard port for most of my SSH, but have had no problems connecting via Optonline. |
|
RickNY
Premium
join:2000-11-02
New York | reply to celicynd
It's not an OOL error.. What authentication method do you usually use? Public-key? Is password authentication on the SSH server disabled? If it is, and you haven't installed your private key on the machine with Putty, you'll get that error. |
|
TheWiseGuy
Dog And Butterfly
Premium,MVM
join:2002-07-04
Yonkers, NY
| reply to celicynd
If they are not blocking the connection to the server it is very very unlikely that OOL has anything to do with the problem. See link below for possible solutions.
»tartarus.org/~simon/putty-snapsh···-no-auth
--
Warning, If you post nonsense and use misinformation and are here to argue based on those methods, you will be put on ignore. |
|
celicynd
join:2005-05-24
Union City, NJ
edit:
May 8th, @12:06PM
| reply to RickNY
Password authentication is enabled on the server. I don't think it's a server error. I can do a fresh install of PuTTY on a different machine online via a different internet connection and all I have to do is put in the host name, click connect, accept the key, input my username and password, and I'm connected. It's only here at work that this issue is showing up, and seems only to have started occuring once we switched over to OOL. |
|
RickNY
Premium
join:2000-11-02
New York
 ·Optimum Online
| reply to celicynd
Can you export the session from the registry on one of the working machines and import it into the machine you are having a problem with? If you go into regedit and pull up HKEY_CURRENT_USER\Software\SimonTatham\PuTTY\Sessions -- you should be able to just export the one session that you use and then import the reg file.
Any time I have ever seen that message, it was due to a configuration issue on the client or the server. You're making the connection -- its the authentication that is failing. |
|
celicynd
join:2005-05-24
Union City, NJ | I'll have to try that when I get home and have access to the working computer... forgot to leave my remote desktop on today.
I'll post an update later. Hopefully that will work. |
|
celicynd
join:2005-05-24
Union City, NJ | reply to RickNY
I tried exporting the session registry keys and loading them on one of the computers at work. Still no go, I get the same error. |
|
