Yeah, I had already found that technote and unchecked it.
(from above)
Under "Edit System Policy"/Authentication Services/Active Directory, I have unchecked "Enforce strict RPC compliance".
Main Topics
Browse All TopicsHello.
We have an ISA 2004 ENT server we use for our firewall. It is configured with 2 interfaces (outside and inside). We have a monitoring system located on the inside network which uses WMI. We need to be able to WMI access the ISA server from the inside network. Currently we cannot.
Here is what I have done so far to try to get it to work:
*****Settings*****
Under Firewall Policy, I have created an Access Rule that allows all outbound traffic from "Internal" to "Internal" & "Local Host".
Under Firewall Policy, I have created an Access Rule that allows "RCP (all interfaces)" & "RPC Server (all interfaces)" traffic from "Internal" to "Internal", "External" & "Local Host".
Under "Edit System Policy"/Authentication Services/Active Directory, I have unchecked "Enforce strict RPC compliance".
Under "Edit System Policy"/Remote Management/Microsoft Management Console (MMC), I have enabled it. Also I have added "Internal" & the management server to the "From" tab.
Under "Edit System Policy"/Diagnostic Services/Windows Netowrking, I have enabled it. Also I have added "Internal" & the management server to the "To" tab.
Under "Edit System Policy"/Remote Monitoring/Remote Performance Monitoring, I have enabled it. Also I have added "Internal" & the management server to the "From" tab.
Under "Edit System Policy"/Remote Monitoring/Microsoft Operations Mananger, I have enabled it. Also I have added "Internal" & the management server to the "To" tab.
Using "wmimgmt.msc" I have made sure that "Root/CIMV2" security has the domain admin's user name listed with all rights.
*****Testing and logging*****
From my management server, using WBEMTEST to test WMI, I have done the following:
Set Namespace to \\isaserver\root\cimv2
Set user and password to the domain admin.
Clicked connect. I get the following error:
Number: 0x800706ba
Facility: Win32
Description: The RPC server is unavailable
While running the above test, I ran ISA server monitoring of the anything going to the ISASERVER's internal IP. I get the following messages:
Protocol Action Rule Result Code Source Network Destination Network
RPC (all interfaces) Initiated Connection Allow remote management from selected computers using MMC 0x0 Internal Local Host
RPC (all interfaces) Initiated Connection Allow remote management from selected computers using MMC 0x0 Internal Local Host
RPC (all interfaces) Closed Connection Allow remote management from selected computers using MMC 0x80074e24 FWX_E_CONNECTION_KILLED Internal Local Host
RPC (all interfaces) Closed Connection Allow remote management from selected computers using MMC 0x80074e24 FWX_E_CONNECTION_KILLED Internal Local Host
RPC (all interfaces) Initiated Connection Allow remote management from selected computers using MMC 0x0 Internal Local Host
RPC (all interfaces) Closed Connection Allow remote management from selected computers using MMC 0x80074e24 FWX_E_CONNECTION_KILLED Internal Local Host
RPC (all interfaces) Initiated Connection Allow remote management from selected computers using MMC 0x0 Internal Local Host
RPC (all interfaces) Initiated Connection Allow remote management from selected computers using MMC 0x0 Internal Local Host
RPC (all interfaces) Closed Connection Allow remote management from selected computers using MMC 0x80074e24 FWX_E_CONNECTION_KILLED Internal Local Host
Thank You
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Create a new protocol:
Name: WMI (17940)
TCP/outbound/17940 to 17940/leave ICMP fields blank
No secondary
Create a new access rule:
Name: Allow WMI
Allow
Selected Protocols: WMI (17940) (the one we just created), RPC (All Interfaces)
Sources: I selected a specific computer
Destinations: Local Host
Users: I left it at All Users
After you finish making the new rule, right click on it and select "Configure RPC protocol", uncheck the box (Enforce strict RPC Compliance).
That's it. You _DO NOT_ need to uncheck the "Enforce strict RPC Compliance" from the System Policy | Authentication Services | General Tab.
Hey Keith,
Not sure where you are seeing 'all protocols'. I'm only allowing two protocols from a specific computer to the localhost:
The one I created 'Allow WMI' and the built-in RPC (All interfaces) protocol.
The Allow WMI only opens port 17940. I don't know why 17940 is needed, that is just what was blocked when I was watching the monitoring while using the wbemtest program, my quick research about WMI didn't find anything that said WMI uses 17940, but that's what the monitoring log indicated.
I created the new protocol and added the access rule. I still get the same error.
From my management server, using WBEMTEST to test WMI, I still get the same error:
Set Namespace to \\isaserver\root\cimv2
Set user and password to the domain admin.
Clicked connect. I get the following error:
Number: 0x800706ba
Facility: Win32
Description: The RPC server is unavailable
While running the above test, I ran ISA server monitoring of the anything going to the ISASERVER's internal IP. I get the following messages:
Protocol Action Rule Result Code Source Network Destination Network
RPC (all interfaces) Initiated Connection Allow remote management from selected computers using MMC 0x0 Internal Local Host
RPC (all interfaces) Initiated Connection Allow remote management from selected computers using MMC 0x0 Internal Local Host
RPC (all interfaces) Closed Connection Allow remote management from selected computers using MMC 0x80074e24 FWX_E_CONNECTION_KILLED Internal Local Host
RPC (all interfaces) Closed Connection Allow remote management from selected computers using MMC 0x80074e24 FWX_E_CONNECTION_KILLED Internal Local Host
RPC (all interfaces) Initiated Connection Allow remote management from selected computers using MMC 0x0 Internal Local Host
RPC (all interfaces) Closed Connection Allow remote management from selected computers using MMC 0x80074e24 FWX_E_CONNECTION_KILLED Internal Local Host
RPC (all interfaces) Initiated Connection Allow remote management from selected computers using MMC 0x0 Internal Local Host
RPC (all interfaces) Initiated Connection Allow remote management from selected computers using MMC 0x0 Internal Local Host
RPC (all interfaces) Closed Connection Allow remote management from selected computers using MMC 0x80074e24 FWX_E_CONNECTION_KILLED Internal Local Host
If I right click on the rule that I created and check the "Enforce strict RPC Compliance" under Configure RPC protocol, I get the same results in the monitoring tab as you do (the wbemtest comes back immediately with the error message).
The only difference is that in my logs, the rule is my "Allow WMI" that I created. Yours is "Allow remote....". Either move the Allow WMI rule up in the order (mine is my second one). Or uncheck the "Enforce strict RPC Compliance" from your "Allow remote..." rule.
The "Allow remote..." is a rule you created correct? Or is that coming from a selection in the System Policy? In any case, we want to see the "Allow WMI" rule being the rule that is being logged. Once we have that I believe your problem will be solved.
The problem seems to be with having the remote computer in the Remote Management | Microsoft Management Console (MMC) system policy rule. If I add my test machine (that is working) to the from tab on that rule, the wbemtest no longer works from my test machine. Unchecking the "Enforce strict RPC compliance" in the Authentication Service | Active Directory System Policy did not make a difference.
You will need to remove your machine from that System Policy (Remote Management | Microsoft Management Console (MMC).
I will continue to see if there is a way to leave a computer in that policy, and yet still be able to use WMI from it to the ISA machine.
Do you need to do both from that machine, or just WMI?
Strange for me removing strict RPC worked straight away with my wmi script but the remote managment MMC rule bit did not work. I think it may be due to the fact that my PC is part of the "remote mangment set" and I would have to remove it from that group but then would loose my ability to mange the server remotley....
Business Accounts
Answer for Membership
by: keith_alabasterPosted on 2005-12-21 at 11:58:27ID: 15529282
These messages are actually generated by the ISA server itself rather than a rule blocking them. You will find references to it on the MS msdn web site.
ers/dmoisa n/
You can find info here though. It is likely you have the enforce strict RPC options set within the System policy (in ISA) as I recall. Uncheck the option and you may get through
Regards
Keith
http://spaces.msn.com/memb