Ping problems after FSMO roles transfer in windows 2003 R2
Hi everyone, The following is my scenario: I had one DC on windows 2003 R2 and got a new server to be able to install another DC for backup purposes. After installing the OS and DCpromoting it, replication worked great and the 2 servers where working like a charm. As the new DC hardware is much faster than the old one, I decided to transfer all the roles to the new DC. No problems whatsoever. Both DCs are Global Catalogues. The problem is that when I ping my domain (peanut.local), I get a reply from the old DC server IP. Even workstations W32time is syncing with the old DC. How can I get the new DC to be ping when I ping the domain name? Please help Thanks in advance
April 19th, 2011 5:26am

Hello, you can change the weight for DNS SRV records so that your new DC will be the most used one: http://technet.microsoft.com/fr-be/library/cc778225(v=WS.10).aspx This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
Free Windows Admin Tool Kit Click here and download it now
April 19th, 2011 5:33am

Hi, Thanks for your reply. Can you please clarify the following: 1. Do I need to insert the new reg keys on both DCs? 2. How does the weight work? Small number, first to reply? Thanks
April 19th, 2011 6:21am

Lower number of wight imply higher priority to clients attempting to use the mentioned service. You can proceed without registry modifications, just go to the SRV records on your DNS zone and change the weight like you want. This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
Free Windows Admin Tool Kit Click here and download it now
April 19th, 2011 6:46am

Hello, ping domain name is not reliabel and should never be used for connection test, also it is not site aware and a DC from whatver location can answer. What you see is expected an NOT a fault. Do not use it, instead ping the DC direct.Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
April 19th, 2011 6:46am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics