HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- SSH keygen from windows
Operating System - HP-UX
1832986
Members
2525
Online
110048
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-12-2007 09:34 PM
12-12-2007 09:34 PM
SSH keygen from windows
Dear Experts
I'm getting the following messages in my HP-UX box(11iv1,v2 etc.) in syslog.log
Dec 13 11:23:25 sshd[16808]: Did not receive identification string from
Dec 13 11:23:35 sshd[16809]: Accepted password for from port 4575 ssh2
That is happen when i connect from windows workstation.
I think this is related to ssh-key.
Can anyone tell me how can i resolve this kind of messages?
NB. - Though the message i can connect and work as usual.
I'm getting the following messages in my HP-UX box(11iv1,v2 etc.) in syslog.log
Dec 13 11:23:25
Dec 13 11:23:35
That is happen when i connect from windows workstation.
I think this is related to ssh-key.
Can anyone tell me how can i resolve this kind of messages?
NB. - Though the message i can connect and work as usual.
a warrior never quits
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-12-2007 10:54 PM
12-12-2007 10:54 PM
Re: SSH keygen from windows
Can you please try change the ssh port and then check.
BR,
Kapil
BR,
Kapil
I am in this small bowl, I wane see the real world......
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-13-2007 12:26 AM
12-13-2007 12:26 AM
Re: SSH keygen from windows
Not related to the ssh-key.
Both the ssh client and server are expected to send an identification string in the beginning of a SSH connection, to allow the identification of protocol version and/or workarounds for known bugs in some client or server versions.
You can see the server's identification string by telnetting to the server's port 22 (the ssh port):
$ telnet localhost 22
Trying...
Connected to localhost.
Escape character is '^]'.
SSH-2.0-OpenSSH_4.4p1-hpn12v11
Protocol mismatch.
Connection closed by foreign host.
In this example, the server's identification string is "SSH-2.0-OpenSSH_4.4p1-hpn12v11". After receiving the server's identification string, the client should respond with a similar string of its own.
Your sshd is saying that your windows-based ssh client did not offer this information.
As you can still connect, your client obviously does not need any special workarounds at the server-side. So the message is information only.
MK
Both the ssh client and server are expected to send an identification string in the beginning of a SSH connection, to allow the identification of protocol version and/or workarounds for known bugs in some client or server versions.
You can see the server's identification string by telnetting to the server's port 22 (the ssh port):
$ telnet localhost 22
Trying...
Connected to localhost.
Escape character is '^]'.
SSH-2.0-OpenSSH_4.4p1-hpn12v11
Protocol mismatch.
Connection closed by foreign host.
In this example, the server's identification string is "SSH-2.0-OpenSSH_4.4p1-hpn12v11". After receiving the server's identification string, the client should respond with a similar string of its own.
Your sshd is saying that your windows-based ssh client did not offer this information.
As you can still connect, your client obviously does not need any special workarounds at the server-side. So the message is information only.
MK
MK
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP