Windows Forum

Ask something
Discussion Locked

Windows XP Domain Issue

0 helpful
16 replies

by pjcannon

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

I have a client with a laptop(used got a "deal" on it, meaning of course no XP or other software cd's) running Windows XP Pro SP2. Went to join it to a windows 2003 domain but the network id is greyed out. If you click change the domain & workgroup boxes are greyed out. You can change the computer name but not the workgroup name or join it to a domain. This is one I have never seen before and have yet to turn up anything on Google or at Microsoft. Any ideas would be appreciated.
Pat

16 replies

by hal 9000

You'll most likely have to install some Windows drivers by going to the Add Remove Programs in the Control Panel and clicking on Windows Components and with a XP SP2 Pro CD install the missing items.

Col

by jamesrl

While HAL's suggestion may get you up and running on that problem, I would highly suggest doing the following - take off any files created since they bought it, then format it and install a clean OS on it. You could be finding and fixing little problems for a long time on it. Better to come clean and start fresh than to inherit someone else's problems.

James

by pjcannon

I appreciate both responses, my client doesn't own an XP cd and wants to avoid buying it at this time if possible. No driver issues are showing up in device manger. TCP\IP works pulls an IP address, can surf the netrnet. If I plug it into a workgroup with the same name as the greyed out workgroup name it can access other computers shared files and printers. Just can't change the workgroup or add it to a domain. Any further ideas?

by mex_carnal

Seems to me like you don't have administrator rights to change the domain or workgroup. Use a user that has admin rights.

Good luck,

by pjcannon

User has admin rights but just to be sure I created another administrator account, same problem.

by jacobgin1

As u r able to browse the net and do other things, I dont think its a driver problem. Check the policies. Like Local computer policies and check if any restrictions are set.

by pjcannon

I won't have an opportunity to fix this issues until tommorrow at which time I will post the results & assign points. All the suggestions are appreciated.

by pendal1

I would even consider rebuilding the tcp/ip protocal stack. You probably already know but the comman is netsh int ip reset (file name). I know this has helped me when I run into erratic problems on the network. However, if that doesn't work, I would also think that some policy or service is disabled. And as has been mentioned, a reinstall of the OS may be the only answer in the end.

This discussion is closed to new replies.