Thanks for the reply, but I did a test: I opened an ARD connection to a machine (A) from one system (B). On another system (C), I ssh into A, and ran:
$sudo /System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resources/kickstart -restart -agent
while it worked, and did *something* (see below), it did not kill my ARD remote connection. I had full control still from B.
Stopped ARD Agent.
Stopped VNC Server.
Stopped RFB Register MDNS
That would be how it's supposed to work, if I understand your description correctly. "B" will of course reconnect to "A" when you run ARD on "B". You said, again unless I misunderstood, that you had some other system, "D", holding the connection and blocking you from connecting from "B", in which case using the killall command should get that to release from "D" unless ARD on system "D" is still running in which case it will probably reconnect.
Have I misunderstood your scenario?
Ok, now I'm confused! hehe
Let me start over.
I have a server (S). An unknown client (C-U) is connected to it. Another client, me, (C-Me) wants to connect to S but can't. I can see in the ARD scanner on C-Me that something is connected to S. I want to disconnect C-U so C-Me can connect.
In my test, I simulated C-U connecting to S. Then from C-Me, I attempt to connect to S, but can't.
Then from C-Me, I ssh to S, and I run the Kickstart restart on S, but I still can not connect to S from C-Me.
On the C-U system, I see the connection is still fully connected, and was never disconnected. Therefore, it looks as if the kickstart command did not do anything (in my limited knowledge of what is happening!)
valid question! Esp coming from someone with as much experience as you... covering the bases.
Yes, it's all real.
My "simulation" only refers to the fact that as I've already hard-rebooted the server to clear the real 'unknown" client...I am now testing the "unknown client (C-U)" with a known computer - so I can see what's happening on it when I issue the command from the server via ssh