No announcement yet.

RPC Issues Help!!

  • Filter
  • Time
  • Show
Clear All
new posts

  • RPC Issues Help!!

    Were having a few issues with RPC mainly involving KMS and Replication

    to give you a brief description of our network to begin with. We have 3 sites all linked together via local fibre links (not over the internet).
    Site 1 being our main site with 2 x 2008 Domain Controllers one of which the PDC. This site is on VLAN 1. KMS installed here. 172.16 Private Range
    Site 2 being routed to by a 3com 5500G Layer 3 Switch with 1 x 2008 Domain Controller and on VLAN 34 10mbps 192.168.100 range
    Site 3 being routed to by a cisco router 2 x 2003 Domain Controllers VLAN1 100mbps 194 public range(dont ask!)

    All sites gateway to the 3com 5500G and all domain controllers have dns installed(This is what a DC has always asked ot be installed so assume this is correct)

    All DC's can ping each other, file transfer to each other, RDP to each other. These is no firewall between sites

    However if you try and force a replication with sites and services to a DC not at site 1 i.e. when the connection gateways to a different subnet you get a RPC service unavailable error

    Then what has bought this to a head is getting our KMS working(which it is at site 1). We have tested the KMS from site 2 by telling the server where the KMS server is i.e. slmgr -skms activationservernameort or slmgr -skms activationservername. this command returns Error 0x800706BA The RPC server is unavailable. This leads me to believe the same error exists

    Is RPC like DHCP traffic i.e. it doesnt cross a router? Because im really at a loss and MS won't talk to us unless we pay them 200 lol All we want to do is activate our software without calling them

    N.B RPCPing all produces a result

    Any ideas?


  • #2
    Re: RPC Issues Help!!

    Just a bit more info from Windows logs

    Event ID 10009
    DCOM was unable to communicate with the computer -skms using any of the configured protocols.

    The replication issue with RPC in sites and services is only present when using sites and services on Win2k3. On Win2k8 you now get a message saying it will attempt to replicate as they are on different sites


    • #3
      Re: RPC Issues Help!!

      This appears not to be a dcom/rpc error after all

      The slmgr script does not like -skms its passing that as the servername?



      • #4
        Re: RPC Issues Help!!

        Ive solved our problems. It was all to do with a misunderstanding of KMS and the -skms switch not working

        We were using the KMS key on every machine. I didnt realise it was only for the KMS server doh!!!

        Here is an excellent article for anyone else who needs to implement KMS

        Key Management Server (KMS) Fast Activation Walkthrough

        This article deals with procedures that are needed for deploying Volume Activation v2.0.

        Volume Activation v2.0 activates Windows Vista and Windows Server 2008 operating systems for volume licensing customers. You can choose to implement volume activations u
        sing two methods:
        • Key Management Service (KMS) - can be activated in any environment including secured isolated networks.
        • Multiple Activation Key (MAK) - online activation - must have an Internet connection.
        Licensing Keys:
        it's important to understand the differences between the licensing keys, usually these keys can be found under (MVLS) using your account under volume license keys section.
        1. For the KMS server, you'll need one of the followings products keys according to the version installed:

          Windows Server 2008 Std/Ent - KMS
          Windows Srv 2008 Data Ctr/Itan- KMS
          Windows Web Srv 2008-KMS
        2. For KMS clients (actually, all of the other computers) including windows 2008 server and windows vista you'll need one of the corresponding keys as follows:
        3. Windows Vista Business - YFKBB-PQJJV-G996G-VWGXY-2V3X8
          Windows Vista Business N - HMBQG-8H2RH-C77VX-27R82-VMQBT
          Windows Vista Enterprise - VKK3X-68KWM-X2YGT-QR4M6-4BWMV
          Windows Vista Enterprise N - VTC42-BM838-43QHV-84HX6-XJXKV
          Windows Server 2008 Datacenter - 7M67G-PC374-GR742-YH8V4-TCBY3
          Windows Server 2008 Datacenter without Hyper-V - 22XQ2-VRXRG-P8D42-K34TD-G3QQC
          Windows Server 2008 for Itanium-Based Systems - 4DWFP-JF3DJ-B7DTH-78FJB-PDRHK
          Windows Server 2008 Enterprise - YQGMW-MPWTJ-34KDK-48M3W-X4Q6V
          Windows Server 2008 Enterprise without Hyper-V - 39BXF-X8Q23-P2WWT-38T2F-G3FPG
          Windows Server 2008 Standard - TM24T-X9RMF-VWXK6-X8JC9-BFGM2
          Windows Server 2008 Standard without Hyper-V - W7VD6-7JFBR-RX26B-YKQ3Y-6FFFJ
          Windows Web Server 2008 - WYR28-R7TFJ-3X2YQ-YCY4H-M249D

          These keys are static and should be used for any new computer you install, if you download the product from the MVLS site, you do not need to type the key since one of these keys will automatically be used and the machine will be activated if a KMS server exists.
        4. For any computer that is not connected to the network or will not be able to reconnect to the network within 180 days a MAK key is required for activation against the Internet.
        The KMS server can run on either windows 2008, windows vista or windows 2003 with SP1 and later, however installing it on windows 2003 requires you to download the appropriate installation files for KMS v1.1 and described in the next section.
        Installing the KMS server on a Windows Vista or Windows 2008 Server:
        • Important note, whenever a command prompt is needed make sure to run it using the run as administrator option.
        To install the KMS server, type the following at the command prompt:
        cscript C:\windows\system32\slmgr.vbs /ipk <KmsKey> (One of the keys from section one).
        Before you activate the KMS host, consider the following:
        To activate Windows Vista, you must have at least 25 computers running Windows Vista or Windows Server 2008 that are connected together; for Windows Server 2008, the minimum is 5 computers.
        Computers that are activated through KMS must be reactivated every six months by connecting to your organization's network.
        Activating the KMS on windows 2008 server or windows vista:
        1. For online activation, type the following at the command prompt and then press Enter:
          cscript C:\windows\system32\slmgr.vbs /ato
        2. For offline (telephone) activation, type the following at the command prompt:
          slui.exe 4
        the next step is to restart the Software Licensing Service using the following command:
        net stop slsvc && net start slsvc

        Installing the KMS server on a Windows 2003 Server:
        Download Key Management Service for Windows Server 2003 from the Microsoft Download Center at for x86 systems or for x64 systems
        After installing both KMS v1.0 and the patch for v1.1, install the KMS key, type the following at the command prompt, and then press Enter:
        cscript C:\windows\system32\slmgr.vbs /ipk <KmsKey> One of the keys from section one).
        Activating the KMS server on windows 2003 server:
        1. For online activation, type the following at the command prompt and then press Enter:
          cscript C:\windows\system32\slmgr.vbs /ato
        2. For offline (telephone) activation, type the following at the command prompt:
          slui.exe 4 the next step is to restart the Software Licensing Service using the following command:
          net stop slsvc && net start slsvc
        Testing the KMS server configuration:
        The KMS server should publish its SRV records in your domain DNS, it is a good thing to test that these records exists using the following command:
        nslookup -type=srv _vlmcs._tcp
        you should see something similar to that: SRV service location:
        priority = 0
        weight = 0
        port = 1688
        svr hostname = internet address = x.x.x.x
        Please note that the KMS server listens on port TCP 1688, if you need to activate KMS client over a firewall, make sure to open this port as necessary.
        now, just try to activate manually one of your clients or servers using the following command:
        cscript C:\windows\system32\slmgr.vbs /ato
        If you need to activate a client in an isolated network, you can assign it the KMS server's static IP address instead of using DNS using the following command:
        slmgr -skms kms-ip-address
        After that, don't forget to run the activation command:
        cscript C:\windows\system32\slmgr.vbs /ato
        Basically, any client will try to activate itself every 120 minutes by default, so there is no need to run the acivation command manually.
        Hope this helps, if you have any comments I'd like to hear about it.


        • #5
          Re: RPC Issues Help!!

          Thanks for Sharing!!
          It's great you find the solution
          Technical Consultant

          MCITP(EA, SA), MCSA/E 2003:Security, CCNA, SNAF, DCUCI, CCSA/E/E+ (R60), VCP4/5, NCDA, NCIE - SAN, NCIE - BR, EMCPE
          "No matter how secure, there is always the human factor."

          "Enjoy life today, tomorrow may never come."
          "If you're going through hell, keep going. ~Winston Churchill"