none
Windows 7 Error: 1722 The RPC - Server is unavailable.

    Question

  • Hello

    I have a Problem with my Windows 7 machines (x86 etc x64). Each User have logonscript (standart Batch Datei), which starts with logging. Each machine is in the domain and bekomes the IP with DHCP. The DC Server are Windows 2008 R2 Server. After logging on, the users with Windows 7 machines bekomes next error: "Error: 1722 The RPC - Server is unavaible."

    At first I thought, that this is the problem with Firewall (I have Symantec Endpoint Protection on each Machine), because of that I've do three things:

    1) Uninstalled Symantec.

    2) deaktivated Windows Firewall.

    Result after 1 and 2: The Error comes again.

    3) Then I tried to find, with wich Process can be something wrong. I've started DHCP - Client and it work without Problem.

    Result after 3 without 1 and 2: It works. It works with Firewall too.

    Can anybody explain me, how can I solve this problem?

    Regards




    • Edited by koozyy Tuesday, November 13, 2012 1:38 PM
    Tuesday, November 13, 2012 1:20 PM

Answers

  • Hi,

    Regarding the current issue, the following article may be helpful.

    Troubleshooting "The RPC server is unavailable"

    http://social.technet.microsoft.com/wiki/contents/articles/4494.troubleshooting-the-rpc-server-is-unavailable.aspx

    Please try to troubleshoot the issue with the methods mentioned in the above article.

    Best Regards,

    Andy Qi

    Wednesday, November 14, 2012 10:31 AM
    Moderator
  • Hallo Guys

    VenkatSP and Andy Qi were right: It is an DNS problem. We have found, that our firewall make DHCP too. Because of that the machines had  becomes bad IP's. Later we shall look, what is the problem with firewall. (I am working at this place not so long, and I must check the network, that was configured before me.)
    With dcdiag command we have localised our problem. (Thank you Andy Qi)  

    Now some of PC's (with Win 7) works with fixed IP's fine. And it comes to Problem no more. (Ofcourse it is the temporal solution) After the solving the problem with firewall, we shall give to PC's the IP's automatically.

    Thank you all.


    ..................

    Tuesday, November 20, 2012 8:52 AM

All replies

  • Hi,

    Regarding the current issue, the following article may be helpful.

    Troubleshooting "The RPC server is unavailable"

    http://social.technet.microsoft.com/wiki/contents/articles/4494.troubleshooting-the-rpc-server-is-unavailable.aspx

    Please try to troubleshoot the issue with the methods mentioned in the above article.

    Best Regards,

    Andy Qi

    Wednesday, November 14, 2012 10:31 AM
    Moderator
  • If I understand you correctly the DHCP service is stopped and when you start it you can communicate with your DC.  If that is what you are saying then yes what you are experiencing is as expected.  The machine needs an ip address which is provided by the DHCP service.

    Am I misunderstanding your problem?

    --
    Paul Bergson
    MVP - Directory Services
    MCITP: Enterprise Administrator
    MCTS, MCT, MCSE, MCSA, Security+, BS CSci
    2008, Vista, 2003, 2000 (Early Achiever), NT4
    http://www.pbbergs.com    Twitter @pbbergs
    http://blogs.dirteam.com/blogs/paulbergson

    Please no e-mails, any questions should be posted in the NewsGroup. This posting is provided "AS IS" with no warranties, and confers no rights.

    Wednesday, November 14, 2012 1:09 PM
    Moderator
  • Hi pbbergs

    Ofcourse the DHCP Client working all the time. The Problem is, that I need to start DHCP Client every time, after machine goes up, if I want my logonskript to work correctly.

    Regards


    • Edited by koozyy Wednesday, November 14, 2012 1:13 PM
    Wednesday, November 14, 2012 1:13 PM
  • I have done the next Test: DCDIAG /TEST:DNS /V /E /F:<filename.log>

    Hier comes Warning on the AGJADS02: no DNS RPC connectivity (error or non Microsoft DNS server is running)

    TCP/IP NetBios Helper, DHCP - Client, RPC are running.

    What can I do to become DNS RPC connectivity?

    DCDIAGLOG.TXT

    Domain Controller Diagnosis

    Performing initial setup:
       * Verifying that the local machine SERVER01, is a DC.
       * Connecting to directory service on server SERVER01.
       * Collecting site info.
       * Identifying all servers.
       * Identifying all NC cross-refs.
       * Found 2 DC(s). Testing 2 of them.
       Done gathering initial info.

    Doing initial required tests
       
       Testing server: Freiburg\SERVER01
          Starting test: Connectivity
             * Active Directory LDAP Services Check
             * Active Directory RPC Services Check
             ......................... SERVER01 passed test Connectivity
       
       Testing server: Freiburg\SERVER02
          Starting test: Connectivity
             * Active Directory LDAP Services Check
             * Active Directory RPC Services Check
             ......................... SERVER02 passed test Connectivity

    Doing primary tests
       
       Testing server: Freiburg\SERVER01
          Test omitted by user request: Replications
          Test omitted by user request: Topology
          Test omitted by user request: CutoffServers
          Test omitted by user request: NCSecDesc
          Test omitted by user request: NetLogons
          Test omitted by user request: Advertising
          Test omitted by user request: KnowsOfRoleHolders
          Test omitted by user request: RidManager
          Test omitted by user request: MachineAccount
          Test omitted by user request: Services
          Test omitted by user request: OutboundSecureChannels
          Test omitted by user request: ObjectsReplicated
          Test omitted by user request: frssysvol
          Test omitted by user request: frsevent
          Test omitted by user request: kccevent
          Test omitted by user request: systemlog
          Test omitted by user request: VerifyReplicas
          Test omitted by user request: VerifyReferences
          Test omitted by user request: VerifyEnterpriseReferences
          Test omitted by user request: CheckSecurityError
       
       Testing server: Freiburg\SERVER02
          Test omitted by user request: Replications
          Test omitted by user request: Topology
          Test omitted by user request: CutoffServers
          Test omitted by user request: NCSecDesc
          Test omitted by user request: NetLogons
          Test omitted by user request: Advertising
          Test omitted by user request: KnowsOfRoleHolders
          Test omitted by user request: RidManager
          Test omitted by user request: MachineAccount
          Test omitted by user request: Services
          Test omitted by user request: OutboundSecureChannels
          Test omitted by user request: ObjectsReplicated
          Test omitted by user request: frssysvol
          Test omitted by user request: frsevent
          Test omitted by user request: kccevent
          Test omitted by user request: systemlog
          Test omitted by user request: VerifyReplicas
          Test omitted by user request: VerifyReferences
          Test omitted by user request: VerifyEnterpriseReferences
          Test omitted by user request: CheckSecurityError
       
       Running partition tests on : DomainDnsZones
          Test omitted by user request: CrossRefValidation
          Test omitted by user request: CheckSDRefDom
       
       Running partition tests on : ForestDnsZones
          Test omitted by user request: CrossRefValidation
          Test omitted by user request: CheckSDRefDom
       
       Running partition tests on : Schema
          Test omitted by user request: CrossRefValidation
          Test omitted by user request: CheckSDRefDom
       
       Running partition tests on : Configuration
          Test omitted by user request: CrossRefValidation
          Test omitted by user request: CheckSDRefDom
       
       Running partition tests on : agjfr
          Test omitted by user request: CrossRefValidation
          Test omitted by user request: CheckSDRefDom
       
       Running enterprise tests on : mydom.com
          Test omitted by user request: Intersite
          Test omitted by user request: FsmoCheck
          Starting test: DNS
             Test results for domain controllers:
                
                DC: SERVER02.mydom.com
                Domain: mydom.com

                      
                   TEST: Authentication (Auth)
                      Authentication test: Successfully completed
                      
                   TEST: Basic (Basc)
                       Microsoft Windows Server 2008 R2 Standard  (Service Pack level: 1.0) is supported
                      NETLOGON service is running
                      kdc service is running
                      DNSCACHE service is running
                      DNS service is running
                      DC is a DNS server
                      Network adapters information:
                      Adapter [00000010] Citrix PV Ethernet Adapter:
                         MAC address is 32:53:72:AE:43:1D
                         IP address is static
                         IP address: 192.168.10.26, fe80::ddd4:ea80:e441:f39b
                         DNS servers:
                            192.168.10.25 (<name unavailable>) [Valid]
                            127.0.0.1 (<name unavailable>) [Valid]
                            192.168.10.26 (<name unavailable>) [Valid]
                            Warning: 192.168.10.10 (<name unavailable>) [Invalid]
                      The A record for this DC was found
                      The SOA record for the Active Directory zone was found
                      Warning: no DNS RPC connectivity (error or non Microsoft DNS server is running)
                      [Error details: 5 (Type: Win32 - Description: Zugriff verweigert)]
             
                
                DC: SERVER01.mydom.com
                Domain: mydom.com

                      
                   TEST: Authentication (Auth)
                      Authentication test: Successfully completed
                      
                   TEST: Basic (Basc)
                       Microsoft Windows Server 2008 R2 Standard  (Service Pack level: 1.0) is supported
                      NETLOGON service is running
                      kdc service is running
                      DNSCACHE service is running
                      DNS service is running
                      DC is a DNS server
                      Network adapters information:
                      Adapter [00000010] Citrix PV Ethernet Adapter:
                         MAC address is D6:3F:17:AB:4B:73
                         IP address is static
                         IP address: 192.168.10.25, fe80::1527:1f78:e3de:b148
                         DNS servers:
                            192.168.10.26 (<name unavailable>) [Valid]
                            127.0.0.1 (<name unavailable>) [Valid]
                            192.168.10.25 (<name unavailable>) [Valid]
                            Warning: 192.168.10.10 (<name unavailable>) [Invalid]
                      The A record for this DC was found
                      The SOA record for the Active Directory zone was found
                      The Active Directory zone on this DC/DNS server was found (primary)
                      Root zone on this DC/DNS server was not found
                      
                   TEST: Forwarders/Root hints (Forw)
                      Recursion is enabled
                      Forwarders Information:
                         10.190.13.1 (<name unavailable>) [Valid]
                         192.168.10.10 (<name unavailable>) [Invalid]
                         192.168.10.254 (<name unavailable>) [Invalid]
                         192.168.10.26 (<name unavailable>) [Valid]
                      
                   TEST: Delegations (Del)
                      No delegations were found in this zone on this DNS server
                      
                   TEST: Dynamic update (Dyn)
                      Warning: Dynamic update is enabled on the zone but not secure mydom.com.
                      Test record _dcdiag_test_record added successfully in zone mydom.com.
                      Test record _dcdiag_test_record deleted successfully in zone mydom.com.
                   
                TEST: Records registration (RReg)
                   Error: Record registrations cannot be found for all the network adapters
             
             Summary of test results for DNS servers used by the above domain controllers:

                DNS server: 192.168.10.10 (<name unavailable>)
                   3 test failures on this DNS server
                   This is a valid DNS server.
                   Name resolution is not functional. _ldap._tcp.mydom.com. failed on the DNS server 192.168.10.10
                   [Error details: 9003 (Type: Win32 - Description: Der DNS-Name ist nicht vorhanden.)]
                   
                DNS server: 192.168.10.254 (<name unavailable>)
                   1 test failure on this DNS server
                   This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 192.168.10.254
                   [Error details: 9002 (Type: Win32 - Description: DNS-Serverfehler.)]
                   
                DNS server: 10.190.13.1 (<name unavailable>)
                   All tests passed on this DNS server
                   This is a valid DNS server.
                   
                DNS server: 192.168.10.25 (<name unavailable>)
                   All tests passed on this DNS server
                   This is a valid DNS server.
                   Name resolution is funtional. _ldap._tcp SRV record for the forest root domain is registered
                   
                DNS server: 192.168.10.26 (<name unavailable>)
                   All tests passed on this DNS server
                   This is a valid DNS server.
                   Name resolution is funtional. _ldap._tcp SRV record for the forest root domain is registered
                   
             Summary of DNS test results:
             
                                                Auth Basc Forw Del  Dyn  RReg Ext  
                   ________________________________________________________________
                Domain: mydom.com
                   SERVER02                     PASS WARN n/a  n/a  n/a  n/a  n/a  
                   SERVER01                     PASS WARN PASS PASS WARN FAIL n/a  
             
             ......................... mydom.com failed test DNS


    • Edited by koozyy Friday, November 16, 2012 9:01 AM
    Thursday, November 15, 2012 10:08 AM
  • First of all, we can try to configure the Fast Logon setting by GPO to check the result:

    Computer configuration\Administrative Templates\System\Logon\Always wait for the network at computer startup and logon.

    Enable this policy, check what the result is.

    See this hotfix too.http://support.microsoft.com/kb/2550944/en-us

    If till the issue persist please post the ipconfig /all details of client PC and event log error message too.


    Best Regards,

    Sandesh Dubey.

    MCSE|MCSA:Messaging|MCTS|MCITP:Enterprise Adminitrator | My Blog

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Sunday, November 18, 2012 12:47 AM
  • Hi,

    I agree with Andy and suggest you to follow the article from his discussion. However after looking at DCDiag log from your comments, I would like to see ipconfig /all from both the DCs. I doubt that it is a DNS misconfig issue. Please post ipconfig /all log.

    I see IPv6 is configured in the DCs, please make it automatic for preferred DNS (on NIC properties select IPv6 and properties and ADV DNS tab).

    Sunday, November 18, 2012 7:39 AM
  • Hallo Guys

    VenkatSP and Andy Qi were right: It is an DNS problem. We have found, that our firewall make DHCP too. Because of that the machines had  becomes bad IP's. Later we shall look, what is the problem with firewall. (I am working at this place not so long, and I must check the network, that was configured before me.)
    With dcdiag command we have localised our problem. (Thank you Andy Qi)  

    Now some of PC's (with Win 7) works with fixed IP's fine. And it comes to Problem no more. (Ofcourse it is the temporal solution) After the solving the problem with firewall, we shall give to PC's the IP's automatically.

    Thank you all.


    ..................

    Tuesday, November 20, 2012 8:52 AM