Remote Access to Headless Server, impossible w

Question

Level 1

46 points

Remote Access to Headless Server, impossible w

Hello

I have a smal problem

Normale I can access my headless macmini i7 server with Apple Remote Desktop.

Now I recognised a problem. I started a recovery with Data Rescue 4. I was able to view the server for a couple of hours, now I can't access the server with ARD.

All the other Services on the macmini works normal. DNS & DHCP seems to work. Also the AFP und FTP Service works normal. Strange is that it is also impossible to access the server by SSH

Is there a way to access my server again with ARD, without to connect a monitor to it? Is it possible to give the SSH and ARD a higher priority?

Regards

Mac mini, OS X Mavericks (10.9.5), OS X Server

Posted on Nov 24, 2014 8:45 AM

Reply

Answer 1

Nov 25, 2014 3:52 AM in response to Gerard Dirks

You can change the SSH settings via ARD and you can change the ARD settings via SSH, however as neither is currently working for you, you are completely blocked unless you have some other remote control software installed e.g. Timbuktu Pro, LogMeIn, TeamViewer, etc.

Is the Server on the same network as your client Mac? If not maybe your network Firewall is the culprit?

Reply

Answer 2

Gerard Dirks Author

Level 1

46 points

Nov 25, 2014 4:01 AM in response to John Lockwood

I will need to wait another 18 hours, then the recovery should be finished.

I if is still not reachable after it is finished, i will need to connect temporarly a monitor to it.

I have no got experience with Teamviwer & Co on a headless server. The Farewall Prompt gives sometimes errors.

Is their a way to give ARD & SSH a higher prorioty? It is not understandable that alle other service runs normal an only ARD und SSH fails

Regards

Gérard

Reply

Answer 3

Nov 25, 2014 5:40 AM in response to Gerard Dirks

I would be guessing either there is a Firewall blocking ARD and SSH traffic, or the processes handling them have crashed, or those services (ARD & SSH) have been disabled.

Try

telnet serveraddress 5900

and see if you get a response. If you get connection refused that port which is the main ARD port is not open and ARD is either not running or being blocked by a Firewall. If you do get a response then it is running and maybe your theory of it responding too slowly due to lack of priority over the disk recovery is accurate.

Once you have access you could look at 'renice' to control the priority given to processes. Also see http://www.ernieflores.net/osx-page-2/adjust-a-mac-apps-cpu-priority-with-proces s-renicer-make-your-app-run-faster/

Reply