Point a Window Client or Server to a particular Domain Controller
When troubleshooting domain controller related issues from a client side there are many things that needs to be checked.
Few items that need to checked:
- Review if DCs are hardcoded in the application residing on the client (if application related)
- Ports are opened from the client to the DC
- Check if the DCs in the Sites & Services are the correct ones servicing the site/subnet, and if it communicating properly.
- There are chances that there are new DCs in the environment and the client is not able to talk to them on the requested ports causing delays or timeouts. You may need to switch the domain controller from the client computer to point to an older DC (incase ports were open to it), or the configuration works sporadically.
If you are in any of the above scenarios switching the domain controller has helped me a few times to find out the next steps:
Find Current Domain Controller
You can grab the domain controller that the computer is currently connected to with these steps:
- Select the “Start†button.
- Type “CMD“.
- Hold “Shift†and right-click “Command Prompt“.
- Select “Run as different user“.
- Type credentials for a Domain Admin user account.
- At the Command Prompt, type:
nltest /dsgetdc:domainname
Switch Domain Controller Command
Actually switch the domain controller computer is using with these steps.
- Select the “Start†button.
- Type “CMD“.
- Hold “Shift†and right-click “Command Prompt“.
- Select “Run as different user“.
- Type credentials for a Domain Admin user account.
- At the command prompt, type:
nltest /Server:ClientComputerName /SC_RESET:DomainName\DomainControllerName
[su_note note_color=”#f9f4ca” text_color=”#000000″ radius=”2″]This option is not permanent, as a restart of the computer may grab a different DC.[/su_note]
[su_note note_color=”#f9f4ca” text_color=”#000000″ radius=”2″]/SERVER: is the name of the machine you want to force a connection *from*. e.g client1 /SC_RESET is where you want to force the connection to which is the domain and domain controller in netbios format. e.g. DOMAIN\DC1 Note: this is using the NetBIOS names as opposed to DNS FQDN.[/su_note]
Set Domain Controller Via Registry
- Hold the Windows Key and press “R†to bring up the Windows Run dialog.
- Type “Regedit“, then press “Enter“.
- Navigate to:
- HKEY_LOCAL_MACHINE
- SYSTEM
- CurrentControlSet
- Services
- Netlogon
- Parameters
- Create a String value called “SiteName“, and set it to the domain controller you wish the computer to connect to. (i.e. DC1.domain.com)
- ClientComputerName = Name of the client computer you want to switch domain for.
- DomainName = Name of Domain.
- DomainControllerName = Computer name of domain controller.
Author
Related Posts
Get all the domains controllers in the AD forest along with their current FSMO roles
In a large enterprise an admin would need to keep track of all the domains in a AD forest, the domain names,...
Read out all
Force synchronization for DFSR-replicated SYSVOL
One of my clients had a problem with processing GPO on client computers. Different computers applied different settings from the same GPO...
Get Inactive Users Report for the past 60 days in a multi domain environment
I had a request recently to provide an inactive user report for the past 60 days. Basically, find out which accounts have...
Get Primary, Secondary, Tertiary DNS values and more from Multiple Servers
Came across a unique request to get primary, secondary, and tertiary DNS values for multiple computers/servers across the domain. I started writing...
Fix Active Directory broken security inheritance problem
Ran into a situation at a client location where in Active Directory, the security permissions applied to an OU were not getting...
How to Fix: Attribute userAccountControl of DC is: 0x82020
When running a DCDiag at a customer site today I had the following error occur: [su_box title=”” box_color=”#f3f1cb” title_color=”#000000″ radius=”6″]Warning: Attribute userAccountControl...