Discussion Locked

NT Setup

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

In setting up a new NT workstation , Once loading you wire it to the network, and it gets to the point where you tell what domain to go to, well it states unable to reach domain. So you go there anyway and you create a user using administation and it creates it and works. Now when you reboot
and sign on as the user that was created it will not let you install or use admin rights, when you sign in as masteruser on network and add user as administrator it still does not work. tried several times reloading still will not give user admin rights unless i sign in on the domain that is local to the system

9 replies

by bill cassada

If I understand this correctly it sounds as if your computer account is not being added to the domain...this is a known issue. At the workstation remove it from the domain to a workgroup (any name will do). On the server delete any account for thatcomputer name, then recreate it, re-sync the domain, then go back to the workstation and add it back to the domain...at this point you will not need to specify a user with admin rights. Microsoft never explained why this happens...it just does. Wehave a domain with over 400 users...and we experience it frequently. The reason your creation of the user AFTER trying to add the workstation failed has to do with the SID for that workstation. Hope this helps!

by arwjnplanotx

Hi,
You may have already tried this, but I am not sure from the information you gave.
Login locally on the Workstation. Delete the affected user. Logon to a domain controller (PDC or BDC) as administrator. In 'User Manager for Domains' create the user with Domain Admins rights. After that you should be able to log into the Workstation under the user with full admin rights. Local admin rights (Administrators) are only good on the workstation. For network admin right the user must be created in'User Manager for Domains' with domain admin rights.
Hope this helps,
Al

by yuval

Hi,
Just somthing to check on, especially if you are working with DHCP. check that you are connected to the server at the protocol level. try to access some other machine on the network. the same thing you described happened to me today and as I chacked it the DHCP server was down... so here you go. Have a nice day. ;-)

by msauer

Looking at your question, there are some unanswered issues:
Is there a computer account on the domain? This is checked on the server using Server Manager. If not, an admin can create an account through the workstation.
The accounts look like theyare only "workstation local" accounts, and may not be admin, or have admin rights at all. Local workstation admins will be in User Manager, Administrators group.
These above items are needed to gain admin to the workstation locally and network.

This discussion is closed to new replies.