IP Binding on PSP 7.2 disabled but working

[Matt Duncan_1]

I have an issue with Windows 2000 and the PSP 7.2. After a fresh install (no previous PSP on the system) the server will start all the PSP tools successfully but when I attempt to browse to the Homepage from a remote system the page is not displayed. If I try to access the page from the local machine it works.

Now here's the fun part...if I restart the HP Homepage service the home page becomes available to remote systems. If I reboot the box I'm back to square one with the local system being able to access the home page but not remote systems.

It's as if the IP Binding is being enabled but not configured. We don't use IP Binding on the PSP and so we don't enable it or configure it. Has anyone else experienced this issue and if so how did you fix it?

[Ole Thomsen_1]

I have a similar problem on the HPSIM server.

When I reboot the server software repository stops responding, and i cannot login to the homepage over the network.

After logging in locally and confirming the security setup (no changes) everything is fine again. I guess it starts working because the service is restarted during this operation.

This happens with ip binding on and ip binding off, no difference

[Rich Purvis]

Matt,
I am not sure that this is an IP Binding problem - no doubt odd behavior. What you are describing sounds more along the lines of the IP Restriction - is that configured at all?
Also, are you running any kind of VM software in this setup? Virtual Machine software can sometimes cause odd behavior like this.

-Rich

[Jason Frei]

I have having the same problem with the PSP 7.3. Everytime I reboot, the server stops listening on ports 2301/2381 on the Prod NIC. However, the localhost is still listening on these ports. If I restart the Systems Management Homepage service then it starts listening on the Prod network again as well as the localhost.

[Matt Duncan_1]

I found the apparent solution to the issue. If you have a server set up to use DHCP on it's NICs the HP agents start up before the DHCP server assigns an address. This causes the HP Management Homepage service to bind to the loopback address of 127.0.0.1. You can check what IP the "web agent" is bound to by opening the config file c:\hp\hpsmh\conf\smhpd.conf. This file is rebuilt every time the HP Management Homepage service is restarted. If you have the NICs in your server set up for DHCP try setting a static IP, reboot the server, and see if the agents are available.
The other quirk I found was more of an issue with one of our support personell than it is HP's agents. If you use Hosts files and enter your server name and IP in them (don't ask me why one of my Engineer's did this) then you need to verify that the Hosts file contains the accurate IP. If the IP is not correct then the HP agents will bind to the incorrect IP and not be available. Correct the IP address in the Hosts file, run an "ipconfig /flushdns", and restart the HP agents. That should be all that's required to get the agents to bind to the correct IP.