Domain controller is down or otherwise unavailable.
After replication server to the Headquarter company.My company user unable login to their user profile and come out the message "the domain controller is down or otherwise unavailable or the computer account was not found,Please try again later"Even my HeadQuarter office also facing the same problem.But the problem occur on certain user very oftenly.After i put back to workgroup and rejoin domain,the user can login again.but after shutdown the pc.They unable to login again.
a 6ya expert can help you resolve that issue over the phone in a minute or two.
best thing about this new service is that you are never placed on hold and get to talk to real repairmen in the US.
the service is completely free and covers almost anything you can think of (from cars to computers, handyman, and even drones).
click here to download the app (for users in the US for now) and get all the help you need. goodluck!
- 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.
It sounds like you might be dealing with 2 issues here.
When you setup a one way trust they are non-transitive. What this means is one of the domains (say A) is the Trusting domain and the other (B) is the Trusted domain. If you are familiar with the graphic presentations of trust relationships think of 2 circles, one labeled A and the other B. There would be an arrow pointing towards domain B from domain A. Users in B can use resources in A. Users in A cannot access resources in B. Global groups from B can be used in A, but not vice versa. Domain B will appear in the login box in the A computers, but Domain A will not appear in the Domain B login screen.Users and groups in a trusting domain cannot be assigned permissions, rights, or access to a trusted domain. If you want all users to be able to use resources in all domains then you would have to setup 2 way Trust Relationships.
The issue that you are having with users having to relogin may be tied to a domain server not copying down login information to all other servers on the network. Make sure that all of your primary domain servers are setup to speak to all of your other primary and secondary domain servers.
This is usually a computer trust issue, if the computer was previously used to logon to the network and has been rebuilt or had in problems it can have trust issues. First way would be to change the computer name and add the DNS Prefix for your domain. ex desktop.abc.com to desktop1.abc.com. when prompted it is best to use the domain admin or equivalent to make the change and then reboot.
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.
When you install a server operating system at that time it will ask you that how many maximum clients you want to attach this server so by default its 10 ,that means you can attach maximum of 10 clients , you can increase or decrease the no of computer you want.
Firstly you have to decide whether to add clients in workgroup mode or Domin mode..in domain mode you have the centralised management on the computer .so select domain level mode . now to make clients either you can make 5 user in active directory user and computer. 1:Go to Administrative tools > Select Active Directory Users and computers > Select user on the left side > right click on that and select new user > now follow on screen instruction to make a user > now make other 4 user also in the same mannner.Now when you are logged on with local user on the clients select my computer > right click and Select properties > select my computer tab >now click change button to make client work with domain type only domain name for eg if your domain is contoso.com ,> type their only contoso > now a box will appear asking you for administrator and password enter domain controller pc password ,it will ask you to restart > after restart user can login at the client computer... Or: just login with local user at client computer Right click my computer > and do the same procedure ,after restarting you can login with your server name administrator and password . --------------------------------------------------------------------------------------------- If this answers your question please rate this as fixed. If you need more help just add a comment and I'll be glad to help you further ---------------------------------------THANKS ----------------------------------------
Make sure and keep copies of all the folders and files.
Take these actions to resolve your problem:
On all Active Directory registered domain controllers:
1. Stop NETLOGON Service
2. Stop File Replication Service (NTFRS)
On the PDC Emulator:
1. Rename all files in the %systemroot%\ntfrs folder and subfolders (change their extension to .old).
2. Give an unlisted account full control of the directory %systemroot%\SYSVOL folder and reset permissions on all child objects.
3. Change the registry key: HKLM\System\CurrentControlSet\Services\ntfrs\paramaters\Backup/Restore\Process at Startup\BurFlags (REG_DWORD) = D4 (The default on this is 0)
4. Start the NETLOGON Service
5. Start the NTFRS Service
On all non-PDC emulators:
1. Change the registry key: HKLM\System\CurrentControlSet\Services\ntfrs\paramaters\Backup/Restore\Process at Startup\BurFlags (REG_DWORD) = D2
2. Start the NETLOGON Service
3. Start the File Replication Service (NTFRS)
At this point, the system in question should have recreated the SYSVOL share and the NETLOGON share. Check this by running 'net share' from a command prompt. You should also see the Group Policy Objects listed in the SYSVOL directory as:
There may be more directories listed here, but these are the Default Domain Policy and the Default Domain Controllers Policy that are installed by default when the Active Directory is created. If these are being replicated, then file replication is functioning.
If you cannot find these directories, then you may have to manually recreate them. Here is a list of the proper directory structure of the %systemroot%\SYSVOL folder:
\SYSVOL ________\domain ________________\DO_NOT_REMOVE_NtFrs_PreInstall_Directory ________________\Policies ________________\Scripts ________\scripts ________\staging ________\staging areas ________________\domain_name ________\sysvol (shared as SYSVOL) ________________\domain_name ________________________\DO_NOT_REMOVE_NtFrs_PreInstall_Directory ________________________\Policies ________________________\Scripts (shared as NETLOGON)
If you have to manually recreate the directories, restart the File Replication Service (NTFRS) on all domain controllers to re-enable replication. This should get the file replication functioning normally
You need to either use a Domain Account if you are using Windows authentication or you need to use SQL server authentication. The reason for this is because the user account that you are using only exists on the machine that you are on not on the machine that you will be replicating to.