Can't ssh to xserve

Question

Can't ssh to xserve

I'm having some difficulty logging in to our Xserve (running 10.4.2) from Terminal running on local machines on our network. I ssh admin_user@X.X.X.X, hit enter and it just sits there (i.e. I never get the prompt for the password)

I can ping the serve fine through Terminal (either the IP address or the local name), file services and all the other services are running fine for the client macgines in OS X, but it doesn't responde to ssh connections. I can also log in fine with that admin user account (including inside Terminal) if I go and sit in front of the server itself.

Any ideas?

Posted on Aug 28, 2005 6:42 PM

Reply

Answer 1

Aug 29, 2005 1:22 PM in response to Garth Humphreys

Could this be prevented by a firewall (port 22) ?
Perhaps the user does not have access, or does not have a default shell set in WGM?

-jeremy

Reply

Answer 2

Aug 31, 2005 10:27 PM in response to Jeremy Matthews

The log in name is an administrator account on the server and has a default shell set. It's all happening on our local network inside our firewall so I don't think that's causing the problem.

Cheers

Garth

Reply

Answer 3

Sep 1, 2005 7:36 AM in response to Garth Humphreys

Does the server have it's firewall turned on? If so, check out the server's firewall rules. Turn on firewall logging while you work on this to see if your packets are being blocked.

Have you enabled or disabled SSH access for individual users? With Server admin, click on the server (as opposed to one of the server's services) and click Settings (bottom right) and hten Access (top right).

-Matt

Reply

Answer 4

Sep 21, 2005 7:43 AM in response to Garth Humphreys

When i have a system in this state, "sometimes" the following works:

ssh system.foo.edu bash
(you will not get prompt, but things like ls may produce output)
shutdown -r now

or for that matter: ssh system.foo.edu "shutdown -r now"

Reply

Answer 5

Finlay

Level 4

2,415 points

Sep 21, 2005 12:12 PM in response to Garth Humphreys

Hi Garth,

Can you post the output of this command:

ssh -o LogLevel=DEBUG3 admin_user@X.X.X.X

Hopefully that might shed some light on the problem.

Reply