It sounds like they didn't put your public key into authorized_keys.
(It's a file on the server, in your $HOME/.ssh/ directory)

Make sure that under Connection->SSH it says '2' as preferred version
instead of '2 only' just in case they put it in the wrong file.

check to make sure you're putting the right username in under
Connection->Data->Auto-login username.

You can get some debug info under Session->logging by asking for 'Log
all session output'

Good luck.

Kelly Thomas wrote:
> Have tried it both ways. Still get the same message... leading me to
> believe that it's not me but, since I'm new at this, I don't know for
> sure.
> 
> -----Original Message-----
> From: Justin Alcorn [mailto:[EMAIL PROTECTED] 
> Sent: Wednesday, July 04, 2007 12:20 PM
> To: Kelly Thomas
> Cc: [email protected]
> Subject: Re: Connecting to host
> 
> In the putty config for that connection, under Connection->SSH->Auth,
> put the private key file in there.
> 
> Or, even better, run pagent on your private key, and then it will run in
> memory and never ask your password again.
> 
> Kelly Thomas sent the following missive on 7/3/2007 12:45 PM:
>> We have recently been asked by one of our vendors to connect to their
>> system through SSH. They are a Unix Host - beyond that, I don't have
>> much information. 
>>
>> We are a 'windows' shop and I'm using Putty version 0.60 to connect
> with
>> a Windows XP Professional machine. I have created a public key and
> sent
>> it to them. They have also sent their public key to me. From what
>> they're telling me, there should be no password to connect. 
>>
>> When I try to connect it first asks for my passphrase. I'm assuming it
>> will only do that the first time to validate my key - not sure. 
>>
>> After typing in my passphrase for the key, I get a disconnect message:
>> Server sent disconnect message type 7 (service not available):
>> "Unsupported request (pty-req)." 
>>
>> This message appears to be something on their end but they are telling
>> me it's on my end. Can anyone help?
>>
> 

Reply via email to