Joining Domain problems 1

[GlenJohnson]

I've been making my W2K pro machines join our domain. I've had no problems, except now I have one that tells me "Your Computer could not be joined to the domain because one of the following errors has occured. The credentials supplied conflict with an existing set of credentials." I've seen this in the past when someone has added a computer manually to AD. I checked AD and even did a find, but the computer does not exeist in AD. Ideas? Thanks. Glen A. Johnson
Microsoft Certified Professional

"Curiosity is one of the most permanent
and certain characteristics of a vigorous intellect."
Samuel Johnson (1709-84); English author.

 

[FilthPig]

That error usually happens when you make connections to a system using two different usernames. For example, if you map a drive to SERVERA using johndoe and while that drive is mapped attempt to map another drive using janedoe you will recieve that error. Marc Creviere

 

[donnie4564]

Change computer name joining to a wkgroup.

Change computer name again (to a name that’s never been used) joining to domain.

 

[GlenJohnson]

Tried joining the domain using my logon, which has worked on other pc's in the past. Same error message. Tried changing the name, same error message. Did a search in AD for multiple pc's and multiple accounts, nothing. Going to move on to my other pc's and come back to these when there done. (Hope I don't have the same issue with any of the others.) Thanks. Glen A. Johnson
Microsoft Certified Professional

"You cannot create experience. You must undergo it."
Albert Camus (1913-1960); French writer and philosopher

 

[blkdawn]

Glen, are you joining them as an Administrator and if so is that the same way you joined the others ? It sounds like a permissions issue, dont quote me tho. Maybe also take a look at configs and shares, believe it or not, 2k/ad are kind of sensitive regarding shares and stuff, especially *.exe's. Have you tried the service pak 2 and security update, if so do you notice a difference, and what ?

 

[GlenJohnson]

Service packs a good idea. Haven't looked there. put IE6 and sp2 on all w2k machines, but some may have slipped through the cracks. By default, I give users admin rights on there pc's so they can add software if needed. Not to strict around here. I don't think it's a permissions issue, because I can log on as me, (I also give myself an account with admin rights by default with all new w2k machines) and joined the domain that way, then logged on al the user and had them join the domain. Tried that with the problem pc's with no luck. Thanks, though. You've given me something to think about. Glen A. Johnson
Microsoft Certified Professional

"You cannot create experience. You must undergo it."
Albert Camus (1913-1960); French writer and philosopher

 

[GlenJohnson]

I just checked. One of my machines that joined the domain with no problems has the same ORIGINAL sp as the one that won't join the domain. Going to msdn.microsoft.com now. Thanks. Glen A. Johnson
Microsoft Certified Professional

"You cannot create experience. You must undergo it."
Albert Camus (1913-1960); French writer and philosopher

 

[GlenJohnson]

I think I've found the problem about why some of my w2k machines join the domain and others don't, now I'm in search of a solution. I checked the event log on the machines that didn't join the domain, and everyone had an error message that it couldn't promote itself to a master browser, it believes the master browser is another w2k machine. I looked at the machines that joined the domain, and each one had the same error message, but they though the master browser was our main server. I went to one of the 2 servers that are members of the domain and ran browstat status and this is what I got.
Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.

C:\WINNT\Profiles\Administrator>browstat status


Status for domain RPCNT on transport \Device\NetBT_Tcpip_{1B81A9F8-8A93-4E06-A30
E-7B34E4DBC370}
Browsing is active on domain.
Master browser name is: NTS1
Master browser is running build 2195
2 backup servers retrieved from master NTS1
\\NTS2
\\NTS1
There are 15 servers in domain RPCNT on transport \Device\NetBT_Tcpip_{1B81A
9F8-8A93-4E06-A30E-7B34E4DBC370}
There are 3 domains in domain RPCNT on transport \Device\NetBT_Tcpip_{1B81A9
F8-8A93-4E06-A30E-7B34E4DBC370}

C:\WINNT\Profiles\Administrator>

We only have 3 servers, and only 2 are members of the domain. NTS2 is a stand alone server that we use for experiments. NTS3 is our main server and it's not listed. I've got to figure out how to make sure all w2k machines see nts3 as the master browser and turn off browsing.
I'm assuming the 15 servers it sees in this report are going to be the w2k machines that don't join the domain. The three domains it sees, I'm guessing are the three servers. Wish me luck. Glen A. Johnson
Microsoft Certified Professional
gjohn76351@msn.com

"You cannot create experience. You must undergo it."
Albert Camus (1913-1960); French writer and philosopher

 

[GlenJohnson]

the deeper I go the more confused I get. On 4/3/02 the browser was started. On 4/4/02 the browser gave an information message that it was have problems. On 4/4/02 the browser could not recieve a list from the master browser and the browsing service stopped. I went to my main server and typed in the browstat status and I recieved an error message that this was not a recognized command. This is bizzare! Glen A. Johnson
Microsoft Certified Professional
gjohn76351@msn.com

"You cannot create experience. You must undergo it."
Albert Camus (1913-1960); French writer and philosopher

 

[caddnima]

The same thing happens to me...

1) I tried to disconnect to the domain by doing a workgroup configuration.

2) I did not even change the computer name...
3) Restart
4) And join back to the domain using the same computer name...

and it worked...

 

[donnie4564]

This problem has to do with the DC creating a trust with the PC. It seems as though the admin password could create the trust. Anyway, the answer is in changing to workgroup and the computer name, then to domain, which has worked for me several times. You can try creating the computer in AD then joining domain but I have never got that to work.

 

[ChrisHirst]

Whenever this has happened to me the solution posted by caddnima has always worked.

Chris.

 

[GlenJohnson]

My only problem is they are already a memeber of the workgroup. I can't go back to a Workgroup config if it's already set up. I'm looking into turning off the browsing settings on the pro machines since I have DNS set up. I don't think the pro's should be browsing to begin with, so the problem of which thinks which is the master browser will go away. Thanks Glen A. Johnson
Microsoft Certified Professional
gjohn76351@msn.com

"You cannot create experience. You must undergo it."
Albert Camus (1913-1960); French writer and philosopher

 

[GlenJohnson]

I may have muliple issues here, including security. I noticed that someone had manually name the pc pcname/domanename.com instead of that being assigned by the server. I also noticed on another pc that had joined the domain, the domain name was domanename.com instead of domainname, which is how I set them up usually. I added the .com on the end of one of the pc's that wouldn't join the domain, and he joined the domain with no problem. The only thing is after copying the profiles over TWICE, when I start outlook, I get an error message that says he doesn't have rights to the original username's pst file. I had to put him back in the workgroup. I've also noticed that the people I've had authenticate to the domain don't have rights to defrag there pc. They can log on locally and do it just fine. I always thought W2K security was pretty lax until you manually set it up. I've got some research to do. Glen A. Johnson
Microsoft Certified Professional
gjohn76351@msn.com

"By attempting the impossible, the possible is achieved."
Henri Barbusse (1873-1935); French writer.

 

[Guest_imported]

This took me 2 hours but simply, make sure that your local machine administrator password (before you add it to the domain) is different to the server administrator password.

It worked for me.

 

[Guest_imported]

I seem to be having a problem adding a system with Win2K to an existing domain. When I try to add it, the message I get is "Your computer could not be joined to the domain because the following error occurred: An internal error occurred." Does anyone have an idea of what the problem could be?

KQuintyn

 

[GlenJohnson]

Fixed it. Turned off browsing in services and registry.
Joined the domain, then copied the olduser profile ovet to the newuser profile and checked the permitted to use button and selected the newuser. Finally went to local users and groups, selected the admin group and added the new user profile from the domain. Everythings perfect now. Talk about a hair puller. Thanks for all the help. Glen A. Johnson
Microsoft Certified Professional
gjohn76351@msn.com
"It is wise to disclose what cannot be concealed".
Friedrich von Schiller (1759-1805); German dramatist.