| Author |
XP Professional Cannot join Active directory domain
|
|
|
| Hi Folks this is a test case for all.I run a multiboot of XP professional and Win2k prof.I am able to join an Active Directory domain using the Win2K professional.But unable to join using the XP.The system is able to join the domain alright but the system changes do not apply, when I restart to apply the changes,at the log on prompt, the system only allows me to log on locally to the machine. No option to show the domain.I have set different machine names for the different OS but the computer can't seem to save the settings.
The OS seems to be working like its a Home Edition OS which can't join a domain .Any help or tricks to help me out? | |
| enforcer 2003-04-11, 4:03 am |
| could be the that the server is detect the same network card for two 'different' machines.
remove the w2k from the domain and then try putting the XP one in | |
| chodan 2003-04-12, 8:19 pm |
| try this
logon on in this manner
domain\username
password
or you can do this
username@domain_name.suffix
say your domain is "flight.local" and your user account is "fred"
logon with fred@flight.local
or flight\fred | |
| Tech Ranger 2003-04-20, 12:55 am |
| The same machine cannot join the same domain twice using 2 OS instances. | |
| Thunder Cloud 2003-04-24, 9:16 pm |
| quote:
Originally posted by Tech Ranger
The same machine cannot join the same domain twice using 2 OS instances.
Tech Ranger:
This doesn't sound right. I have a laptop that dual boots btw. NT 4.0 and W2K Pro. Both of the OS's have different computer names, but both OS's are members of the same domain. We are a mixed mode environment, and the domain I log in to is not a W2K server, but it still works. Am I missing something? | |
| Tech Ranger 2003-04-24, 11:26 pm |
| You are saying that this is a Win2K domain (mixed mode) and neither of the 2 instances is a dc? | |
| Thunder Cloud 2003-04-25, 7:41 am |
| quote:
Originally posted by Tech Ranger
You are saying that this is a Win2K domain (mixed mode) and neither of the 2 instances is a dc?
* It is a mixed environment
* There are several domains, the particular domain I'm logging into is not an AD domain.
* We have another domain we can log into, with different credentials, that is an AD domain. I have not logged in to this domain with either OS
* Neither of the 2 OS instances on the laptop are DC's.
Is this the issue: Since the domain the laptop logs in to is not an AD domain, then it is possible to have the same machine log in to it? Or, is it possible to do it in an AD domain (Windows 2000), just use different machine names. | |
| Tech Ranger 2003-04-25, 7:49 am |
| The issue has to do with AD domains. This is from personal experience. I could be wrong. It may apply only to cases where the PC is a DC and/or where the user mistakenly uses the same computer name to identify the box. I think it also has to do with whether a computer object is created versus login without managing the box. What I am not clear on is the role of the GUID of the box. Do you know whether the computer's GUID is read at every AD login or is it only for RIS prestaging? | |
| Thunder Cloud 2003-04-25, 8:09 am |
| Tech:
You have stumped the geek.
I have no idea. I will bring that laptop to work next week and test this out. I will attempt to log in to the AD domain with both instances to see if it works. If it doesn't, then it's probably the GUID. I can see the point about whether the machine is a DC or if it uses the same name. But, there are so many dual boot machines out there, I can't imagine Microsoft allowing this to occur. (Yeah, right!) | |
| KScheler 2003-04-25, 8:22 pm |
| I ran into somethig like this in one of my classes today. A student rebuilt/reinstalled his server OS and gave the server the same name. When he tried to join it to the domain as a member server it would not allow him, stating that the computer account already existed. I had not deleted the computer account from AD yet. It apparently was still associating the name with the GUID. I had him rename the machine with a different name and it joined with no problem.
On the dual-boot machine in question, try giving each OS a different computer name than the other. | |
| Thunder Cloud 2003-04-28, 8:01 am |
| Just completed testing logging inot an AD domain with a dual boot machine. One OS is NT 4, the other W2K. No problem, but the OS's do have different machine names. This is probably the key issue. | |
| enforcer 2003-04-28, 8:06 am |
| I think the original post stated that both OS's were on the domain, but the problem was policies were not working on one.
Try setting up some policies and see if they work for both OS's | |
| netport 2003-05-01, 9:40 pm |
| The actual problem here was, a XP pro could not login into the AD. It acted like its a XP home ed. What would differentiate a XP pro from a XP home? The price? | |
| KScheler 2003-05-04, 4:16 pm |
| I ran into something like this in a lab the other day. The XP box would not join the domain until I gave the machine a FQDN. I did this by right-clicking My Computer, click Properties. Go to the Computer Name tab, click on Change, then click on More. Once there enter the primay DNS suffix for the computer. You will need to reboot. After rebooting, try to re-join to the domain.
After I did this the machine joined the domain and "behaved" like it was supposed to. Untill then I'd get "path not found" or "rpc service not available" plus a few other error messages. The thing to remember here is that AD relies so heavily on DNS it's almost scary. | |
| cm2gj 2003-05-06, 10:38 pm |
| quote:
Originally posted by Tech Ranger
The same machine cannot join the same domain twice using 2 OS instances.
disagree.
i have 4 OS on my machine and all OSs can join the domain. | |
| cm2gj 2003-05-06, 10:39 pm |
| quote:
Originally posted by Kakra
Hi Folks this is a test case for all.I run a multiboot of XP professional and Win2k prof.I am able to join an Active Directory domain using the Win2K professional.But unable to join using the XP.The system is able to join the domain alright but the system changes do not apply, when I restart to apply the changes,at the log on prompt, the system only allows me to log on locally to the machine. No option to show the domain.I have set different machine names for the different OS but the computer can't seem to save the settings.
The OS seems to be working like its a Home Edition OS which can't join a domain .Any help or tricks to help me out?
check dns and tcp ip on the xp machine. | |
| chodan 2003-05-07, 8:36 am |
| Did you try my suggestion yet? | |
| Kakra 2003-05-07, 11:28 am |
| Hi Chodan
Tried all that you said but no success.I hope the case I said is clear enough but just as a recap.I Multiboot between Win2k proff and Windows XP proff.I can join the Win2k proff to an active directory domain on a Win2k Server.But for the Win XP I have to go through the process of joining the domain each time I log off It does not register the settings for the domain its joined.
Well Chodan any solutions or tips you can think off | |
| killxp 2003-08-10, 6:36 pm |
| Hi Kakra,
Had the same problem myself on a laptop running XP Pro & Win2K. It appears to be related to the machines GUID, I managed to overcome the problem by removing the machine from AD computers object tree. Then I re-ran the Network ID wizard and re-joined the domain and now all is fine. I gave seperate computer names for each OS, but not sure how this affects the GUID.....but it worked.
Good Luck | |
| jarbob69 2003-08-11, 4:35 pm |
| I agree with the poster above: delete the computer account for the xp machine from the PDC for the domain which you are trying to log in. Then on the xp installation remove from domain, reboot, and then rejoin domain.
Also make sure it can resolve a FQDN for the domain controller. Use a host file entry if necessary. | |
|
| Create new user profile on your server and login into it FIRST WITH THE XP PRO and you will be able to login after that with the W2K too. I haven't discovered yet what exactly causes the problem but it seems to be profile incapability if you first access it and save settings from older MS OS - probably Group policy issues. | |
| anternet 2003-10-16, 4:27 pm |
| I have just had a similar problem. New build of W2k AD native domain following HDD failure on my home network. 3 XP Pro machines could not join the domain, made all the right noises running through the "join domain" wizard, and then got "windows xp computer could not be joined to the domain.... cannot find the network path" at the last minute. Thought it was DNS related and been scratching my head and tinkering with stuff for a few hours . KScheler's posting did the trick for me. I created the computer accounts in AD first, then changed the XP computer name to FQDN as suggested, rebooted then joined the domain 1st time. Big thanks to KScheler .
Ant  |
|
|
|