Can't transfer master roles from 2003 to SBS 2003 - RPC server unavailable

Posted on 2009-04-18
Last Modified: 2012-05-06
I thought I was on the home stretch bringing my 2003 SBS server back into my existing domain but after transferring the master roles FSMO to the SBS 2003 server, the Continue Installation process claims that it does not have all the master roles.  I don't want to seize the role because I need the other server to stay in production.  Netdom query fsmo on the SBS server gives RPC server is unavailable.  Netdom from the 2003 give incorrect parameter.. :|  When I try to connect with NTDSUTIL to the SBS server from the 2003 Enterprise server, it errors out with an RPC error: DsBindW error 0x6ba(The RPC server is unavailable.)  I've started the RPC services but that didn't help.  DNS is installed on both servers and both servers are currently pointing to the SBS server.  Any ideas?
Question by:jhuntii
    LVL 6

    Accepted Solution

    You have some issues with either DNS or ports
    To check DNS, make sure you have secondary zones on both sides for each other
    Also, make sure ports required for AD are open
    Following ports should be open
    DNS 53 tcp udp
    WINS 42
    LDAP 389
    GC 3268 3269
    RPC 135
    Download the port query (portqryui) from Microsoft website to check if required ports are open or not
    In portqry, you have to enter IP/name of target DC and check the ports, If any of these ports are not listening or filetered, you have the number
    Make sure these ports are open on router/firewall

    Hardeep Saluja

    Author Comment

    Thank you very much.  It looks like Windows Firewall was on and was blocking RPC.  I just turned it off for now and am able to connect from the 2003 Ent to the SBS with ntdsutil !!! :)  However, events now show a schema mismatch.  I'm planning to tranfer all roles back to the 2003 server, may even remove AD for the SBS, then bring it back in again...

    Author Comment

    Actually, the swing migration told me to transfer the roles and then reboot - which I did.  What I did not do was to wait until the roles had syncronized before rebooting.  I ended going back and rebuilding the new server and this time when I transfered the roles, they came across just fine - then I rebooted and the rest went OK.  Thanks.

    Author Closing Comment

    Thanks for your quick response and for the info on the ports.

    Featured Post

    Looking for New Ways to Advertise?

    Engage with tech pros in our community with native advertising, as a Vendor Expert, and more.

    Join & Write a Comment

    Do you have users whose passwords are expiring and they are constantly calling you?  Well I sure did and needed a way to put an end to this.  We have a lot of remote users which would not be notified that their passwords were expiring since they wer…
    Find out how to use Active Directory data for email signature management in Microsoft Exchange and Office 365.
    This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
    This tutorial will walk an individual through the process of configuring their Windows Server 2012 domain controller to synchronize its time with a trusted, external resource. Use Google, Bing, or other preferred search engine to locate trusted NTP …

    733 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    17 Experts available now in Live!

    Get 1:1 Help Now