Software :: Binding Mac To Win2003R2 AD DC
Jan 25, 2010
I have a Mac G4 that I am attempting to bind to AD. When I attempt to bind I get error: "An invalid domain and Forest combination was specified. You should enter a fully qualified DNS name for the domain and forest." DHCP is providing IP and and a HP switch is providing the routing. In Network connection setup I pointed to the client to DNS server to use. NTP is coming from the same server as DNS. I have also set the time server on the machine. I have no problems pinging the IP to these servers, but ping to hostname fails. If I do an NSLookup from that machine using the hostname, I will get a return with the IP.
It would seem the reason I am not able to connect to AD is because the domain name can not be resolved.
OS on the Mac is 10.4.11
DHCP is being provided by a Mac OS X server 10.4.8
DHCP routing is provided by an HP Proliant Switch
DNS is provided by Win2003R2 Domain Controller
View 1 Replies
May 7, 2012
I am having difficulty binding clients to multiple open directory servers. All clients are running Lion. This issue did not occur under Snow Leopard. The servers are both Mac OS X Servers running Open Directory. There are two domains to which the client is successfully bound (DomainA and DomainB). If a user attempts to login using credentials from DomainB, they log in successfully but home folders are "not in the expected location" - so no data is present. If I unbind the client from DomainA and then attempt to login using credentials from DomainB, the issue is resolved. Is there a way to set a priority for how the client binds?
View 1 Replies
View Related
May 15, 2012
I am running an open directory/active directory network. Authentication is from the Windows server 2003 active directory. It has worked fine until the last month. Now clients stop authenticating & when I check the AD plugin it says network accounts are not available. I can force the server to unbind, then renew the binding & everything works great.Is there any work around or fix for this other than upgrading the windows server to 2008?
Info:
OS X server, Mac OS X (10.6.8)
View 2 Replies
View Related
