Group Policy Results Wizard

Discussion in 'Windows Small Business Server' started by Robert Byrne, Aug 10, 2006.

  1. Robert Byrne

    Robert Byrne Guest

    I'm having difficulty running the Group Policy Results Wizards from the
    server to an interal Workstation. I receive the following error:

    Failed to connect OCG\workstation1 due the error listed below. Ensure that
    the Windows Management Instrumentation [WMI] service is enabled on the
    target computer, and consult the event log of the target computer for
    further details.

    The RPC server is unavailable.

    Research online indicates it can be a Windows Firewall issue. I have
    disabled the firewall on the client machine. However, I still receive this
    error. Could the ISA server be blocking the traffic? I ran a query from
    the ISA while attempting the connection. I receive the following entries:

    10.8.9.1 ODYSSEY2006 - TCP - No - 19488 0 0 0 0x0 0x0 0x0
    Firewall 8/10/2006 12:27:06 PM 10.8.9.17 135 RPC (all interfaces) Initiated
    Connection Allow RPC from ISA Server to trusted servers 10.8.9.1 - Local
    Host Internal -
    10.8.9.17 ODYSSEY2006 - TCP - No - 1265 0 0 0 0x0 0x0 0x0
    Firewall 8/10/2006 12:27:06 PM 10.8.9.1 135 RPC (all interfaces) Initiated
    Connection SBS Protected Networks Access Rule 10.8.9.17 - Internal Local
    Host -
    10.8.9.17 ODYSSEY2006 - TCP - No - 1266 0 0 0 0x0 0x0 0x0
    Firewall 8/10/2006 12:27:06 PM 10.8.9.1 1026 RPC (all interfaces) Initiated
    Connection SBS Protected Networks Access Rule 10.8.9.17 - Internal Local
    Host -
    10.8.9.1 ODYSSEY2006 - TCP - No - 19488 16 1594 213 0x80074e24
    0x0 0x0 Firewall 8/10/2006 12:27:06 PM 10.8.9.17 135 RPC (all interfaces)
    Closed Connection Allow RPC from ISA Server to trusted servers 10.8.9.1 -
    Local Host Internal -
    10.8.9.1 ODYSSEY2006 - TCP - No - 19452 233250 164 364 0x80074e24
    0x0 0x0 Firewall 8/10/2006 12:27:06 PM 10.8.9.17 135 RPC (all interfaces)
    Closed Connection Allow RPC from ISA Server to trusted servers 10.8.9.1 -
    Local Host Internal -
    10.8.9.1 ODYSSEY2006 - TCP - No - 19492 0 0 0 0x0 0x0 0x0
    Firewall 8/10/2006 12:27:06 PM 10.8.9.17 135 RPC (all interfaces) Initiated
    Connection Allow RPC from ISA Server to trusted servers 10.8.9.1 - Local
    Host Internal -
    10.8.9.1 ODYSSEY2006 - TCP - No - 19492 16 1638 237 0x80074e24
    0x0 0x0 Firewall 8/10/2006 12:27:06 PM 10.8.9.17 135 RPC (all interfaces)
    Closed Connection Allow RPC from ISA Server to trusted servers 10.8.9.1 -
    Local Host Internal -
    10.8.9.1 ODYSSEY2006 - TCP - No - 19494 0 0 0 0x0 0x0 0x0
    Firewall 8/10/2006 12:27:06 PM 10.8.9.17 135 RPC (all interfaces) Initiated
    Connection Allow RPC from ISA Server to trusted servers 10.8.9.1 - Local
    Host Internal -
    10.8.9.1 ODYSSEY2006 - TCP - No - 19496 0 0 0 0x0 0x0 0x0
    Firewall 8/10/2006 12:27:06 PM 10.8.9.17 135 RPC (all interfaces) Initiated
    Connection Allow RPC from ISA Server to trusted servers 10.8.9.1 - Local
    Host Internal -
    10.8.9.1 ODYSSEY2006 - TCP - No - 19496 15 888 60 0x80074e24
    0x0 0x0 Firewall 8/10/2006 12:27:06 PM 10.8.9.17 135 RPC (all interfaces)
    Closed Connection Allow RPC from ISA Server to trusted servers 10.8.9.1 -
    Local Host Internal -

    The log appears to be allowing the communication. Is there some special
    considerations or configurations for SBS2003 to utilize this functionality?

    Robert
     
    Robert Byrne, Aug 10, 2006
    #1
    1. Advertisements

  2. Robert Byrne

    Crina Li Guest

    Hi Robert,

    Thank you for posting in SBS newsgroup.

    According to your post, I understand that when you are using Group Policy
    result and targeted a Windows XP client computer, there is an error message
    as "The RPC server is unavailable". If I have misunderstood your concerns,
    please do not hesitate to let me know

    Firstly please ensure that the Windows Management Instrumentation [WMI]
    service is enabled on the client computer. Then before we go any further,
    can I assume that the client computer is Windows XP SP2?

    Please try to edit the Small Business Server Windows Firewall GPO and
    enable Windows Firewall: Allow Remote Administration Exceptions under
    Computer Configuration | Administrative Templates | Network | Network
    Connections | Windows Firewall | Domain Profile. This will open TCP ports
    135 (RPC) and 445 (SMB) as well as additional dynamically-assigned ports in
    the range of 1024 to 1034.

    And then run "gpupdate /force" on the clients and SBS to update the GPO.

    The detailed steps are as following:

    1. Start -> Administrative Tools -> Group Policy Management
    2. Expand Domains -> Your Domain
    3. Right click the Small Business Server Windows Firewall and click Edit
    4. Expand Computer configuration>Administrative templates>Network>Network
    connections> Windows Firewall> Domain Profile;
    5. Double click "Windows Firewall: Allow Remote Administration Exception"
    to enable it in right pane.
    6. Run Gpupdate /force on clients and SBS.
    7. Logoff and logon your client and test your issue again.

    If the issue still occurs, would you please help me collect the following
    information?

    1. Does this issue occur only when connecting to this client computer in
    GPMC? Please try to connect to the other computers to see if they are
    experiencing this problem.
    2. Is there any problem when opening shared folder on the affected Windows
    XP client computer?
    3. Get the ipconfig/all result from the client computer and SBS.

    If the issue occurs on lots of client computers, please check the following:

    Generally, this issue may occur:

    1. There are DNS resolution problems when solving the client computer's
    computer name to its IP address.
    2. There are network issues which prevents the connection from SBS Server
    to the client computer.
    3. There are WMI or Remote Registry problems which prevents the GPMC from
    collecting system data.

    Now, let's do the following:

    1. On the SBS Server, go to command prompt, type the following command:
    NSLOOKUP
    [XP client computer's computer name]

    When the result is returned, please check if the DNS Server resolves the
    client computer's computer name to its IP address.

    2. On the SBS Server, go to command prompt. Type the following command:
    PING [XP client computer's computer name]
    PING [XP client computer's IP address]

    Please check if the network connection is working.

    3. Go to the client computer, click Start -> Run, type Services.msc and
    click OK. Locate the "Windows Management Instrumentation" service and open
    its properties page. When it opens, under General tab, make sure that the
    "Startup Type" is set as Automatic and this service is started.

    4. In the Service Console, check if the Remote Registry service's startup
    type is Automatic and make sure that this service is started

    5. On the XP client computer, make sure that the Windows Firewall has not
    been started.

    Then, please try again to see how it goes.

    I appreciate your time and look forward to hearing from you.

    Best regards,

    Crina Li (MSFT)

    Microsoft CSS Online Newsgroup Support

    Get Secure! - www.microsoft.com/security

    =====================================================
    This newsgroup only focuses on SBS technical issues. If you have issues
    regarding other Microsoft products, you'd better post in the corresponding
    newsgroups so that they can be resolved in an efficient and timely manner.
    You can locate the newsgroup here:
    http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

    When opening a new thread via the web interface, we recommend you check the
    "Notify me of replies" box to receive e-mail notifications when there are
    any updates in your thread. When responding to posts via your newsreader,
    please "Reply to Group" so that others may learn and benefit from your
    issue.

    Microsoft engineers can only focus on one issue per thread. Although we
    provide other information for your reference, we recommend you post
    different incidents in different threads to keep the thread clean. In doing
    so, it will ensure your issues are resolved in a timely manner.

    For urgent issues, you may want to contact Microsoft CSS directly. Please
    check http://support.microsoft.com for regional support phone numbers.

    Any input or comments in this thread are highly appreciated.

    =====================================================

    This posting is provided "AS IS" with no warranties, and confers no rights.
    --------------------
    | From: "Robert Byrne" <>
    | Subject: Group Policy Results Wizard
    | Date: Thu, 10 Aug 2006 12:28:58 -0500
    | Lines: 62
    | X-Priority: 3
    | X-MSMail-Priority: Normal
    | X-Newsreader: Microsoft Outlook Express 6.00.2900.2869
    | X-RFC2646: Format=Flowed; Original
    | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
    | Message-ID: <>
    | Newsgroups: microsoft.public.windows.server.sbs
    | NNTP-Posting-Host: ip70-177-108-254.ok.ok.cox.net 70.177.108.254
    | Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP04.phx.gbl
    | Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:288692
    | X-Tomcat-NG: microsoft.public.windows.server.sbs
    |
    | I'm having difficulty running the Group Policy Results Wizards from the
    | server to an interal Workstation. I receive the following error:
    |
    | Failed to connect OCG\workstation1 due the error listed below. Ensure
    that
    | the Windows Management Instrumentation [WMI] service is enabled on the
    | target computer, and consult the event log of the target computer for
    | further details.
    |
    | The RPC server is unavailable.
    |
    | Research online indicates it can be a Windows Firewall issue. I have
    | disabled the firewall on the client machine. However, I still receive
    this
    | error. Could the ISA server be blocking the traffic? I ran a query from
    | the ISA while attempting the connection. I receive the following entries:
    |
    | 10.8.9.1 ODYSSEY2006 - TCP - No - 19488 0 0 0 0x0 0x0 0x0
    | Firewall 8/10/2006 12:27:06 PM 10.8.9.17 135 RPC (all interfaces)
    Initiated
    | Connection Allow RPC from ISA Server to trusted servers 10.8.9.1 - Local
    | Host Internal -
    | 10.8.9.17 ODYSSEY2006 - TCP - No - 1265 0 0 0 0x0 0x0 0x0
    | Firewall 8/10/2006 12:27:06 PM 10.8.9.1 135 RPC (all interfaces)
    Initiated
    | Connection SBS Protected Networks Access Rule 10.8.9.17 - Internal Local
    | Host -
    | 10.8.9.17 ODYSSEY2006 - TCP - No - 1266 0 0 0 0x0 0x0 0x0
    | Firewall 8/10/2006 12:27:06 PM 10.8.9.1 1026 RPC (all interfaces)
    Initiated
    | Connection SBS Protected Networks Access Rule 10.8.9.17 - Internal Local
    | Host -
    | 10.8.9.1 ODYSSEY2006 - TCP - No - 19488 16 1594 213 0x80074e24
    | 0x0 0x0 Firewall 8/10/2006 12:27:06 PM 10.8.9.17 135 RPC (all interfaces)
    | Closed Connection Allow RPC from ISA Server to trusted servers 10.8.9.1 -
    | Local Host Internal -
    | 10.8.9.1 ODYSSEY2006 - TCP - No - 19452 233250 164 364
    0x80074e24
    | 0x0 0x0 Firewall 8/10/2006 12:27:06 PM 10.8.9.17 135 RPC (all interfaces)
    | Closed Connection Allow RPC from ISA Server to trusted servers 10.8.9.1 -
    | Local Host Internal -
    | 10.8.9.1 ODYSSEY2006 - TCP - No - 19492 0 0 0 0x0 0x0 0x0
    | Firewall 8/10/2006 12:27:06 PM 10.8.9.17 135 RPC (all interfaces)
    Initiated
    | Connection Allow RPC from ISA Server to trusted servers 10.8.9.1 - Local
    | Host Internal -
    | 10.8.9.1 ODYSSEY2006 - TCP - No - 19492 16 1638 237 0x80074e24
    | 0x0 0x0 Firewall 8/10/2006 12:27:06 PM 10.8.9.17 135 RPC (all interfaces)
    | Closed Connection Allow RPC from ISA Server to trusted servers 10.8.9.1 -
    | Local Host Internal -
    | 10.8.9.1 ODYSSEY2006 - TCP - No - 19494 0 0 0 0x0 0x0 0x0
    | Firewall 8/10/2006 12:27:06 PM 10.8.9.17 135 RPC (all interfaces)
    Initiated
    | Connection Allow RPC from ISA Server to trusted servers 10.8.9.1 - Local
    | Host Internal -
    | 10.8.9.1 ODYSSEY2006 - TCP - No - 19496 0 0 0 0x0 0x0 0x0
    | Firewall 8/10/2006 12:27:06 PM 10.8.9.17 135 RPC (all interfaces)
    Initiated
    | Connection Allow RPC from ISA Server to trusted servers 10.8.9.1 - Local
    | Host Internal -
    | 10.8.9.1 ODYSSEY2006 - TCP - No - 19496 15 888 60 0x80074e24
    | 0x0 0x0 Firewall 8/10/2006 12:27:06 PM 10.8.9.17 135 RPC (all interfaces)
    | Closed Connection Allow RPC from ISA Server to trusted servers 10.8.9.1 -
    | Local Host Internal -
    |
    | The log appears to be allowing the communication. Is there some special
    | considerations or configurations for SBS2003 to utilize this
    functionality?
    |
    | Robert
    |
    |
    |
     
    Crina Li, Aug 11, 2006
    #2
    1. Advertisements

  3. Robert Byrne

    Mark Crall Guest

    Hi Robert,
    I'm not trying to get in the way of Crina's suggestions, but there is also a
    thread on this same issue posted 6/30/06 with the exact same subject. You
    may want to read through those. I've pasted the last post below so you can
    read the thread (in reverse if from top to bottom).

    --
    Regards,
    Mark Crall
    Systems Engineer
    Charlotte Tech Care Team / Carolina VoIP
    Microsoft Small Business Specialist
    Charlotte SBS Group Leader - www.sbs-charlotte.com
    Direct: (704) 248-8328 x33

    If you think installing patches and security updates is expensive, try not
    installing them...





    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    Mark,

    Thanks for your reply. I found one of those links very helpful and ended up
    downloading and running the WMI Diagnostic tool on my laptop. It reported
    that WMI was working correctly. However, the server still gives the same
    error whenever I try to run the Group Policy Results Wizard.

    Very strange .... oh well.

    Thanks for trying anyway. Much appreciated.

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     
    Mark Crall, Aug 11, 2006
    #3
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.