Server Management - Systems Insight Manager
1833263 Members
2841 Online
110051 Solutions
New Discussion

Re: Connect to SMH on a managed server through CMS

 
Ales Kostohryz
Occasional Contributor

Connect to SMH on a managed server through CMS

Dear all

Can anyone help me. I've lost communication on my CMS (SIM 5.0 SP2) with SMH (2.1.3.132)
I try to connect to SMH on a managed server through CMS I get IE window with message
"There is no System Management Home Page for ak-srv7.stredozem.net"

In CMS on "System Page" for AK-srv7 in tab "Tools & Links" is missing "System Management Page: ak-srv7"

When I run Task "System Automatic Discovery" it ran too long time and in log "mxdomainmgr.1920.out" are errors mesage

"[PoolTcpEndpoint] Remote Host /127.0.0.1 SocketException: Software caused connection abort: recv failed"
"[PoolTcpEndpoint] Remote Host /127.0.0.1 SocketException: Connection reset"

Anyone any ideas?
9 REPLIES 9
rcseattle
Frequent Advisor

Re: Connect to SMH on a managed server through CMS

Check the services on the server to make sure they are running. If discovery ran while the service was not running it would cause this.

Verify the SMH is working on ak-srv7 by going directly to it http://servername:2381

If SNMP security is set to trust only certain hosts, be sure the CMS name is in there are well as localhost.

Ales Kostohryz
Occasional Contributor

Re: Connect to SMH on a managed server through CMS

The service "HP System Management Homepage" is running. The service HP agents are as well as running.

The SMH is working, if I run the SMH click on icon on desktop.

If I verify the SMH on ak-srv7 by going directly to:

http://127.0.0.1:2381 - window is blank
http://localhost:2381 - window is blank
http://ak-srv7:2381 - The page cannot be displayed
http://ak-srv7.steredozem.net:2381 - window is blank
https://127.0.0.1:2381 - connect SMH
https://localhost:2381 - connect SMH
https://ak-srv7:2381 - The page cannot be displayed
https://ak-srv7.steredozem.net:2381 - The page cannot be displayed

Current WinHTTP proxy is settings Direct access (no proxy server)
rcseattle
Frequent Advisor

Re: Connect to SMH on a managed server through CMS

Have you checked the SNMP settings?

If the radio button "Accept SNMP packets from these hosts" is checked, make sure localhost is included there as well as the name of your CMS server.

Also once I had one server misbehaving and it was somehow related to the VC Agent. Unchecking "interact with desktop" fixed that one, however I don't understand why that service defaults that way or what impact unchecking the box may have. But for now it all seems to be working well for me that way.
rcseattle
Frequent Advisor

Re: Connect to SMH on a managed server through CMS

Right I missed the "s"

https://servername:2381

Giving this more thought, if it was the SNMP issue you'd get part of the page but not all of it. And it would be the same whether you did it locally or remotely.

I have seen the VCAgent issue I mentioned above in one case causing the whole page to timeout, but it also behaved the same locally and remotely.

The problem you're describing sounds exactly like the issue with the Version 2.1.2.127 SMH when the server in question has multiple NICs. The page would bind to the wrong NIC and not all of them.

Maybe forcing a reinstall 2.1.3.132 on the server would be your best bet.
Rich Purvis
Honored Contributor

Re: Connect to SMH on a managed server through CMS

Since it looks like you are connecting by localhost and the loopback IP address you might try and see if you can connect using the IP address of the system. If that works then it would look like you can connect by IP address and not by name - perhaps it could be some DNS type issue with the network. It sounds like you already have the latest SMH - if the version shown on the SMH pages is the same you listed in your first post there is no reason to reinstall.

-Rich
Why does my tivo keep recording Nickelodeon?
Ales Kostohryz
Occasional Contributor

Re: Connect to SMH on a managed server through CMS

SNMP settings is correctly. In "Accept SNMP packet from these hosts" is "localhost" and IP address CMS servers.

On Server was install SMH 2.1.2.127 from PSP 7.40a and then was install SMH 2.1.3.132 from Management CD 7.42.

If I verify the SMH on ak-srv7 (ip - 172.26.6.20) by going directly to:

https://172.26.6.20:2381 - The page cannot be displayed

Ales
rcseattle
Frequent Advisor

Re: Connect to SMH on a managed server through CMS

Ales, a couple of questions for you:
Does the server have multiple NICs?
When you try https://ak-srv7:2381 is the device you are coming from on the same network segment?

See if ak-srv7 pings from the device you're trying to connect remotely.

Or try
telnet ak-srv7 2381

If it connects, you should get a blank screen. If it can't connect, you'll get a message that the connect failed.

If it doesn't ping it's obviously a network/routing issue. If it does ping but telnet fails, it may be firewalled somehow.

If you haven't already, try connecting to the SMH from another device on the same segment if you can.

If you have multiple NICs on ak-srv7 and all else seems to fail, force reinstallation of 2.1.3.132; it doesn't require a reboot and I see no downside to reinstalling that.

*******************
One more thing I just thought of; one of the SP's for Windows 2000 sets DisableStrictNameChecking=0. The OS will not respond to a c-name if that is set. To disable set the following reg key and reboot:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters]
"DisableStrictNameChecking"=dword:00000001

Mark_672
Advisor

Re: Connect to SMH on a managed server through CMS

I encounter the same problem. I have single NIC and have a "Page cannot be displayed error". I have HP Proliant ML370 G4 on Windows 2000 Server.
rcseattle
Frequent Advisor

Re: Connect to SMH on a managed server through CMS

By chance I had one server behaving the same way this morning.

I restarted services. I still couldn't get to the server SMH remotely, but could locally.

I checked another server on the same segment. It still worked so I figured this was not a any kind of network issue.

So I forced reinstallation of SHM 2.1.3.132 and guess what. It seems to be working normally again.