Forum Replies Created
-
Posts
-
I’ve got this solved, and wanted to post here so everyone knows. It turns out I had set everything up exactly right with one exception- under search suffix in the network card setup, both ethernet cards had to have not “.local”, but plain “local”. Apple evidently has been very literal about the suffix here, and doesn’t have anything in place to trap the “.” if it’s put in there. After both ethernet cards were set to use the SBS box for DNS and both cards had “local” set in the search suffix, it bound right up.
Thanks all, for your help. I learned a lot.
Thanks – tried to run that command, but it wouldn’t accept my password. There’s also no directory in the location you specified. I also can no longer access the internet, or do an nslookup, or get DNS of any kind, so I’ve moved backwards from where I was in the first place.
End of thread. I’ll post again once I’ve got my shit together to the point where I can ask intelligent questions.
Thanks for your help.
OK, still trying to get my AD domain to respond. I reconfigured the OSX box as an Open Directory master, and tried again, no luck. I then attempted to connect Open Directory to the Active Directory on the backup server on the Windows network. With the exception of a faster response time due to not using a broadband connection to get there, I get the same result.
Any assistance anyone can render would be most appreciated – Apple’s about to make $700 offa me otherwise.
Thanks!
How about Open Directory settings? Just by way of giving some more information to see if it triggers anything:
In the Open Directory applet in Server Admin, Open Directory is set as a standalone server, lookupd is running, netinfod is local only, LDAP server is stopped, password server is stopped, Kerberos is stopped. In the logs, the Active Directory Plugin version 1.5.6 is loaded on demand and set active. Under Settings, there isn’t much… set as a standalone server, there is no search base or database set for LDAP, and all the Policy settings appear to be defaulted.
Under computers and services on the left, Open Directory is not lit.
Did I mention I’m brand new at OSX?
Hi Josh, and thanks for joining the thread :-).
I’m not a DNS master, but I found this thread relating to verifying SRV records: http://support.microsoft.com/kb/816587. There appears to be a typo in the locations they’re saying I should look (missing carriage return), but I was able to locate the _ldap and the _kerberos services listed in what I believe are the correct locations.
Farther down the page there is also an nslookup test. I followed the nslookup procedure there (setting nslookup type to all and looking up _ldap._tcp.dc._msdcs.Domain_Name) on the AD box and got back an SRV service location which appears to be correct (Priority:0, weight:100, port:389, and svr hostname). When I try the same procedure on the OSX box, I get a message that the server can’t find it. It is querying the correct DNS server, and if I nslookup the domain without specifying _ldap._tcp.dc._msdcs.Domain_Name, it comes back right away with the correct address. I still can’t ping it though. 🙄
I had already entered {mydomain}.local in that field for both network cards. I changed it to simply .local for both network cards and still get the same result.
Thanks for your help… There are two network cards in the system, one for the outside world and one for the SBS network. The one for the SBS network was configured with the SBS server as the DNS server, as you suggested. I went ahead and set the DNS for both cards to the SBS address, and got the same result, that is to say, nothing. It seems strange to me… I must be missing something very basic, because the procedure appears very simple – go to Directory Access, configure Active Directory, type in the server, click Bind, put in the password… is there more to it than this?
