• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 468
  • Last Modified:

MAC will not authenticate and log in network users, working with MAC server

I have a MAC workstation running 10.6 that is in a network environment with a MAC server.  Everything was running fine for months until today, now this one computer will no longer allow network users to "authenticate" and log in.  I have tried the following:

Ran Onyx to clean up files
Un-bound and re-bound the machine to the server
Performed a reinstall of the OS files from the MAC disk

The problem still persists.  Of course I have ensured that there is good network connectivity and I can see the network and all network resources when logged in as the local administrator, I just can not get network users logged into this machine.  We are using LDAP on the server to administer the accounts.  Any ideas would greatly be appreciated.
0
jfoster316
Asked:
jfoster316
  • 5
  • 3
2 Solutions
 
abaskervilleCommented:
Have you booted from the CD and done a repair disk?  

We had this problem once and it was caused because we restarted a computer that we thought was hung up during a firmware update.  It booted up okay, but you couldn't get anywhere.  For us, our only solution was to redeploy the system image from the server.

0
 
jfoster316Author Commented:
Yes, I tried booting from the disk and doing a repair, unfortunately that did not work either.  I can only think at this point it has something to do with the kerboros database getting corrupted somehow.  I am going to try and fix the kerberos, but barring that, reinstall is the only thing that I can think should work.
0
 
EdTechyCommented:
A couple of things you can try.
Unbind the workstation from the server. Delete the file /Library/Preferences/edu.mit.Kerberos, rebind.
Check System Preferences>Accounts>Login Options. Make sure there is a check mark next to "Allow network users to log in at login window." Check the options for that and make sure they are appropriate.
Make sure your time is synced to the same server on the workstation and server. Or at least, the time is within a few seconds of each other.
0
Get Certified for a Job in Cybersecurity

Want an exciting career in an emerging field? Earn your MS in Cybersecurity and get certified in ethical hacking or computer forensic investigation. WGU’s MSCSIA degree program was designed to meet the most recent U.S. Department of Homeland Security (DHS) and NSA guidelines.  

 
jfoster316Author Commented:
I have reloaded the MAC, erased the HDD first and did a clean reload.  You may not believe this, but now I can not join it to the server now with the admin account.  It will not allow the admin user and password to even talk to the server.

Something is wickedly wrong with this set up.  I am out of ideas, and have tried all of the suggestions posted here and many others suggested by friends and colleagues.
0
 
EdTechyCommented:
Try binding without authentication.
Here is some info from apple on authenticated binding. I do not require it on my server so I don't know much about it. http://docs.info.apple.com/article.html?path=ServerAdmin/10.5/en/c8od18.html
0
 
jfoster316Author Commented:
I use the binding with authentication so that I can use roaming profiles.
0
 
jfoster316Author Commented:
Issue solved on my end.  Found that after reload and then rebooting the server, this machine finally allowed me to authenticate users on it.  Then hooked this mac back up to the original location and it failed again.  Did some checking and found that the ethernet cable had been crushed back behind some furninture.  This crushing did not seem to have totally terminated the connection, as I was still able to surf the web, see network resources, and the like, but for some reason, the signal was degraded enough to causee the connection to the server to become corrupted when Kerberos was trying to authenticate.  So, after replacing the ethernet cord and then rebooting the server to purge the database, the machine is up and running perfectly fine.  Only MAC could have this kind of crazy issue, IMO.
0
 
jfoster316Author Commented:
This issue all stemmed from a bad cable, that for some reason caused the Kerberos database on the server to become corrupt and not allow this machine to log in.
0
 
EdTechyCommented:
Glad you got it.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Prepare for an Exciting Career in Cybersecurity

Help prevent cyber-threats and provide solutions to safeguard our global digital economy. Earn your MS in Cybersecurity. WGU’s MSCSIA degree program curriculum features two internationally recognized certifications from the EC-Council at no additional time or cost.

  • 5
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now