- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- WBEM and ISA 2004 EE
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-15-2005 10:22 PM
тАО09-15-2005 10:22 PM
WBEM access to four of my servers works fine.
I have not WBEM access to the fifth server, which is Microsoft ISA 2004 Enterprise Edition server computer. For example, if I select Properties link on the System Page of that server I see the message я┐╜Error: Cannot connect to target system using WBEMя┐╜. Two Failure Audit messages appear at the same time in the security event log of the ISA Server Computer with event ID 537 (an error occurred during logon), my user name and correct domain name are indicated in the message body, Logon Process and Authentication Package fields contain Kerberos. No я┐╜denied accessя┐╜ messages appear in the ISA log, I created two я┐╜globalя┐╜ rules for All Outbound Traffic я┐╜ the one from Internal network to LocalHost and another from LocalHost to Internal Network. I guess ISA should pass all traffic between CMS and ISA computer transparently in this case.
Could you suggest something?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-16-2005 01:54 AM
тАО09-16-2005 01:54 AM
Re: WBEM and ISA 2004 EE
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-16-2005 02:26 AM
тАО09-16-2005 02:26 AM
Re: WBEM and ISA 2004 EE
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-17-2005 03:07 AM
тАО09-17-2005 03:07 AM
Re: WBEM and ISA 2004 EE
Dear AMicSys, I wrote in my question that all traffic between ISA and Internal network was enabled. Moreover, no \ denied access\ messages appear in the ISA log. Certainly, the port 5989 was opened. But the most funny and strange fact is that there was no need to open the port. The only messages I found in the ISA log after clicking on the Properties link on the System Page of my ISA Server computer in the SIM was messages for RPC protocol. That is a key fact for solution search.
For those who spent a lot of time to solve the same problem I ll describe the cause. At first, read the FAQ \ I cannot use DCOM from a computer in the Remote Management Computers set to the ISA Server computer. Why not? \ at the following link http://www.microsoft.com/technet/prodtechnol/isa/2004/plan/faq-administering.mspx. My CMS was included in the Remote Management Computers set. The rule No2 of the ISA system policy rules called \ Allow remote management from selected computers using MMC\ enables RPC, but Enforce strict RPC compliance flag can t be cleared for this rule. The flag prevents remote DCOM execution from computers indicated as sources for this rule. I have removed CMS from this rule and have created another Array Access Rule for RPC protocol with CMS as source and with cleared Enforce strict RPC compliance flag.
The strangest thing in this history is that DCOM execution prevention resulted in the \ Cannot connect to target system using WBEM\ message
I can see the system properties in SIM now, but the ISA log doesn t register any traffic on the port 5989.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-17-2005 03:19 AM
тАО09-17-2005 03:19 AM
Re: WBEM and ISA 2004 EE
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-25-2005 05:19 AM
тАО09-25-2005 05:19 AM
Re: WBEM and ISA 2004 EE
Regards
Morgan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-25-2005 10:05 AM
тАО09-25-2005 10:05 AM
SolutionAMicSys: Your information is incorrect. This is a Windows machine and Windows uses WMI and NOT WBEM. Port 5989 would be used to communicate to a device talking WBEM (such as the OpenWBEM or OpenPegasus CIMOM on Linux). For devices that speak WMI, HP SIM uses the WMI Mapper service either locally or remotely, to translate back and forth.
"I think the reason you are not seeing any traffic on ports 5988/5989 is that Windows WMI/WBEM uses RPC."
Morgan: WBEM does NOT equal WMI. WMI communications are via DCOM. WBEM communications are via HTTPS on 5989. HP SIM will talk to the WMI Mapper on 5989 and the WMI Mapper will relay that to the WMI device via DCOM.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-25-2005 10:12 AM
тАО09-25-2005 10:12 AM
Re: WBEM and ISA 2004 EE
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-25-2005 10:47 AM
тАО09-25-2005 10:47 AM