Hi,sir i hav wind server 2003 ,there is active directory ,i hav a domain name ,but right now i do,t hav any user connected with domain ,i want to connect some user with domain,i tried , like i changed the pc from ,workgroup to domain ,i gave the domain name which is existing in the server ,but the error is (the domain controller for the domain ........(my domain name) could not be connected ,ecsure that domain name is typed correctly) while i m sure the domain name is correct,
what could be a problem ,plz help me
,thanks and regards,
An expert who has achieved level 2 by getting 100 points
An expert who has answered 20 questions.
An expert that has over 10 points.
An expert whose answer got voted for 2 times.
Re: user creating in domain
In active directory on the server you need to create a network admin user and any other normal users u want to have access to the domain. Then you have to add the pc to the domain using the network admin user. After this u can log on to the pc with the network admin or the other created user names.
- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
Hello Mr. Ali. I've been recently admitted to this Win Server 2008 R2 course. I had a class related to your problem, so I believe that I may help you solve this problem.
Click Start, point to Administrative Tools and then click Active Directory Users and Computers. Goto the properties of your created Domain Controller and scroll down to find this function "DSMmachineAccount", click to to change the value to Zero.
A Microsoft Windows Active Directory Domain is a directory service for a computer network. Think of it like a phonebook for all your companies computers, users, and printers to name a few. Active Directory provides a central authentication point for all users/computers in the building and controls network policies. This makes network management for multiple computers and users MUCH easier.
The resolution and workaround to solve the error is as below.
Login to the Windows 2003 domain controller, and delete the computer account object from the Active Directory by using Microsoft Management Console (MMC) which you can always access from “Manage Your Server”.
Log-in to the PC workstation as local administrator. If you cannot logon as local administrator, try to unplug the network cable and logon to the computer by using a domain administrator user that used to logon on the PC before, by using cached logon credentials feature.
Go to Control Panel, then click on System icon, then go to Computer Name tab.
Unjoin the computer from the domain by clicking on “Change”. You should see that Domain button is now selected. Remember your domain name in the text box. Select (Click) on “Workgroup” to remove the computer from the domain, and put any workgroup name in the text box (e.g. workgroup).
Click OK to exit.
Restart the computer (optional)
Go back to the Control Panel, launch System properties and then go to Computer Name tab, and click on “Change”.
Rejoin the domain by uncheck the Workgroup button and select (check) Domain button, and put in the domain name noted above into the text box.
Click OK to exit.
Reboot the PC.
This should solve the unable to logon to domain error, without changing or losing the user profiles on AD.
DNS is the primary name resolution service for Windows Server 2003. Active Directory depends on DNS for domain controller location, and DNS influences Active Directory domain naming. Thus, to fully understand Active Directory, it helps to understand how DNS acts as an integral component in the design of Active Directory.
DNS provides Active Directory with both a name resolution service for domain controller location and a hierarchical design that Active Directory leverages to provide a naming convention that can reflect organizational structure.
Typically, a DNS domain namespace deployed to accommodate the Active Directory mirrors the Active Directory domain namespace. In cases where there is an existing DNS namespace prior to Active Directory deployment, the DNS namespace is typically partitioned for Active Directory, and a DNS subdomain and delegation for the Active Directory forest root is created. Additional DNS domain names are then added for each Active Directory child domain.
DNS data is used to support the location of Active Directory domain controllers also. During or after the creation of the DNS zones used to support Active Directory domains, the zones are populated with DNS resource records that enable network hosts and services to locate Active Directory domain controllers.
Active Directory think of it has management system for all network LAN PCs in your domain. You can add users to certain enterprise groups, you can disable accounts, push and pull software application better then you can in SMS domain. I use to to clone user accounts or create new user groups. Very easy to learn. To install on Server requires a domain, DNS. If you're using Windows Server 2003 and setup the server to manage active directory all the options for the installation process will appear for installation. There are a lot of info online and in books if you need more info. There are training classing offer at MS Solutions Centers.
Active Directory (AD) is a technology created by Microsoft that provides a variety of network services,
Active directory is a directory service used to store information about the network resources across a domain and also centralize the network.
DNS stands for Domain Name Server. These are the servers that match up a fully qualified domain with the proper IP address. This is necessary because computers only understand the IP address for your domain (eg- 123.45.678.90).
An application directory partition is represented by a domainDNS object with an instanceType attribute value of DS_INSTANCETYPE_IS_NC_HEAD combined with DS_INSTANCETYPE_NC_IS_WRITEABLE. This domainDNS object represents the application directory partition root (NC head), and is named similar to a regular domain partition, for example, "DC=dynamicdata,DC=fabrikam,DC=com", which corresponds to a DNS name of "dynamicdata.fabrikam.com". An application directory partition can, therefore, be instantiated anywhere a domain partition can be instantiated. There is no NetBIOS name associated with an application directory partition.
It is possible to nest application directory partitions, that is, an application directory partition can have child application directory partitions. Searches with subtree scope rooted at an application directory partition head will generate continuation references to the child application directory partitions.
An application directory partition replica can only be created on a domain controller that is running on Windows Server 2003 and later and only while the Domain-Naming FSMO role is held by a Windows Server 2003 and later domain controller. In a mixed forest that has both Windows Server 2003 domain controllers and down-level domain controllers (Windows 2000 domain controllers or Windows NT 4.0 primary domain controllers), an attempt to create an application directory partition replica on a down-level domain controller will fail.
An application directory partition also has a corresponding crossRef object in the Partitions container of the configuration partition. The crossRef can be pre-created manually before creating the domainDNS object. The pre-created crossRef object must have the attribute values shown in the following table or the partition creation will fail. If the crossRef object does not exist, the Active Directory server will create one when the application directory partition is created.