Binding Client to Server

Question

Level 1

27 points

Binding Client to Server

I have a Mac Mini Server, Mac Pro, and MacBook Pro all running 10.6.3. I have set up and enabled the Directory Service on the Mac Mini for use with my client machines. When I attempt to Bind my MacBook Pro to the Directory Service, I get an "Unable to Add Server - could not resolve address error (2200)" message.

The Directory Service is setup to be an Open Directory Master and I have not experienced any other issues in configuring the Directory Services. Everything has been by-the-book to this point. I have used the "changeip -checkhostname" and verified my DNS is correctly setup.

The network has a DSL Router w/WiFi (192.168.0.1) and the server is using DHCP with a fixed address (192.168.0.20). Everything else is using a DHCP assigned address and all equipment use ethernet (WiFi not enabled).

I have downloaded OpenDirAdmin_v10.6.PDF document, but have not been able to locate any useful information at this point. Any hints on how I can proceed, so I can Bind both of my clients to the server's Directory Services?

Mac Pro, MacBook Pro, Mac Mini Server, iPhone 3GS, Mac OS X (10.6.3)

Posted on Apr 2, 2010 3:28 PM

Reply

Answer 1

foilpan

Level 4

1,385 points

Apr 2, 2010 3:53 PM in response to sysx

make sure you have dns running somewhere on your LAN and that clients and server can resolve the server's hostname. in a small network, i usually run dns on the OD master itself.

for clients, make sure you set the primary resolver to the server's ip in the dhcp config and add the search path. that way, the clients will look to the server first for name resolution without having to change anything on the client side. point the server to itself as primary resolver in network prefs -> dns and also add the search domain there.

without all that in place, lots of stuff won't work. report back if you already have all that in place and binds still fail.

Reply

Answer 2

sysx Author

Level 1

27 points

Apr 2, 2010 5:13 PM in response to foilpan

The DNS is enabled on the Mac Mini Server and I set the DNS Server address to the Mac Mini IP Address in both the MacBook Pro and the Mac Mini Server network configurations. I am not sure what to use as a search path.
server.company.com or server.local or ????

I tried the Bind again and it still fails at the same place with the same message.

Reply

Answer 3

foilpan

Level 4

1,385 points

Apr 2, 2010 6:10 PM in response to sysx

use the default zone you have configured in dns on the server.

so if your server responds to server.company.com and the server is authoritative for the company.com zone on your lan, add company.com to the search path.

Reply

Answer 4

sysx Author

Level 1

27 points

Apr 2, 2010 7:18 PM in response to sysx

I fixed the search domain issue with "company.com", but still had the same problem. I open the console window and looked at the messages. I got four identical messages during the process as follows:

4/2/10 6:56:28 PM System Preferences[3446] -[ODCAddServerSheetController didFinishGettingServerInfo:] for "server.company.com" got error Error Domain=com.apple.OpenDirectory Code=2200 UserInfo=0x343030 "Custom call 200 to LDAPv3 failed."

Then followed by this error message:

4/2/10 6:57:59 PM System Preferences[3446] -[ODCAddServerSheetController handleOtherActionError: gotError: Error Domain=com.apple.OpenDirectory Code=2200 UserInfo=0x1f3f70 "Custom call 201 to LDAPv3 failed.", Could not resolve the address.

The process stops and an error message is displayed. What is interesting is that I have exactly four users defined in Workgroup Manager. Coincidence or relative?

Also, "server.company.com" in the first four messages showed up as:
"server.co" "server.compa" "server.company" & "server.company.com"

One of the messages had the correct fully qualified name.

Reply

Answer 5

sysx Author

Level 1

27 points

Apr 3, 2010 6:30 PM in response to foilpan

Thanks for getting me to re-look at the DNS information. Everything was set up correctly, but I finally noticed (earlier today) I had checked the "Authenticate Bind" on the server. When I unchecked that box, everything worked liked it should have. Thanks again.

Reply