WinXP-Pro Trust Relationship Failed to Join Domain

M

mark shahan

Problem: While using the Network Identification Wizard to
join a Windows 2000 domain with an existing account from a
new Windows XP Professional workstation, the process
failed.

A dialog box stating that "The user could not be added
because the following error has occurred: The trust
relationship between this workstation and the primary
domain failed" appeared.

The workstation's Event View contains the following error:
"No suitable Domain Controller is available for domain
RCMG. An NT4 or older domain controller is available but
it cannot be used for authentication purposes in the
Windows 2000 or newer domain that this computer is a
member of. The following error occurred: There are
currently no logon servers available to service the logon
request."

Environment:
1-Cisco router with NAT
1-Windows 2000 Server as Domain Controller w/DHCP,DNS,WINS
1-Windows NT 4 Server as Backup Domain Controller
20-Windows NT 4 Workstations as DHCP clients
5-Windows 2000 Pro workstations as DHCP clients
5-Windows XP Professional workstations as DHCP clients

The LAN uses private IP addressing.
The Windows 2000 Server provides the private IP addresses
with DHCP services.
The Cisco router provides NAT for 1-static private IP
address.
All workstations recieve their private IP address from the
Windows 2000 DHCP server.
The DHCP server's scope options push the following to each
workstion:
1. a private IP address and matching subnet mask
2. the router's 1-static private IP address as the gateway
entry
3. both the (a) router's public IP addresses and (b) the
Domain Controller's IP address as the DNS entries

Current Conditions:
All Windows NT 4 Workstations and Windows 2000
Professional workstations can both login to the domain and
surf the Internet.
Only the new Windows XP Professional workstations cannot
login to the domain, but can surf the Internet.
When I switch order of DHCP DNS entries pushed to each
workstation from (a) & (b) to (b) & (a), all XP clients
can login but not surf but all other workstations could
still do both.
 
M

Matt DuBois [MSFT]

Set your clients to point only to the Windows 2000 server for DNS, and
configure your Windows 2000 server to be a DNS forwarder. Take your ISPs
DNS completely out of the configuration. For instructions on how to
configure a DNS forwarder, see the "How to Configure Forwarders" heading in
the following article:

http://support.microsoft.com/?id=323380
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top