when telnet to port 10000 ,it gives a "protocal mismatch"
When try to run " telnet XX.XX.XX.XX 10000" commnad the server gives out folowing error ( XX - ip address)
"SSH-2.0-OpenSSH_5.3p1 Debian-3ubuntu7" "Protocol mismatch." the correct output what i expected is somthing like this "Ç$☺PµYC☻♥ _ " please let me know how to solve this Thanks |
You're trying to telnet to a service other than telnet. Specifically, the service listening on port 10000 is an SSH deamon, which expects connecting clients to communicate using the SSH protocol.
An SSH daemon always announces the SSH version and product name when a client connects. Why you would expect to see garbage characters instead is not immediately obvious. |
Program telnet talks telnet protocol. Try netcat (nc).
Edit: but I don't think you could emulate ssh protocol... Perhaps you should use ssh client program? |
As noted, the daemon you are telneting to is a secure shell service.
The version identification is part of the protocol. The following garbage characters are the public key that the client should use for encrypting the next part of the communication. The "protocol mismatch" is due to the failure of the handshaking (telnet protocol vs ssh protocol). If I remember right, you are supposed to present your public key.... but the telnet protocol from the client doesn't do that. |
Thank you very much for your reply :)
What I really want to do is configure Symantec Backup exec client on the remote server , and it use port 10000 to communicate with the Backup exec server.with this specific server it failed to communicate because of this "protocol mismatch" issue. Please let me know what i should do to rectify this . Thanks again for all your support ... |
As far as I know, that has nothing to do with Linux, nor ssh... It is a windows product only.
A client does exist for Linux... but it does its own thing. |
Hello,
Ive had much success with the following suggestions offered here http://www.symantec.com/business/sup...t&id=TECH48522 |
You just gave everyone on the (local) net the root password...
and confirmed that it is not using ssl/TLI for protection. Which is opposite what you listed at the beginning. |
Quote:
|
All times are GMT -5. The time now is 01:10 PM. |