- Community Home
- >
- Services
- >
- Insight Remote Support
- >
- Re: ISEE unable to connect
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
тАО05-04-2006 04:39 PM
тАО05-04-2006 04:39 PM
This is what is in the mad.log:
040506 21:58:45.168 ERROR,[Comm] install failed for server: stlsmorcaraendmz02.e
naf.****.***.com auth_key: guest
040506 21:58:45.168 ERROR,[Comm] NetworkException (1): socket.cpp:116 (238) Conn
ection timed out Socket::connect(): socket() failed: stlsmorcaraendmz02.enaf.****.***.com (144.160.176.***)
I configured the motprefs=Agent_Port=5060 and the server above as the default_motive_server.
Sorry about the **s
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-04-2006 10:08 PM
тАО05-04-2006 10:08 PM
Re: ISEE unable to connect
If you are pointing the ISEE to the SPOP server then you should use the SPOP's server name.
Try to reinstall the client first.
If it doesn't help please provide more information about the setup.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-04-2006 11:52 PM
тАО05-04-2006 11:52 PM
Re: ISEE unable to connect
Is this the name of your Server stlsmorcaraendmz02? If this is true, then you are trying to send ISEE packacges to itself.
Server Name must be the name of HP Backend Server you are reporting to.
If this is HP-UX and your Server is in North Americas, you can run:
/opt/hpservices/RemoteSupport/bin/changeServer isee.americas.hp.com
If this is Windows, do a search for the command and run it as above.
Make sure your Server can resolve the IP address of isee.americas.hp.com plus port 80 on your Firewal has been open to allow outbound traffic.
Hope this helps,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-05-2006 09:34 AM
тАО05-05-2006 09:34 AM
SolutionI was able to make the change on your SPOP, please try submitting the info again. If you see the Entitlement section in the GUI, this means it's working.
If you are still having problem, please mail me /opt/hpservices/log/mad.log and /opt/hpservices/etc/motprefs.
Thanks,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-05-2006 10:59 AM
тАО05-05-2006 10:59 AM
Re: ISEE unable to connect
I sent emailed you the info you requested.