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.
USERBOX
CATEGORIES
MOST READ TODAY
- Redirecting tcp / udp ports with socat
- Syntax highlighting in less
- Disabling reverse dns lookups in ssh
- Passwordless sudo setup
- Users with /bin/false shell to login on vsftpd
- Using lsof utility
- Scp resume
- Enabling remote desktop on a VirtualBox Machine
- dropbear rsa key problem
- XFS Filesystem has duplicate UUID problem
LAST ADDED
- Using iPhone internet sharing over bluetooth under Linux
- Using USB sound card with amarok
- Multi-conditional search and replace (clearing a ftp trojan script example)
- Disabling ipv6 functionality
- How to convert a mp3 file
- How to choose the fastest Debian mirror
- Disabling reverse dns lookups in ssh
- Rewriting destination ip address
- Deleting A File By It's Inode Value
- Learning which libraries are used for a binary
