HP Systems Insight Manager - Manual (Page 78)

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.
13.13.4.3 When I use the IP Restricted Login feature, 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?
Enter 127.0.0.1 in addition to the IP addresses of the server if you intend to restrict the local
machine. The address 127.0.0.1 is always permitted in the Include section, so it is only
restricted if it is explicitly placed in the Exclude section.
13.13.4.4 Although an IP restriction is configured, localhost access is not being denied. Why is this
happening?
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 local host access. If you do need to
block localhost access, enter 127.0.0.1 into the Exclude field under IP Restriction.
13.13.4.5 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.
As a precaution against users unintentionally locking themselves out of HP SMH access,
localhost requests are not denied when the local IP addresses are not mentioned in the Include
list. If 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.
13.5 Sign In Problems
13.13.5.1 After signing onto the Windows operating system on a ProLiant or Integrity server running HP
SMH Version 2.1.3 (or later), the ROTATELOGS.EXE command prompt appears on the screen
if SMH is configured to allow interaction with the desktop. When this occurs, one or two smaller
command prompt windows appear with messages similar to the following:
(drive) :\hp\hpsmh\bin\rotatelogs.exe
The command prompt window messages do not affect the performance or functionality of the
server or of SMH and can be ignored.
Any ProLiant or Integrity server configured with Windows 2000 Server or Windows Server
2003 (any edition) and HP SMH Version 2.1.3 (or later) when SMH is allowed to interact
with the desktop can be affected.
To prevent HP SMH from interacting with the server desktop, perform the following:
1. Click Start
→Programs→Administrative Tools→Services
2. Click HP System Management Homepage Properties.
3. Click the Log On tab.
4. Deselect Allow service to interact with desktop.
5. Click Apply and then click OK.
6. Restart the HP System Management Homepage service.
13.13.5.2 I gave a user group defined by Windows, such as Backup Operators, Administrator, Operator
and User , privileges through the HP SMH User Groups settings page. However, users in that
group cannot sign in or do not have the correct privileges in HP SMH.
HP SMH only recognizes four user groups defined by Windows: Administrators, Users, Guests
and Power Users. Other groups defined by Windows, such as Backup Operators, are not
recognized.
NOTE: On Linux, the group must be previously created using system tools as groupadd.
13.13.5.3 When trying to sign in to HP SMH on a Windows system using an administrative account
defined in the Backup Operators group, the sign in fails.
78 Troubleshooting topics