Home › Forums › OS X Server and Client Discussion › Active Directory › Unable to multihome OD Master in AD/OD domain
- This topic has 1 reply, 1 voice, and was last updated 14 years, 7 months ago by
apprenticewizard.
-
AuthorPosts
-
March 29, 2012 at 9:41 pm #381744
apprenticewizard
ParticipantI have a new Lion Server. The server is an OD Master and bound to the AD server. The Airport connection is at the top of the list in the Network preferences, as well as in the Set Service Order (the gearbox tool). Its address is 10.168.1.x with a router address of 10.168.1.1 with subnet mask of 255.255.255.0. The DNS address for this interface is 8.8.8.8.
The Ethernet address is 192.168.1.x with subnet mask of 255.255.255.0 and NO router address. The DNS address for this connection is 192.168.1.x (the DNS for AD domain).
I have DNS turned enabled on the server with a forwarder address of the AD DNS.
I have all proxy configuration empty, so the only way an Internet request will work is through the wireless.
I can browse the internet with no trouble. However, I cannot browse the internal intranet web sites by name: only by IP address. From the terminal, pings by IP address always work, both to outside addresses and internal addresses, showing all interfaces are connected and working. I cannot ping any internal hosts, whether it’s with short host name or Fully Qualified Domain Name, although the hosts file addresses will work.
It seems that any service that uses DNS (like AD authentication) will fail. This means that although I have imported the Domain Users group from active directory (only after disabling Airport), no user can successfully log into the server’s mydevices page until I once again disable Airport.
So for me, the reality is that one cannot multihome (multi network) an Apple server in a mixed AD/OD network. I would love for someone to prove me wrong without it cosing $695, which is what Apple wants per incident.
March 31, 2012 at 3:16 am #381745apprenticewizard
ParticipantThis has been solved. The secret is to remove any reference to the external DNS on all interfaces. I had to add the internal DNS as the only address on the external Airport connection. Now all functions work: AD credentials work for webpage login, and I’m able to browse the Internet, and Software Update Server continues to receive the updates from Apple. I was able to make the Ethernet interface the primary interface and it still works!
Doing the Happy Dance…
-
AuthorPosts
- You must be logged in to reply to this topic.