The following is the error I get when trying to bind Windows XP to the Mac OS X.4 PDC.

[code]
Note: This information is intended for a network administrator. If you are not your network’s administrator, notify the administrator that you received this information, which has been recorded in the file C:\WINDOWS\debug\dcdiag.txt.

The following error occurred when DNS was queried for the service location (SRV) resource record used to locate a domain controller for domain fake.domain.name:

The error was: "DNS name does not exist."
(error code 0x0000232B RCODE_NAME_ERROR)

The query was for the SRV record for _ldap._tcp.dc._msdcs.fake.domain.name

Common causes of this error include the following:

– The DNS SRV record is not registered in DNS.

– One or more of the following zones do not include delegation to its child zone:

fake.domain.name
domain.name
name
. (the root zone)

For information about correcting this problem, click Help.
[/code]

DNS is working just fine.
I can resolve the server name and domain name from the WinXP client.
OD and Kerberos is working perfect on the Mac OS X.4 Server.
I’ve ran ipconfig /flushdns /release /renew and have rebooted but this error still happens.

Any Ideas???!!!

So no . at all?
I’ve setup tons of Win2K AD servers in my career and have always used full domain names ‘something.com’ or fake ones like ‘something.local’.
I’ll have to try setting up the PDC on the Mac OS X.4 Server with the domain ‘something’ and see if I can bind to it with the XP machine.
I did try setting it up ‘something.local’ but that didn’t work.
Thanks for the replies…

I think my problem is bigger then that…
I’ve changed the Windows PDC Domain Settings on the Mac OS X.4 Server to SOMETHING and then tried binding to it via a Windows XP client.
I tried binding to the PDC from the Win XP client through simply changing the Domain under Computer Name and I also tried using the Network ID wizard.
These are the errors I get…
[code]
The domain name SOMETHING might be a NetBIOS domain name. If this is the case, verify that the domain name is properly registered with WINS.

If you are certain that the name is not a NetBIOS domain name, then the following information can help you troubleshoot your DNS configuration.

The following error occurred when DNS was queried for the service location (SRV) resource record used to locate a domain controller for domain SOMETHING:

The error was: “This operation returned because the timeout period expired.”
(error code 0x000005B4 ERROR_TIMEOUT)

The query was for the SRV record for _ldap._tcp.dc._msdcs.SOMETHING

The DNS servers used by this computer for name resolution are not responding. This computer is configured to use DNS servers with the following IP addresses:

10.1.0.1
10.1.0.2
10.1.0.3

Verify that this computer is connected to the network, that these are the correct DNS server IP addresses, and that at least one of the DNS servers is running.

For more information on how to correct this problem, click Help.[/code]

[code]
The domain name SOMETHING might be a NetBIOS domain name. If this is the case, verify that the domain name is properly registered with WINS.

If you are certain that the name is not a NetBIOS domain name, then the following information can help you troubleshoot your DNS configuration.

The following error occurred when DNS was queried for the service location (SRV) resource record used to locate a domain controller for domain SOMETHING:

The error was: “DNS server failure.”
(error code 0x0000232A RCODE_SERVER_FAILURE)

The query was for the SRV record for _ldap._tcp.dc._msdcs.SOMETHING

Common causes of this error include the following:

– The DNS servers used by this computer contain incorrect root hints. This computer is configured to use DNS servers with following IP addresses:

10.1.0.1
10.1.0.2
10.1.0.3

– One or more of the following zones contains incorrect delegation:

SOMETHING
. (the root zone)

For information about correcting this problem, click Help.[/code]

Here is the server configuration from DHCP to DNS…
DHCP supplied DNS Default Domain: something.com, Name Servers: 10.1.0.3, 10.1.0.2, 10.1.0.1, WINS Primary/Secondary: 10.1.0.3, 10.1.0.2, NBDD Server: 10.1.0.2, NBT Node Type: Mixed, NetBIOS Scope ID: SOMETHING
DNS: Name Servers: server.something.com, server.something.com points to 10.1.0.2 and 10.1.0.3, Server IP Address: 10.1.0.2

Again, I’ve release/renewed/flushed IP/DNS. I’ve rebooted the server and the client. LDAP, OpenDirectory, and Kerberos are working 100% on Mac OS X.x clients and the server.

What am I overlooking?

Whelp guess what…???
I’ve enabled NetBIOS over TCP/IP as described at that site.
Then I tried binding to the domain via the Network ID wizard and the Change Name.
I got the same errors as before.
So then I installed the ‘NWLink IPX/SPX NetBIOS Compatible Transport Protocol’ and gave it a try binding the two ways listed above and it gave me the same errors.
I’ve restarted the Win XP machine after making these adjustments each and every time.
Is there something else that might be causing the conflict?

I am binding to the domain two ways.
Right clicking My Computer -> Properties -> Computer Name -> Network ID -> Walk through the wizard to connect to a domain
And I’ve done it this way…
Right clicking My Computer -> Properties -> Computer Name -> Change -> Select Domain and input the domain -> I’m never prompted for an Admin Username/Password to join the domain.

I’ve built and designed Windows NT/2000/2003 Server domains/networks and understand DNS, DHCP, and NetBIOS/WINS/ActiveDirectory.
I’ve also designed Mac OS X.1/4 Server NetInfo/OpenDirectory networks.

The server is running DNS, DHCP, AFP, OD, and Kerberos perfectly. I’ve even tested the SingleSignOn capabilities with success.

What I have noticed in the Samba logs is that both IP/NICs are listening for WINS/NetBIOS. I know having more then one Master Browser on the network can/could cause trouble.
I configured both NICs to listen for OD/LDAP and WINS assuming that the server would do some traffic balancing decreasing latency/lag.

It does give me errors when trying to bind to the domain…
[code]The domain name SOMETHING might be a NetBIOS domain name. If this is the case, verify that the domain name is properly registered with WINS.

If you are certain that the name is not a NetBIOS domain name, then the following information can help you troubleshoot your DNS configuration.

The following error occurred when DNS was queried for the service location (SRV) resource record used to locate a domain controller for domain SOMETHING:

The error was: “This operation returned because the timeout period expired.”
(error code 0x000005B4 ERROR_TIMEOUT)

The query was for the SRV record for _ldap._tcp.dc._msdcs.SOMETHING

The DNS servers used by this computer for name resolution are not responding. This computer is configured to use DNS servers with the following IP addresses:

10.1.0.1
10.1.0.2
10.1.0.3

Verify that this computer is connected to the network, that these are the correct DNS server IP addresses, and that at least one of the DNS servers is running.

For more information on how to correct this problem, click Help.[/code]
Windows service configured as PDC, Domain: SOMETHING, Enabled:WINS…
I’ve tried binding Mac OS X.4 to ActiveDirectory but I also get errors (don’t have them documented).
I know that NetBIOS/WINS isn’t working off the server correctly because the clients can’t even find the server. Also, I have the log settings at high in order to debug this but I get nothing as far as client connection requests/errors.