Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 30
  • Last Modified:

RPC issues with new domain controllers

We recently built new 2008r2 DC's and everything went smoothly,  till we shutdown our old 2003 DC as a test.  When the 2003 DC is up we everything works fine, however when powered off we get rpc server cannot be found.  I need free up this box but cannot figure out what is on that 2003 DC thats causing the issue.  Any ideas?
0
LS_Acadia
Asked:
LS_Acadia
  • 2
  • 2
1 Solution
 
nwgservicesCommented:
Hello LS Acadia,

Here is a basic How-To.

Have you transferred FSMO roles ?

Regards,

NWGServices
0
 
MuraliCommented:
Hi, Did you transferred all the roles to new DC?
0
 
LS_AcadiaAuthor Commented:
Yes we have transfered all of the FSMO roles to the new 2008 DC
0
 
MuraliCommented:
Just check all FSMO roles are hosted in new DC..

http://www.petri.co.il/determining_fsmo_role_holders.htm

make sure that your client DNS settings are pointing to new DC properly...

At the client end... open command prompt... execute SET command... check whats the 'logonserver'? is it ur new DC?
0
 
LS_AcadiaAuthor Commented:
We figured it out, we changed the SRV weight/priority to allow the other DC's to respond first.
0

Featured Post

Free learning courses: Active Directory Deep Dive

Get a firm grasp on your IT environment when you learn Active Directory best practices with Veeam! Watch all, or choose any amount, of this three-part webinar series to improve your skills. From the basics to virtualization and backup, we got you covered.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now