I am intending to use my Athlon64 box with Suse 9.0-64 for a game server which means that all communication will be remote via ssh. It will replace an existing box that has been running a year and a half on RH7.3. The 64 has been working fine as a local terminal. I have kept everything up-to-date. However, I am having severe problems with ssh (good thing I tried it before installing it 30 miles away). Putty from windows aborts after accepting a password. Using ssh from another (32-bit) box will log in and run "ls" commands but hangs on a "cd" command. Only recourse is to Cntrl-C and exit. Anyone else having these issues? Or is everyone using their systems locally? Thanks. ......Chuck
Chuck Gibke
I am intending to use my Athlon64 box with Suse 9.0-64 for a game server which means that all communication will be remote via ssh. It will replace an existing box that has been running a year and a half on RH7.3.
The 64 has been working fine as a local terminal. I have kept everything up-to-date. However, I am having severe problems with ssh (good thing I tried it before installing it 30 miles away). Putty from windows aborts after accepting a password. Using ssh from another (32-bit) box will log in and run "ls" commands but hangs on a "cd" command. Only recourse is to Cntrl-C and exit.
Anyone else having these issues? Or is everyone using their systems locally?
I'm using ssh since ages with AMD64 systems and we never had problems. This looks more like a network problem to me, Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj SuSE Linux AG, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Chuck: I've used ssh a lot both to and from my Opteron system without incident. Does putty have some sort of a verbose or diagnostic mode you can turn on to see protocol opterations? Command line ssh uses the "-v" switch. It might be interesting to see the output of such a thing. In particular, ssh really doesn't care about the user doing "ls" or "cd" - it's just passing the characters you type to the remote shell. Have you tried enabling rsh or telnet and seeing if remote access works for those protocols? Good luck, - Darrell On Tuesday 03 February 2004 04:55, Chuck Gibke wrote:
I am intending to use my Athlon64 box with Suse 9.0-64 for a game server which means that all communication will be remote via ssh. It will replace an existing box that has been running a year and a half on RH7.3.
The 64 has been working fine as a local terminal. I have kept everything up-to-date. However, I am having severe problems with ssh (good thing I tried it before installing it 30 miles away). Putty from windows aborts after accepting a password. Using ssh from another (32-bit) box will log in and run "ls" commands but hangs on a "cd" command. Only recourse is to Cntrl-C and exit.
Anyone else having these issues? Or is everyone using their systems locally?
Thanks.
......Chuck
- -- sused@mucus.com "Perfect! ....what am I doing?" -- Washu -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQFAH8iseo6c0kw6mZ0RAv3MAJ9vDFuY9AqQI3Hi056NYyjFUxQu8ACeK85e 59kHvo7lFL8r7bYQ56F7CQk= =dT6n -----END PGP SIGNATURE-----
participants (3)
-
Andreas Jaeger
-
Chuck Gibke
-
Darrell Shively