speckytecky Posted March 31, 2011 Posted March 31, 2011 (edited) Got a new iMac which I have bound to the network. I see it in AD but when I now restart the Mac it refuses to log onto the domain. Logging on as local again and checking the directory Utility the domain is no longer accessible. What did I miss doingg? Steps to Bind were: Applications / Utility / directory Utility.app / Services Tab / Active Directory Followed this through and with Domain admin powers bound the mac. Next System Preferences / Accounts / Login Options / Disabled Automatic and changed Names to Names and Password. restart and tried domain\account with password Failed Logged back on local and checked to find domain no longer available and Internet also no longer connected. All IP's look ok. Edited March 31, 2011 by speckytecky
Treecat Posted March 31, 2011 Posted March 31, 2011 Well, we have one classroom with 20 macs here, and the plan was to bind them to Active Directory aswell. I could join them to the domain using the tools in system preferences, and everything seemed fine. But after a reboot, the domain could not be found anymore. I have spend a couple of days on this problem, but never found a solution. What we do now, is use a local profile named "student" without password, so every student can log in using that. And I made a script witch give the student the option to enter their student number and password so then it mounts their home directory located on the windows server, so they can access their own files. When user logs off, the student profile is overwritten by a default profile again, so stuff dont get messed up for the next user. 1
speckytecky Posted March 31, 2011 Author Posted March 31, 2011 Is this issue a setting that I need to change in Directory Utility / Advanced / User Experience: Currently Mapping and Administrative - nothing ticked. Network Protocol SMB and Default User Shell bin/bash.
speckytecky Posted March 31, 2011 Author Posted March 31, 2011 Thanks Treecat - your first I notice! I don't want to run a workaround though - I'm thinking it must be a step thats really simple that I'm missing. I had the same issue with the Internet and managed to find the setting to change for that. I'm thinking that as the Mac has bound to the domain but subsequently the domain is shown but listed as not available then it must be a setting somewhere that would clearly be obvious to an experienced Mac Tech but missing / less obvious to us old Windows folk!! Well, we have one classroom with 20 macs here, and the plan was to bind them to Active Directory aswell. I could join them to the domain using the tools in system preferences, and everything seemed fine. But after a reboot, the domain could not be found anymore. I have spend a couple of days on this problem, but never found a solution. What we do now, is use a local profile named "student" without password, so every student can log in using that. And I made a script witch give the student the option to enter their student number and password so then it mounts their home directory located on the windows server, so they can access their own files. When user logs off, the student profile is overwritten by a default profile again, so stuff dont get messed up for the next user.
clareq Posted March 31, 2011 Posted March 31, 2011 Macs are very sensitive to the time being off - make sure that the times are synced.
3s-gtech Posted March 31, 2011 Posted March 31, 2011 100% on the above, that's where our early issues arose - set them to sync to your NTP server. Not got a Mac in front of me to check the individual directory settings for you, but the AD server not responding could be caused by a number of problems. Is your DNS working nicely? Is your domain not named domain.local?
speckytecky Posted March 31, 2011 Author Posted March 31, 2011 Job done - turned out that a restart isn't good enough for Macs. Shutting it down then starting up again and it let me log onto the Domain!!
speckytecky Posted March 31, 2011 Author Posted March 31, 2011 OK I now hate Macs I was logged on it on the Domain adding printers then it lost the network ability again - mid adding a printer and has refused to let me log back on the domain ever since!
Treecat Posted March 31, 2011 Posted March 31, 2011 Kinda sounds right like the problems I had, sometimes it works, and with luck also after a reboot, and then at random times it just refuses to connect again. If you find a solution then I would be happy if you post it here, I might consider putting our macs on the domain again if there's a solution to this.
speckytecky Posted April 8, 2011 Author Posted April 8, 2011 Strange old thing! Successfully bound several to the domain yesterday. Had to go to Network / advance / directory Utility then set a new setting in LDAPV3 and configured it's various settings for our proxy. Not convinced about having Macs on the AD as apart from being able to log onto the domain and folder access what else is actually useful about it?
3s-gtech Posted April 8, 2011 Posted April 8, 2011 With the 'Magic Triangle' running, it's a nice system. Then you can lock down settings, manage centralised features etc, and only have to issue one account per user. Backups come from their usual home areas too. I'd counter - why wouldn't you have them on AD? When it's sorted, they just work. 1
Treecat Posted April 11, 2011 Posted April 11, 2011 Only problem with the magic triangle is that you must have an Apple server for that, and if you only have 15 macs like us then its not really worth it to get another server just for that.
iSteve Posted April 11, 2011 Posted April 11, 2011 Check your DNS is perfect for forward and reverse lookups. In directory utility, make sure your AD is the first item in the search path, and again, time has to be correct with your domain controller +/- 5 minutes I believe. Re - golden triangle. Run OS X server on any old second hand Mac, and you have a very cheap, secure solution to managing a small amount of Macs.
nonmonotonic Posted April 12, 2011 Posted April 12, 2011 The shutting down fix would point to time difference. Is your Mac synced to a NTP ( time ) server?
RobMongoose Posted April 12, 2011 Posted April 12, 2011 We've had similar issues. What it came down to was that OS X seems to take a little while after boot to get a DHCP address and get its DNS resolution working. The solution we came up with was to set a managed preference to show the network status on the login prompt and add a message asking the user not to attempt login until the light goes green. This does require a Mac server though.
3s-gtech Posted April 12, 2011 Posted April 12, 2011 The fun of Nvidia Nforce network cards - good choice Apple!
iSteve Posted April 14, 2011 Posted April 14, 2011 They have done this for ages, even with Broadcom cards. You don't need a Mac server to show network/directory status in the login window. Simply run this command in Terminal: sudo defaults write /Library/Preferences/com.apple.loginwindow AdminHostInfo DSStatus That'll give you the red/amber/green lights.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now