 |  | Browser Problems |
When I use Internet Explorer 6.0 in Windows, why do I see warnings in the Security Alert dialog box when I login to the System Management Homepage?
Solution: There are two possible warnings that may be seen including: Warning #1: The name on the security certificate is invalid or does not match the name of the site. This warning occurs when you browse to the System Management Homepage using an IP address. This also occurs if you browse locally using localhost for the machine name. Warning #2: The security certificate was issued by a company you have not chosen to trust. View the cert to determine whether you want to trust the certificate authority. The certificate is issued by System Management Homepage. You can add the certificate to your Trusted Certificate list and the warning goes away.
Opening a second Mozilla browser can appear as an unauthorized login into System Management Homepage.
Solution: Mozilla browsers share sessions when launched separately.
Note: Separate sessions are shared in Mozilla when launched from the desktop, however they are not shared in Internet Explorer.
I get security messages or partially displayed pages when browsing into System Management Homepage from Internet Explorer running on Windows 2003.
Solution: The version of Internet Explorer 6.0 on Windows 2003 Server has different security settings in the default install. To prevent the problem, add each managed system into the local intranet zone twice, once as: http://hostname:2301 and once more as: https://hostname:2381. The alternatives to this solution are to decrease the level of security settings in the browser (not recommended) or alter the browser security settings to allow cookies (both stored and per-session) and allow active scripting.
My browser page does not display all of the contents. What is wrong?
Solution: Frame sizes are optimized for medium fonts. If you switch your browser to use larger or smaller fonts, then manually adjust the frame layout using the mouse.
Why does the browser prompt to accept cookies when accessing a system?
Solution: Browser cookies are required to keep track of user state and security. Cookies must be enabled in the browser and prompting for acceptance of cookies should be disabled.
How can I tell if my browser is supported?
Solution: The supported browsers are: Internet Explorer 6.0 Mozilla 1.5 Mozilla 1.6
When I browse to https://ipaddress:2381 on a local machine running Windows 2003, I don't see the Login screen.
Solution: Internet Explorer 6.0 on Windows 2003 sometimes causes only the Account Login text in a blue bar to appear instead of the entire Login page. This issue only occurs when browsing on a local system. Rather than specifying the IP address in the URL, the problem can be resolved by using localhost. HP recommends using the following URL to resolve this issue:
https://localhost:2381
 |  | Installation Problems |
When installing System Management Homepage, I am getting an error that reads, Another instance is running.
Solution: The System Management Homepage installation attempted to install on a system that had files that were previously corrupted or if the installation was aborted. To resolve this issue, navigate to the \temp directory on the System Management Homepage system and delete the smhlock.tmp file.
When installing System Management Homepage, I am getting an error that reads, error: cannot get exclusive lock on /var/lib/rpm/Packages error: cannot open Packages index using db3 - Operation not permitted (1) error: cannot open Packages database in /var/lib/rpm.
Solution: This error appears when more than one instance of the install is initiated on a Linux system. You can only run one installation of the System Management Homepage at a time.
 |  | IP Address Problems |
Is there an easier way to access the local system with my browser without having to find out its IP address?
Solution: Yes. You may access the local system at https://localhost:2381 or https://127.0.0.1:2381.
Note: The word localhost does not work in all languages. In addition, if you have a proxy server configured in your browser, you might need to add 127.0.0.1 to the browser list of addresses that should not be proxied.
When I use the IP Restricted Login feature on Windows 2000 Advanced Server, entering my server IP address does not have the desired effect. How can I be sure that the local machine IP addresses are recognized by this feature?
Solution: On Microsoft Windows NT 4.0 and Windows 2000 Advanced Server, enter 127.0.0.1 in addition to the actual IP addresses of the server if you intend to include or exclude the local machine. The address 127.0.0.1 is always included in the Include section, so it is only excluded if it is explicitly placed in the Exclude section.
Why isn't localhost access denied when I setup an IP restriction?
Solution: If you do not include the IP address for the local host in the Include field, the local host is still granted access because most users do not intend to block the local host access. If you do need to block localhost access, enter 127.0.0.1 into the Exclude field under IP Restriction.
Under IP Restriction, I did not include the system's local IP address or 127.0.0.1 to the Include list, but I can still browse to it locally.
Solution:As a precaution against users unintentionally locking themselves out of System Management Homepage access, localhost requests are not denied when the local IP adresses are not mentioned in the Include list. If this is absolutely necessary, the local system's IP address and 127.0.0.1 can be added to the Exclude list, and this setting denies access to any user trying to gain access from the local system.
 |  | Login Problems |
I cannot login to System Management Homepage on my Windows operating system.
Solution: Verify that a valid Windows operating system account has been set up and that the login is included in the Administrators group or one of the System Management Homepage operating system groups. Login to the operating system. Change the password if prompted.
Note: If this password prompt appears, then the operating system Administrator has setup the user account with the user must change the password on next logon option selected. Any login created in the future can be added by the operating system Administrator without selecting the user must change the password on next logon option. In addition, if this option is selected, you can change the password through the operating system before logging in to the System Management Homepage.
Why doesn't my password work after I upgraded my Web Managed Products?
Solution: System Management Homepage 2.0 and greater uses operating system accounts whereas previous versions used three static accounts (administrator, operator, and user). Any operating system account belonging to the administrators group (root group in Linux) has administrative access to the System Management Homepage. With this access, you can assign accounts in other operating system account groups to different levels of access for System Management Homepage. The System Management Homepage online help describes this process in detail.
I created new Windows accounts, using default settings, for use with the System Management Homepage but I cannot use them to login.
Solution: By default, new accounts created in Windows operating systems are set to user must change the password on next login. This option must be deselected before the account can be used to login to the System Management Homepage.
When I use Internet Explorer 6.0 in Windows and browse through the management server to a system that was discovered by IP address, I cannot log into the System Management Homepage. If anonymous access is enabled, I get through anonymously but the user name is incorrect.
or
When I use Internet Explorer 6.0 in Windows and browse through the management server to a device that was discovered by the IP address, the detailed certificate information does not appear in the text box of the Automatic Import Certificate screen.
Solution: These issues can be resolved two different ways by adjusting the Internet Explorer settings:
 |  | Security Problems |
Why can I not import X.509 certificates directly into System Management Homepage?
Solution: System Management Homepage generates Certificate Request in base64 encoded PKCS#10 format. This certificate request should be supplied to the Certificate Authority. Most Certificate Authorities return base64 encoded PKCS#7 certificate data that you can import directly into System Management Homepage by selecting
Settings System Management Homepage
. If the Certificate Authority returns the certificate data in X.509 format, then you can rename the X.509 certificate file as cert.pem and place it into \hp\sslshare directory. When System Management Homepage is restarted, this certificate is used.
Why is my PKCS#7 data cert data not accepted?
Solution: When using a Mozilla browser, there can be problems when cutting and pasting cert request and reply data when using Notepad or other editors. To avoid these problems always use Mozilla to open any certificate reply files from your CA. Be sure to use the Select All, Cut , and Paste operations that are supplied by Mozilla when working with certificates.
Why is my private key file not protected by the file system?
Solution: If you are using Windows operating systems, you must have the system drive in NTFS format for the private key file to be protected by the file system.
Why do I get errors when I paste my customer generated certificate PKCS#7 data into the HP Systems Insight Manager Certificate Data field in Settings System Management Homepage Security Trusted Management Servers
?
Solution: The customer generated certificate PKCS#7 data does not belong in the Trusted Management Servers field. The PKCS#7 data should be imported into the Customer Generated Certificates Import PKCS#7 Data field under Settings→System Management Homepage→Security→Local Server Certificate. The HP Systems Insight Manager Certificate Data field is used to configure which HP Systems Insight Manager servers are trusted by the System Management Homepage. For more information, refer to Security - Trusted Management Servers
Why can't I use a Windows 2003 Certificate Authority to grant my third-party certificate into the System Management Homepage?
Solution: To use a Windows 2003 Certificate Authority to create a certificate for System Management Homepage: Create the PKCS#10 data packet by clicking Settings System Management Homepage Security Local Server Certificate page. Press the Ctrl+ C keys to copy the data into a buffer. Navigate to http://W2003CA/certsrv.
Note: Replace W2003CA with the name of your Windows 2003 Certificate Authority system. Select Request a certificate. Select Advanced certificate request. Select Submit a certificate request by using a base.... Press the Ctrl+ V keys to paste the PKCS#10 data into the field.
From your Windows 2003 Certificate Authority system: Click [Start] → [All Programs] → Administrative Tools → Certification Authority. Click CA (Local) → W2003CA/certsrv, where W2003CA with the name of your Windows 2003 Certificate Authority system.. Issue the pending request certificate
Navigate to http://W2003CA/certsrv.
Note: Replace W2003CA with the name of your Windows 2003 Certificate Authority system. Select View the status of a pending certificate request. Select Base 64 encoded and Download certificate (not certificate chain). The file download is certnew.cer. Rename certnew.cer to cert.pem.
 |  | Other Problems |
Why can't I install the System Management Homepage on my system?
Solution: The System Management Homepage install requires a Java version that requires at least 256 colors to load.
Why do I get an error indicating the page cannot be displayed when I click the Management Processor link?
Solution: The administrator for the management processor has configured the Web server on the management processor to use a port other than port 80. The System Management Homepage does not currently have access to that parameter and assumes the management processor is on port 80.
Why can I not install on Linux when I am not root?
Solution: You must be logged in as root for System Management Homepage to have the proper access rights.
Note: You cannot su- to mimic root access for reinstall on United Linux 1.0/ SuSE SLES 8.
Why can I not install System Management Homepage on my version of Linux?
Solution: The versions of Linux that the System Management Homepage supports each require their own specific set of RPM packages. To see which RPM packages are missing on your system, install the System Management Homepage RPM in verbose (non-silent) mode, and any missing RPM packages will be listed.
Why can I not access the System Management Homepage after I installed some McAfee products?
Solution: McAfee has announced (through its website) an incompatibility that might render its own products and several Web-based products unusable. The list of incompatible products includes the HP System Management Homepage. This incompatibility can be seen on Windows 2000. The McAfee website described the issue: "Internet connectivity issues caused by incompatible Layered Service Providers: Product Versions All McAfee VirusScan 7 versions All McAfee Internet Security 5 versions All McAfee Firewall 4 versions
Operating Systems Windows 2000/XP Windows 98/Millennium System Information
Connection to the Internet: You might experience Internet connectivity issues when McAfee Products are used in conjunction with other applications, which include a Layered Service Provider (LSP.) Most applications, which include a LSP, do coexist successfully. Those that are known to conflict with the McAfee LSP are listed below:”
McAfee is a business unit of Network Associates, Inc.
|