#int - Known Nomad Login Issues

How To Resolve Nomad Login Issues

This article explains how to resolve common & known issues when logging in to Nomad or if NoMad is missing from the machine's list of applications and Self Service.

Prerequisites: 

  • A Biola issued Mac Computer
  • A Biola NetID & Password
  • *An admin_netid account
    • To enroll a device into JAMF
 

Instructions

Primary Troubleshooting Steps:

  1. Confirm machine is connected to the internet
  2. Confirm NetID & Password are correct
  3. If the Nomad client doesn't automatically connect to the AD domain
    • Manually input ad.biola.edu in the domain field
  4. Unenroll and Re-enroll in JAMF

 

"Not Connected. Unable to reach any KDCs in your realm"

  • If you get the following error message: "Not Connected. Unable to reach any KDCs in your realm. You are most likely not connected to the AD domain."
  • Resolution: Sign into Enterprise Connect - after that is successful, NoMad should automatically sign in. Enterprise Connect should be in the list of applications or in Self Service.

 

Need more help?

If you cannot find your answer here or related articles, please view the section "Related Services / Offerings" to open a ticket.

Please provide feedback on this article, especially if it is not accurate or providing an answer you expect. Select "Yes" or "No" below where is asks "Was this helpful?" This feedback helps us and the rest of the community provide better resources.

Print Article