Windows Forum

Ask something
Discussion Locked

NT Domain Setup Problems in Win Xp Pro

0 helpful
5 replies

by trinianouk

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi,

I have just recently upgraded one of my computers on my Ethernet network from XP Home to XP Pro.
We have an NT4 SP6a server, and I am trying to get the XP Pro machine to connect to the DOMAIN..it is currently connected as a Workgroup computer.

When I change the options under My Computer to "Member of Domain" i enter the domain name. Then it asks for user name and password.I enter the username and password the same as I have it on the NT Server i.e. in User Manager for Domains.

When the XP Pro machine tries to connect to the domain i'm getting the following error:
"The session setup from the computer SUPP-MNGR failed because there is no trust account in the security database for this computer.
The name of the account referenced in the security database is SUPP-MNGR$."
Event ID: 5723
Source: NETLOGON

WHAT AM I NOT DOING??? It should connect...i'm seeing all the computers in network neighborhood.

Any help would be greatly appreciated!!!
Jason

5 replies

by bob the builder

try creating a computer account (not a user account) for the computer in question. If the compter is already in the domain then remove it and then add it again.

by ltop

Also, you need to use a user account which has the priviledges to add workstations to the domain (not the local admin account)

regards

by rboone

The following is a snipplett from the Microsofts Support web site. It should resolve your problem:

The NETDOM command line utility makes it possible to reset the secure channel of the BDC. This can be very useful when the NetLogon service on the BDC cannot start due to a secure channel problem.

The BDC secure channel can be reset as follows:

NETDOM BDC mybdc /RESET

The command above may be run on the PDC, BDC, or any member of the domain, provided that you are logged on as a user who is a member of the Domain Admins group. The output looks similar to the following:

NetDom 1.2 @1997.
Querying domain information on computer \\MYBDC ...
The computer \\MYBDC is a domain controller of THEDOMAIN.
Searching PDC for domain THEDOMAIN ...
Found PDC \\THEPDC
Verifying secure channel on \\MYBDC ...
Verifying the computer account on the PDC \\THEPDC ...
The computer account for \\MYBDC doesn't exist or has an invalid
password.
Resetting secure channel ...
Changing computer account on PDC \\THEPDC ...
Stopping service NETLOGON on \\MYBDC .... stopped.
Starting service NETLOGON on \\MYBDC .... started.
The BDC \\MYBDC secure channel was reset successfully.
Logoff/Logon \\MYBDC to take modifications into effect.

The command above resets BDC secure channels only if required. If the password for the BDC secure channel was good, then you receive a message silimar to the following:

NetDom 1.2 @1997.
Querying domain information on computer \\MYBDC ...
The computer \\MYBDC is a domain controller of THEDOMAIN.
Searching PDC for domain THEDOMAIN ...
Found PDC \\THEPDC
Verifying secure channel on \\MYBDC ...
Verifying the computer account on the PDC \\THEPDC ...
Secure channel checked successfully.

by curacao_dejavu

you can do either one following.
rename the computer and then try to join the domain.
create a computer account manually, in the domian controller.
Reinstall the computer with xp-pro (it could be a problem due the upgrade of xp-home to xp-pro)

You did verify already the the eventlog is clean of errors ..

Also check the http://tinyurl.com/26zyp ms article

Leopold

This discussion is closed to new replies.