Since upgrading a 8.6 LANDesk core to 8.7 SP4 (and changing the core's IP address to one in another segment), we're having problems with remote control from the web console. I'm not sure if this is an inventory updating issue or a remote control/web console issue. We are using integrated security. The agent is configured to run inventory upon IP address change.
The problem I'm having with several machines is that I can successfully remote control them from the 32-bit console on the core and from my own machine, but not from the web console on the core (or anywhere else). When remote control successfully connects via the 32-bit console, it tries the inventoried IP, but then tries an IP that is different than the one shown in Inventory from either console, and the Last Updated by Inventory date displayed in either console is current. The inventoried IP from a current inventory scan appears to be incorrect as I can ping these machines from the core by machine name and get the correct address, i.e., the one that the 32-bit console switches to as viewed in the Remote Control window.
The problematic machines showing an incorrect IP address in inventory after a current inventory scan all seem to be in the same IP range, so far, and all switch to a different IP range when using remote control from the 32-bit console, i.e, a 10.99.4.x IP is tried first, but then remote control via the 32-bit console connects to a 10.99.5.x or 10.99.6.x address, as viewed in the Remote Control window.
As I've said, I'm not sure if this is a remote control issue, inventory issue or some failing with the web console, so I've attached today's IIS log. The failed web console remote control attempts in the log are coming from users TALX\csk2 from the core and TALX\rfm from another workstation (TALX\csk2 is the userID for a successful 32-bit console remote control session.) I'm also curious to understand how the 32-bit console would "know" the correct IP address to change to when it's not the address showing up in inventory, whereas the web console only tries to use the IP address shown in inventory.