Results 1 to 7 of 7

Thread: RPC Server is Unavailable

  1. #1
    eltonchew@gmail.com Guest

    RPC Server is Unavailable

    Hello community,

    I currently have 2 domains - One and Two. When user from domain One
    trying to RDP into a Terminal server in Domain Two, I received a "RPC
    Server is Unavailable" error. With reference to KB224370
    (http://support.microsoft.com/default...en-us;Q224370), it
    suggest that I may need configure secondary zones on each domain's dns
    server as follow:

    1) Domain One DC1.One.com - Hosts DNS Primary Zone for One.com &
    Secondary Zone for Two.com
    2) Domain Two DC1.Two.com - Hosts DNS Primary Zone for Two.com &
    Secondary Zone for One.com

    Can I check with the community if setting forwarder as follow will
    server the same purpose?

    1) Domain One DC1.One.com - Forwarder set to DC1.Two.com
    2) Domain Two DC1.Two.com - Forwarder set to DC1.One.com

    I have the above configured but it am still getting the same error.

    Anything else i should check?

    Thanks!


  2. #2
    ECEE Guest

    Re: RPC Server is Unavailable

    Sorry - I forget to add. The domains are running in Windows 2000 mode.
    Thanks!


  3. #3
    ECEE Guest

    Re: RPC Server is Unavailable

    And yes - there is a one-way trust established. i.e. Two trust One.
    Thanks!


  4. #4
    Kevin D. Goodknecht Sr. [MVP] Guest

    Re: RPC Server is Unavailable

    eltonchew@gmail.com wrote:
    > Hello community,
    >
    > I currently have 2 domains - One and Two. When user from domain One
    > trying to RDP into a Terminal server in Domain Two, I received a "RPC
    > Server is Unavailable" error. With reference to KB224370
    > (http://support.microsoft.com/default...en-us;Q224370), it
    > suggest that I may need configure secondary zones on each domain's dns
    > server as follow:
    >
    > 1) Domain One DC1.One.com - Hosts DNS Primary Zone for One.com &
    > Secondary Zone for Two.com
    > 2) Domain Two DC1.Two.com - Hosts DNS Primary Zone for Two.com &
    > Secondary Zone for One.com
    >
    > Can I check with the community if setting forwarder as follow will
    > server the same purpose?
    >
    > 1) Domain One DC1.One.com - Forwarder set to DC1.Two.com
    > 2) Domain Two DC1.Two.com - Forwarder set to DC1.One.com
    >
    > I have the above configured but it am still getting the same error.
    >
    > Anything else i should check?


    How exactly are these two domains connected to each other?
    Getting DNS resolution is one thing, having RPC connectivity is another. Use
    Dcdiag from each DC to the other domain, make sure all ports are open
    between the networks if they are on separate networks. NetBIOS resolution is
    going to be a big problem if the DCs are both named DC1.
    Start with this from the two.com DC. dcdiag /n:one.com /e /v You can exclude
    the /e switch if there is only one DC in one.com.


    --
    Best regards,
    Kevin D. Goodknecht Sr. [MVP]
    Hope This Helps
    ===================================
    When responding to posts, please "Reply to Group"
    via your newsreader so that others may learn and
    benefit from your issue, to respond directly to
    me remove the nospam. from my email address.
    ===================================
    http://www.lonestaramerica.com/
    http://support.wftx.us/
    https://secure.lsaol.com/
    ===================================
    Use Outlook Express?... Get OE_Quotefix:
    It will strip signature out and more
    http://home.in.tum.de/~jain/software/oe-quotefix/
    ===================================
    Keep a back up of your OE settings and folders
    with OEBackup:
    http://www.oehelp.com/OEBackup/Default.aspx
    ===================================



  5. #5
    ECEE Guest

    Re: RPC Server is Unavailable

    Hi Kevin, thank you for your reply. I have some answers for your
    questions...

    >>How exactly are these two domains connected to each other?

    The two domains are on seperate network with two firewalls in between,
    each belonging to their respective domain.

    >>Use Dcdiag from each DC to the other domain, make sure all ports are open between the networks if they are on separate networks.

    Unfortunately, we only have access to two.com's domain controllers...
    and the reply from a dc (global catelogue), which looks unpromising, is
    as follow:

    **************************************************************************************************** **********************************************************
    C:\ dcdiag /n:one.com /v
    The distinguished name of the domain is DC=one,DC=com.

    DC Diagnosis

    Performing initial setup:
    Done gathering initial info.

    Doing initial non skippeable tests

    Testing server: AP-SeriaHeadOffice-SERHO\SERHO-S-003
    Starting test: Connectivity
    ......................... SERHO-S-003 passed test Connectivity

    Doing primary tests

    Testing server: AP-HeadOffice-SERHO\SERHO-S-003
    Starting test: Replications
    [SERHO-S-004] DsBind() failed with error 1722,
    The RPC server is unavailable..
    [SERHO-S-002] DsBind() failed with error 1722,
    The RPC server is unavailable..
    [Replications Check,SERHO-S-003]
    DsReplicaGetInfoW(PENDING_OPS) failed with error 8453,
    Replication access was denied..
    ......................... SERHO-S-003 failed test Replications
    Starting test: NCSecDesc
    ......................... SERHO-S-003 passed test NCSecDesc
    Starting test: NetLogons
    [SERHO-S-003] An net use or LsaPolicy operation failed with
    error 64, The specified network name is no longer available..
    ......................... SERHO-S-003 failed test NetLogons
    Starting test: Advertising
    Fatal Error:DsGetDcName (SERHO-S-003) call failed, error 5
    The Locator could not find the server.
    ......................... SERHO-S-003 failed test Advertising
    Starting test: KnowsOfRoleHolders
    [AMSDC1-S-03012] DsBind() failed with error 1722,
    The RPC server is unavailable..
    Warning: AMSDC1-S-03012 is the Schema Owner, but is not
    responding to DS RPC Bind.
    [AMSDC1-S-03012] LDAP connection failed with error 58,
    The specified server cannot perform the requested operation..
    Warning: AMSDC1-S-03012 is the Schema Owner, but is not
    responding to LDAP Bind.
    Warning: AMSDC1-S-03012 is the Domain Owner, but is not
    responding to DS RPC Bind.
    Warning: AMSDC1-S-03012 is the Domain Owner, but is not
    responding to LDAP Bind.
    [CBJ-S-03015] DsBind() failed with error 1722,
    The RPC server is unavailable..
    Warning: CBJ-S-03015 is the PDC Owner, but is not responding
    to DS RPC Bind.
    [CBJ-S-03015] LDAP connection failed with error 58,
    The specified server cannot perform the requested operation..
    Warning: CBJ-S-03015 is the PDC Owner, but is not responding
    to LDAP Bind.
    Warning: CBJ-S-03015 is the Rid Owner, but is not responding
    to DS RPC Bind.
    Warning: CBJ-S-03015 is the Rid Owner, but is not responding
    to LDAP Bind.
    [CBJ-S-03016] DsBind() failed with error 1722,
    The RPC server is unavailable..
    Warning: CBJ-S-03016 is the Infrastructure Update Owner, but
    is not responding to DS RPC Bind.
    [CBJ-S-03016] LDAP connection failed with error 58,
    The specified server cannot perform the requested operation..
    Warning: CBJ-S-03016 is the Infrastructure Update Owner, but
    is not responding to LDAP Bind.
    ......................... SERHO-S-003 failed test
    KnowsOfRoleHolders
    Starting test: RidManager
    [SERHO-S-003] DsBindWithCred() failed with error 1722. The RPC
    server is unavailable.
    ......................... SERHO-S-003 failed test RidManager
    Starting test: MachineAccount
    Could not open pipe with [SERHO-S-003]:failed with 64: The
    specified network name is no longer available.
    Could not get NetBIOSDomainName
    Failed can not test for HOST SPN
    Failed can not test for HOST SPN
    * Missing SPN :(null)
    * Missing SPN :(null)
    ......................... SERHO-S-003 failed test
    MachineAccount
    Starting test: Services
    Could not open Remote ipc to [SERHO-S-003]:failed with 64: The
    specified network name is no longer available.
    ......................... SERHO-S-003 failed test Services
    Starting test: ObjectsReplicated
    ......................... SERHO-S-003 passed test
    ObjectsReplicated
    Starting test: frssysvol
    [SERHO-S-003] An net use or LsaPolicy operation failed with
    error 64, The specified network name is no longer available..
    ......................... SERHO-S-003 failed test frssysvol
    Starting test: kccevent
    Failed to enumerate event log records, error The specified
    network name is no longer available.
    ......................... SERHO-S-003 failed test kccevent
    Starting test: systemlog
    Failed to enumerate event log records, error The specified
    network name is no longer available.
    ......................... SERHO-S-003 failed test systemlog

    Running enterprise tests on : one.com
    Starting test: Intersite
    ......................... one.com passed test Intersite
    Starting test: FsmoCheck
    Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error 5
    A Global Catalog Server could not be located - All GC's are
    down.
    Warning: DcGetDcName(PDC_REQUIRED) call failed, error 5
    A Primary Domain Controller could not be located.
    The server holding the PDC role is down.
    Warning: DcGetDcName(TIME_SERVER) call failed, error 5
    A Time Server could not be located.
    The server holding the PDC role is down.
    Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed,
    error 5
    A Good Time Server could not be located.
    Warning: DcGetDcName(KDC_REQUIRED) call failed, error 5
    A KDC could not be located - All the KDCs are down.
    ......................... one.com failed test FsmoCheck

    **************************************************************************************************** **********************************************************
    >>NetBIOS resolution is going to be a big problem if the DCs are both named DC1.

    The DC1 name were fictitious... they have different names.

    Also, I forgot to mention that when interactively (in from of the
    machine) logging into the Terminal Server using a one.com account, such
    error does not occur.
    I have a strong hunch that this is firewall configuration issue... any
    idea what need to be opened?

    Many Thanks!


  6. #6
    Kevin D. Goodknecht Sr. [MVP] Guest

    Re: RPC Server is Unavailable

    ECEE wrote:
    > I have a strong hunch that this is firewall configuration issue... any
    > idea what need to be opened?


    Yes, your hunch is correct.
    Q179442 - How to Configure a Firewall for Domains and Trusts:
    http://support.microsoft.com/default...;EN-US;Q179442

    --
    Best regards,
    Kevin D. Goodknecht Sr. [MVP]
    Hope This Helps
    ===================================
    When responding to posts, please "Reply to Group"
    via your newsreader so that others may learn and
    benefit from your issue, to respond directly to
    me remove the nospam. from my email address.
    ===================================
    http://www.lonestaramerica.com/
    http://support.wftx.us/
    https://secure.lsaol.com/
    ===================================
    Use Outlook Express?... Get OE_Quotefix:
    It will strip signature out and more
    http://home.in.tum.de/~jain/software/oe-quotefix/
    ===================================
    Keep a back up of your OE settings and folders
    with OEBackup:
    http://www.oehelp.com/OEBackup/Default.aspx
    ===================================



  7. #7
    one3cap Guest

    Re: RPC Server is Unavailable

    i had this same exact problem was not my dns it was the rpc service which has
    alot of dependencies. i had to reboot the server. that fixed it. you cannot
    restart the rpc service because of all the dependencies. well that fixed
    mine. a reboot of the terminal server.

    "ECEE" wrote:

    > Hi Kevin, thank you for your reply. I have some answers for your
    > questions...
    >
    > >>How exactly are these two domains connected to each other?

    > The two domains are on seperate network with two firewalls in between,
    > each belonging to their respective domain.
    >
    > >>Use Dcdiag from each DC to the other domain, make sure all ports are open between the networks if they are on separate networks.

    > Unfortunately, we only have access to two.com's domain controllers...
    > and the reply from a dc (global catelogue), which looks unpromising, is
    > as follow:
    >
    > **************************************************************************************************** **********************************************************
    > C:\ dcdiag /n:one.com /v
    > The distinguished name of the domain is DC=one,DC=com.
    >
    > DC Diagnosis
    >
    > Performing initial setup:
    > Done gathering initial info.
    >
    > Doing initial non skippeable tests
    >
    > Testing server: AP-SeriaHeadOffice-SERHO\SERHO-S-003
    > Starting test: Connectivity
    > ......................... SERHO-S-003 passed test Connectivity
    >
    > Doing primary tests
    >
    > Testing server: AP-HeadOffice-SERHO\SERHO-S-003
    > Starting test: Replications
    > [SERHO-S-004] DsBind() failed with error 1722,
    > The RPC server is unavailable..
    > [SERHO-S-002] DsBind() failed with error 1722,
    > The RPC server is unavailable..
    > [Replications Check,SERHO-S-003]
    > DsReplicaGetInfoW(PENDING_OPS) failed with error 8453,
    > Replication access was denied..
    > ......................... SERHO-S-003 failed test Replications
    > Starting test: NCSecDesc
    > ......................... SERHO-S-003 passed test NCSecDesc
    > Starting test: NetLogons
    > [SERHO-S-003] An net use or LsaPolicy operation failed with
    > error 64, The specified network name is no longer available..
    > ......................... SERHO-S-003 failed test NetLogons
    > Starting test: Advertising
    > Fatal Error:DsGetDcName (SERHO-S-003) call failed, error 5
    > The Locator could not find the server.
    > ......................... SERHO-S-003 failed test Advertising
    > Starting test: KnowsOfRoleHolders
    > [AMSDC1-S-03012] DsBind() failed with error 1722,
    > The RPC server is unavailable..
    > Warning: AMSDC1-S-03012 is the Schema Owner, but is not
    > responding to DS RPC Bind.
    > [AMSDC1-S-03012] LDAP connection failed with error 58,
    > The specified server cannot perform the requested operation..
    > Warning: AMSDC1-S-03012 is the Schema Owner, but is not
    > responding to LDAP Bind.
    > Warning: AMSDC1-S-03012 is the Domain Owner, but is not
    > responding to DS RPC Bind.
    > Warning: AMSDC1-S-03012 is the Domain Owner, but is not
    > responding to LDAP Bind.
    > [CBJ-S-03015] DsBind() failed with error 1722,
    > The RPC server is unavailable..
    > Warning: CBJ-S-03015 is the PDC Owner, but is not responding
    > to DS RPC Bind.
    > [CBJ-S-03015] LDAP connection failed with error 58,
    > The specified server cannot perform the requested operation..
    > Warning: CBJ-S-03015 is the PDC Owner, but is not responding
    > to LDAP Bind.
    > Warning: CBJ-S-03015 is the Rid Owner, but is not responding
    > to DS RPC Bind.
    > Warning: CBJ-S-03015 is the Rid Owner, but is not responding
    > to LDAP Bind.
    > [CBJ-S-03016] DsBind() failed with error 1722,
    > The RPC server is unavailable..
    > Warning: CBJ-S-03016 is the Infrastructure Update Owner, but
    > is not responding to DS RPC Bind.
    > [CBJ-S-03016] LDAP connection failed with error 58,
    > The specified server cannot perform the requested operation..
    > Warning: CBJ-S-03016 is the Infrastructure Update Owner, but
    > is not responding to LDAP Bind.
    > ......................... SERHO-S-003 failed test
    > KnowsOfRoleHolders
    > Starting test: RidManager
    > [SERHO-S-003] DsBindWithCred() failed with error 1722. The RPC
    > server is unavailable.
    > ......................... SERHO-S-003 failed test RidManager
    > Starting test: MachineAccount
    > Could not open pipe with [SERHO-S-003]:failed with 64: The
    > specified network name is no longer available.
    > Could not get NetBIOSDomainName
    > Failed can not test for HOST SPN
    > Failed can not test for HOST SPN
    > * Missing SPN :(null)
    > * Missing SPN :(null)
    > ......................... SERHO-S-003 failed test
    > MachineAccount
    > Starting test: Services
    > Could not open Remote ipc to [SERHO-S-003]:failed with 64: The
    > specified network name is no longer available.
    > ......................... SERHO-S-003 failed test Services
    > Starting test: ObjectsReplicated
    > ......................... SERHO-S-003 passed test
    > ObjectsReplicated
    > Starting test: frssysvol
    > [SERHO-S-003] An net use or LsaPolicy operation failed with
    > error 64, The specified network name is no longer available..
    > ......................... SERHO-S-003 failed test frssysvol
    > Starting test: kccevent
    > Failed to enumerate event log records, error The specified
    > network name is no longer available.
    > ......................... SERHO-S-003 failed test kccevent
    > Starting test: systemlog
    > Failed to enumerate event log records, error The specified
    > network name is no longer available.
    > ......................... SERHO-S-003 failed test systemlog
    >
    > Running enterprise tests on : one.com
    > Starting test: Intersite
    > ......................... one.com passed test Intersite
    > Starting test: FsmoCheck
    > Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error 5
    > A Global Catalog Server could not be located - All GC's are
    > down.
    > Warning: DcGetDcName(PDC_REQUIRED) call failed, error 5
    > A Primary Domain Controller could not be located.
    > The server holding the PDC role is down.
    > Warning: DcGetDcName(TIME_SERVER) call failed, error 5
    > A Time Server could not be located.
    > The server holding the PDC role is down.
    > Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed,
    > error 5
    > A Good Time Server could not be located.
    > Warning: DcGetDcName(KDC_REQUIRED) call failed, error 5
    > A KDC could not be located - All the KDCs are down.
    > ......................... one.com failed test FsmoCheck
    >
    > **************************************************************************************************** **********************************************************
    > >>NetBIOS resolution is going to be a big problem if the DCs are both named DC1.

    > The DC1 name were fictitious... they have different names.
    >
    > Also, I forgot to mention that when interactively (in from of the
    > machine) logging into the Terminal Server using a one.com account, such
    > error does not occur.
    > I have a strong hunch that this is firewall configuration issue... any
    > idea what need to be opened?
    >
    > Many Thanks!
    >
    >


Similar Threads

  1. RPC Server is unavailable
    By Flaco in forum Windows Vista Network
    Replies: 2
    Last Post: 29-01-2008, 06:35 AM
  2. RPC Server is unavailable
    By Paul in forum Vista Help
    Replies: 4
    Last Post: 28-01-2008, 06:27 AM
  3. RPC Server Unavailable (Small Business Server 2003 SP2)
    By Leythos in forum Small Business Server
    Replies: 3
    Last Post: 08-01-2008, 03:14 PM
  4. RPC server is unavailable
    By Bikkelbink in forum Windows Server Help
    Replies: 2
    Last Post: 20-12-2007, 09:03 PM
  5. The RPC server is unavailable.
    By bjude in forum Active Directory
    Replies: 2
    Last Post: 27-03-2005, 07:18 PM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 1,714,104,628.55098 seconds with 17 queries