![]() ![]() I did not force the unbind as I figured I would not be able to rebind if the Domain Controller could not be contacted. It may seem silly but where does that ID come from -where do I check to see if that Computer ID is actually the ID for the server? I assume that it would still be correct after the upgrade -but maybe not? Maybe that isn't the problem at all? One more piece -I tried to Unbind by clicking the button in the Directory Utility -up popped a message that read "Unable to contact Domain Controller". ![]() The Active Directory list on the Windows 2003 server does list that Computer ID as being bound. It does show the "Unbind" button which would imply that binding exists. I'm not certain that the Computer ID is correct. Also, your question about marking DNS servers to be used for queries is the wrong way round - its the domain name part that needs to be marked, for use with the internal DNS server, not the IP. Editing of that Active Directory listing shows the correct forest and domain. The VPN server should be configured to specify the name servers and the domain(s) that these should be used for. An account must exist on the domain before the laptop can join it. Directory Utility shows Active Directory. Follow these steps to join your Apple Mac laptop to the University domain. Authentication worked perfectly from the same computers before server upgrade to Yosemite 10.10 and Server 4.0. Upgraded a server from Mavericks and Server 3.2.2 to Yosemite and Server 4.0 and have now lost the ability for users to authenticate using an Active Directory account on our Windows 2003 server. ![]() We are having as issue that might be related. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |