Re: WMI RPC Server not available

Hi Peter.

Don't think that really covered it. I have WinXP SP2 clients. Firewall is
configured using a GPO to enable the Firewall and set up a few port and
program exceptions. Included in this are ports 135 and 445

when I run wbemtest I connect to \\pcname\root\cimv2. In the past this
always worked, regardless of OS when I attempted to connect remotely to a
machine using thie above connection string. Once connected I would put in a
query of "Select * from Win32_atchstate where status = 'Applicable' to showe
me the patches that were still outstanding on that PC.

Since installing SP2, this now does not work for XP SP2 machines, but does
for W2k and W2k3 servers.

Not sure what I'm missing, I thought opening 135 would sort the problem but
it doesn't

Regards,

John


"Peter Falz" <pf.ms.news@xxxxxxxxxxxxxxxx> wrote in message
news:et5HAQqPFHA.1392@xxxxxxxxxxxxxxxxxxxxxxx
> Hi John,
>
> Take a look at:
> http://groups.google.de/groups?q=%22Remote+Procedure+Call+failed%22+%2Bwmi&hl=de&lr=&selm=KvfaPVtEFHA.4072%40TK2MSFTNGXA01.phx.gbl&rnum=3
>
> HTH
>
> Bye
> Peter
>
>
> "John" <hush@xxxxxxxxxxxxxx> schrieb im Newsbeitrag
> news:eGg4CIqPFHA.1096@xxxxxxxxxxxxxxxxxxxxxxx
>> Hi.
>>
>> I hope this is the correct group to post this query to. If not I
>> apologise.
>>
>> I occasionally use WBEMTEST.exe to check patchstate on individual
>> machines
>> where SMS reporting is quirky. When I try to run this tool against a
>> remote
>> PC, some of them give me an RPC Server is unavailable error when I
>> attempt
>> to connect using \\PCName\root\cimv2. The Error number is 0x800706ba and
>> Facility is Win32
>>
>> all my clients are WXP with SP2. (If I run WBEMTEST locally, it works as
>> expected.)
>>
>> This has something to do with the Firewall settings on SP2. I assume a
>> port
>> needs to be opened. I already have 135 and 445 opened for internal subnet
>> use. If I stop the Firewall, i can then connect remotely
>>
>> Can anyone tell me the one I need to enable? (I have tried this with a
>> Group
>> policy, but some machines work, others don't, yet the GP is being applied
>> successfully to all machines, as other changed made by the GP are
>> visible).
>>
>> Thanks
>>
>> john
>>
>>
>>
>
>


.

Relevant Pages

  • Re: Shared Printer Problem
    ... "Printer status cannot be displayed with port that is currently running." ... file/printer sharing and then install the correct drivers for your printer ... start by running the Network Setup Wizard on all machines (see ... by 1) a misconfigured firewall or overlooked firewall (including a stateful ...
    (microsoft.public.windows.vista.print_fax_scan)
  • Re: File sharing
    ... >>> firewall, but it doesn't work. ... >>> machines here this configuration works fine. ... I would also use telnet to try and access TCP port 139 and 445 on a machine that works correctly and one that does not to help determine if it is a network access or other problem. ... If the port is open you will see a blank command window with a blinking cursor like you will see if you run telnet 127.0.0.1 445 on your computer. ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Windows Firewall Blocks my ability to connect to an FTP site
    ... I'm using SP2 ... port 21 and did the steps the the KB Article. ... with the firewall off works fine. ... The Command-line FTP reports Unknown Error Number. ...
    (microsoft.public.windowsxp.security_admin)
  • Re: NetBios Names and SP2
    ... Using the Ips yes, but when using computers names, non ... >> Before SP2, I ll machines connect to each other using computer names. ... >> SP2 and it's firewall, when firewall is active, I can not connect to ...
    (microsoft.public.windowsxp.network_web)
  • Re: Port 25 closing?
    ... > connections to our mail server via port 25. ... I can log onto the firewall, ... > after installing SP2. ...
    (Fedora)
Loading