Unable to get to Network Identification Wizard or change domain name in Windows XP

preslove

Lifer
Sep 10, 2003
16,754
64
91
I just started my first tech support gig as a graduate assistant. I was just given a problem to fix that's been stumping the more established employees here:

We need to get to the Network Identification Wizard on the computers in a lab here, but;
1). Even logged in as administratror they don't show "properties" when you right click on MyComputer. 2). System in Control Panel will not open. 3). Going into Computer Management and going to computer management properties allows me to see the Computer Name, but doesn't show Network Identification Wizard or Change Domain name.

I'm logged in as Administrator, but can't seem to get it.

Any help would be much appreciated.
 

mrbill14

Member
Jan 16, 2003
97
0
0
Just a few thoughts:

Are these computers on a domain?

Are they connected to the LAN? Valid IP address?

Sounds like you have some policies going on.... hiding some of these options. Either that, or you're running XP Home (instead of Pro).

Reply back...
 

preslove

Lifer
Sep 10, 2003
16,754
64
91
Originally posted by: mrbill14
Just a few thoughts:

Are these computers on a domain?

Yep
Are they connected to the LAN? Valid IP address?
Yep
Sounds like you have some policies going on.... hiding some of these options.
Yeah, that's what I'm thinking. I just don't know how to get at these policies.

Either that, or you're running XP Home (instead of Pro).
Nope, they're all running XP Pro.

Reply back...

I'll be here to 5:00 EST :)
 

GreyMittens

Member
Nov 1, 2005
174
0
0
It does sound like some policies are being shoved down the clients throat. Do all computers in the lab behave like this? Check group policy management on the lab dc and see if it is the cause.

You could also try forcing the client to join the domain using NETDOM (should be part of the support tools on the server CD iirc)

 

TG2

Banned
Nov 14, 2005
774
0
0
Try runing GPResult from a command line to see what group policies are being pushed to the client.
Sounds like the local admin account isnt allowed access to some stuff