Quantcast
Channel: Forefront TMG and ISA Server forum
Viewing all articles
Browse latest Browse all 3822

Can't get WMI connections through the TMG server

$
0
0

Hey all,

I've been googling relentlessly trying to get this to work. I have a monitoring server in this case PRTG and I'd like to monitor a service on one of the servers hosted between the monitoring server and the TMG firewall.

I launched WBEMtest on the monitoring server to ensure that WMI first off succeeds with my account than would proceed to go on with a dedicated PRTG based account.

Sure enough I created an access rule on the TMG from my Monitoring server to my Server hosting the service. Sure enough the Wbemtest fails.

Alright... google.. Helpful by Marc Grote ... and even more helpful by Ori Yosefi as well as this helpful one from the great Richard Hicks.

All great guides however, As mentioned by the first two links, I created a rule

1) access rule that allows RPC (All Interfaces) from the Internal network to the Local Host network.

on the next Step they both claim to uncheck the strict RPC check box by clicking the rule and selecting

"To do so, right click the Firewall Policy rule and select the RPC setting." - Marc Gotes

or

"After creating the rule, right-click it and select Configure RPC Protocol." - Ori Yosefi

However whenever I right click the rule I don't have either of these options.. and click the protocols tab from the properties on the rule All I can do is get basic settings for the protocol and not this required checkbox anywhere.

What am I missing here?

They also mention removing the check box from the Active Directory section of teh System Policy Editor. Which I already have Enforce Strict RPC compliance unchecked.

I then created a Rule to Allow "ALL Outbound traffic" from my monitoring Server to the server which I need monitored. As specified by Ori Yosefi's post.

Yet when I run the WBEMtest it still fails to connect... I even verified all local firewall rules on the server I need and tested wbemtest from a server in the same subnet and it connected just fine.

Please someone... what did I miss?!?!?!


Viewing all articles
Browse latest Browse all 3822

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>