- win2k workstation join win2k domain problem
- Posted by brian on January 8th, 2004
I have a win2k server DC.
From the server logged on as administrator I created a
user (user2).
I converted my win2kpro laptop to join my new domain using
the network identification change applet.
I can logon as user2 and administrator.
I went to convert the next win2k workstation in the same
manner. It joined the domain and requested a reboot and
after reboot it will not logon to the domain (over
ethernet)
I enter the user name user2 with the passwped user2 and
select the domain. The computer barks "the local policy of
this system does not permit you to logon interactively".
I cannot logon using administrator either. Same thing.
If I use a bogus name and password the system says the
username and password are incorrect.
I can move my laptop to the workstation's cable and logon
as user2 or administrator.
I cannot even get the workstation to come up to the desktop
Anyone know what I can do to recover this workstation?
brian.harris@network.com
- Posted by Richard McCall [MSFT] on January 8th, 2004
Try adding the workstation to the domain using netdom and then override the
Logon locally user right using a domain policy. if the admin user can now
log in then modify the local security policy so that the log on locally user
right matches the laptop.
"brian" <brian.harris@network.com> wrote in message
news:003e01c3d60c$472aba40$a401280a@phx.gbl...
- Posted by brian on January 8th, 2004
Thanks for the advice.
my user definitions/rights must be working because I can
logon from my laptop using them.
I can see the computer names of my laptop and workstation
in active directory users.
I have attempted to match the properties of the computer
names.
When I boot the workstation I cannot get past the logon
prompt.
If I select the domain it barks the the local policy ETC.
Is this something with the computer definition/settings in
the server or something with the workstation itself?
I can't even get logged on if I select "this computer"
Do I keep playing around with the server or just reload
the op sys on the workstation?
Thanks.
Brian