any differences in the sysctl parameters?
Main Topics
Browse All TopicsI am running 2 Dell R900 Servers and i have a problem when i ssh from one to the other. Exaple when i ssh in and run a top command it hangs and nothing happens. If its done from any other server it works.Only these 2 servers are not working between them.
what can it be both servers have firewall off. They are also on the same subnet.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
debug3: packet_send2: adding 64 (len 57 padlen 7 extra_pad 64)
debug2: we sent a password packet, wait for reply
debug1: Authentication succeeded (password).
debug1: channel 0: new [client-session]
debug3: ssh_session2_open: channel_new: 0
debug2: channel 0: send open
debug1: Entering interactive session.
debug2: callback start
debug2: client_session2_setup: id 0
debug2: channel 0: request pty-req confirm 0
debug3: tty_make_modes: ospeed 38400
debug3: tty_make_modes: ispeed 38400
debug3: tty_make_modes: 1 3
debug3: tty_make_modes: 2 28
debug3: tty_make_modes: 3 127
debug3: tty_make_modes: 4 21
debug3: tty_make_modes: 5 4
debug3: tty_make_modes: 6 0
debug3: tty_make_modes: 7 0
debug3: tty_make_modes: 8 17
debug3: tty_make_modes: 9 19
debug3: tty_make_modes: 10 26
debug3: tty_make_modes: 12 18
debug3: tty_make_modes: 13 23
debug3: tty_make_modes: 14 22
I've had similar issues in the past where screen output doesn't seem to function properly.
Check the protocol settings on each of the servers and compare it to the client capabilities on the local client as well as the "other" clients. It's entirely possible that you're having a protocol or capability negotiation problem.
You could also try hard-coding the protocols in the server capabilities, or even specifying certain protocol settings or other capabilities on the ssh client command line when connecting to see if it changes anything.
Business Accounts
Answer for Membership
by: brutuzPosted on 2009-09-15 at 09:40:35ID: 25336772
do ssh -vvvv [login]
see where it stops..