I have a custom WMI application. It works wonderfully on a number of servers (windows 2003, 2008). However, some of our servers are behind another firewall. I have followed http://msdn.microsoft.com/en-us/library/windows/desktop/bb219447%28v=vs.85%29.aspx and have the permissions the same as the other 2008 machines. We opened port 24158 and 135.
As you might have guessed it still doesn't connect. I would love any thoughts on this.
Update: these machines are actually not R2. I had stupidly assumed they were, since all of our other servers are. The version is 6.0.6002 to be exact.
Update: from this article http://technet.microsoft.com/en-us/library/cc730673%28WS.10%29.aspx
under Administrative Tools > Component Services > leftpane >Component Services> Computers > My Computer > DCOM Config > middle pane > Windows Management and Instrumentation, and then click Properties under endpoits it is correctly configured to use 24158. However no packet is ever sent to or from that port when WMI is enabled.
Update: It may be netbios related, as there is a packet coming from a closed netbbios port that is being flagged in Wireshark. Why does WMI need to use netbios?
Best Answer
You should try your hand at Network Monitor and install it on the computer you are running the WMI from. You should see it attempt to connect to the remote server so you can first validate it is trying to connect on 24158. You should see connections out and data coming back on those two ports if you have both sides configured correctly.