Skip to main content
Question

Casper Remote - SSH fails to authenticate

P
Forum|alt.badge.img+6
Sending Wake On LAN command... Opening SSH Connection to 10.85.31.22... Authenticating... Authenticating...

This question has been proposed before, but my typical actions for resolution are all failing.

  1. I've had this fail when the hostname on the machine hadn't updated properly. (check)

  2. I've had this happen randomly when even though 'Remote Login' and 'Remote Management' are both checked in the sharing menu, ssh and screen sharing fail, this is typically resolved by toggling the check box. (check)

I've also been able to verify that I can login in as a local and domain user via ssh to the machine. So SSH would appear to be working

  1. I've also seen the issue described here, where upgrading whole OS versions, screws with <501 accounts. (As is our Management account) https://www.jamf.com/jamf-nation/discussions/8534/casper-remote-not-authenticating

I've killed the jamf binary, deleted the admin account, deleted the record from JSS, re-enrolled the machine, and even narfled the Garthok.

But it still returns:

Authenticating... Authenticating...

I don't know where else to look at this point - Any Suggestions?

Edit: If anyones wondering why the number list restarts back at 1 I typed 3, but it's parsed back to 1.
inb4 pics or didn't happen.

    5 replies

    P
    Forum|alt.badge.img+14
    • perrycj
    • Valued Contributor
    • 296 replies
    • January 17, 2017

    @zerocool This usually happens when the management account credentials saved in the inventory record for this or any Mac showing this behavior are incorrect.

    Can you try just verifying the management account credentials are correct and then see if it will authenticate?

    P
    Forum|alt.badge.img+6
    • Phatmandrake1
    • Author
    • New Contributor
    • 5 replies
    • January 17, 2017

    Yes, I have manually assigned our local admin account (verified the login on the machine and via ssh) in JSS as a management account, and have also tried reassigning through JAMF recon.

    Previously this /has/ been successful, but it's not the ticket this time around.

    P
    Forum|alt.badge.img+14
    • perrycj
    • Valued Contributor
    • 296 replies
    • January 17, 2017

    If you can manually ssh in via terminal with the same credentials and that works fine.. i would delete the inventory record of that mac and re-enroll. If it's all or a bulk of your Macs, I would contact JAMF Support since you've tried most steps to resolve this already.

    R
    Forum|alt.badge.img+3
    • rushingj
    • New Contributor
    • 3 replies
    • January 18, 2017

    I ran into this a few months ago. I got the same response when I tried to use Casper Remote into two of our labs. I could successfully SSH into the computers using the JAMF management account but for some reason Casper Remote would get the error.

    For me the fix was to run the delete account command on each computer and remove the JAMF management account.

    jamf deleteAccount -username <management account username>

    then enroll the computer with JAMF again.

    A
    Forum|alt.badge.img+4
    • argo
    • New Contributor
    • 4 replies
    • February 12, 2018

    Stumbled onto this as well.
    Computers made check-in's and also sent inventory updates but if I wanted to "hard" push something they just kept pending on "Authenticating..." I tried Network scanning via recon but some computers skipped this and still the problem occurred, so I took the IP-s and enrolled them one-by-one with remote enrollment in recon and this solved my problem.

    Reply


    Most helpful members this week

    Terms & ConditionsCookie settingsAccessibility statement

    Cookie policy

    We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

     
    Cookie settings