Solving ssh problems
If you have an error with ssh client or server itself you should try with followings:
Firstly, you should set extra verbose messages on ssh client outputs with -vvv flag:
ssh -vvv user@host
There are quite usefullinformations in verbose output mode.
Secondly, you should take a look at ssh server logs or syslog records.
If you have a bit strange problem, you have to start another instance of ssh server with debugging enabled on unused port like that:
/usr/sbin/sshd -d -p 5656
and try to connect this instance with:
ssh -vvv -p 5656 user@host
Now you can see both of the client and server side messages. Ssh prints lots of useful information in debugging mode. If you want even more debuggin messages at server side, add another d flags and increase verbosity like that:
/usr/sbin/sshd -ddd -p 5656
- 0 Comment
- Murat Demirten
- 04 Jul 2008, 15:12
-
You must be login first or sign-up for an account to post comments.
Maybe you should look at these also:
USERBOX
CATEGORIES
MOST READED TODAY
- Creating splitted rar archive files
- Converting MAC dfonts to TrueType
- Solving ssh problems
- XFS Filesystem has duplicate UUID problem
- Network interface status with mii-tool
- Recovering Root Password
- Recovering mysql root password
- Changing time in Linux
- Listing files by size
- Search and replace on multiple files
LAST ADDED
- Routing packets back from incoming interface
- Users with /bin/false shell to login on vsftpd
- Redirecting TCP ports with redir
- Assembly code of a C code
- Network interface status with mii-tool
- dropbear rsa key problem
- Displaying disk io statistics
- Disabling ssh password authentication
- Creating splitted rar archive files
- Creating self-extracting zip archives for both Linux and Windows
