Link to home
Start Free TrialLog in
Avatar of Rob Hayes
Rob HayesFlag for United States of America

asked on

Network/internet Slowness since replacing primary domain contoller

I inherited an older Microsoft Server 2008R2 DC running AD/DNS/DHCP taht was converted to a VM.  I was having some issues with it but I was trying to wait until we moved to a new circuit and made some other networking issues.  It crashed.

I built a new DC with 2012R2- I was able to get everything up and running no problems.

That being said have some quirky issues.  There are some people who were experiencing slowness- if I gave them a static ip address slowness went away

I have one server that doesn't seem to resolve to DNS anymore.

i realize that not running dcpromo is not ideal but I did not have an option.  Everything else seems to be ok
Avatar of Will Szymkowski
Will Szymkowski
Flag of Canada image

moved to a new circuit and made some other networking issues.  It crashed.

Did this DC hold any of the roles? if so, you need to make sure that you have seized the roles to the domain controller that is still online. You will also need to setup the new DC as the PDC (external time source provider)

External Time Source - http://blogs.technet.com/b/nepapfe/archive/2013/03/01/it-s-simple-time-configuration-in-active-directory.aspx

You will also need to perform metadata cleanup as well.
Metadata Cleanup
https://technet.microsoft.com/fr-ca/library/cc816907%28v=ws.10%29.aspx?f=255&MSPPError=-2147217396

Also you need to change the DHCP user scopes not to point to the old domain controller for DNS. If you have this entry there this could very well be a reason why your users are getting a delay.

Another very important thing you ensure is that the SRV records for the old DC have been cleaned up. This is the folder under the DNS Zones for domain.com. It is the _msdcs.domain.com folder. In there you will see several folders gc,dc,pdc, etc. You need to go through all of those folders and remove/delete any references that still exists from the old DC. This is also another common reason why users have slowness if SRV records are not cleaned up.

Will.
Avatar of Rob Hayes

ASKER

I am using the same ip address on the rebuilt DC- so since the records refer to ip address the scope options - did not have to change

the DC has a different name though
SOLUTION
Avatar of Hypercat (Deb)
Hypercat (Deb)
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
i have never see that before- can you tell me how that is done?
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Will- I have done all the steps you have suggested except that I cannot delete thee old DC for AD Sites and Services- it keeps giving me an access denied error.

Also I am not sure what you mean about the seize the roles
Avatar of compdigit44
compdigit44

Can you post the results for the following command so we can get an overview of your AD environement

dcdiag /v /e >c:\dcidag.txt
You dcdiag seems ok.

On an affected workstation install Network Monitor or Wireshark and capture traffic while the workstation is using DHCP the upload the results so we can help you review them
Stupid question but DNS is set for Dynamic updates correct???
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Run the command netdom query fsmo

If the command comes back and it is pointing to the old dc then you need to seize the roles on the new dc.

Will.
everything says its good excpet I get
dns.JPG