SUMMARY
In some cases, it is necessary to validate the machine information from which certain connections to Strategy Intelligence Server were created. This information can be obtained either two ways;
1.-Executing reports from Enterprise Manager that contain session information, such as ‘102. Recent Sessions, Users’, that contain the out of the box Enterprise Manager attribute ‘Client Machine’ which will display the network address of the session.
2.-Accesing the ‘User Connections’ monitor within Strategy Developer under ‘Administration’ -> ‘System Monitors’.
Additionally, there are several types of formats for Network Address that can be seen within the User Connections monitor or on Enterprise Manager reports utilizing the attribute ‘Client Machine’. These include:
This indicates a web session created internally by a Strategy Web client to connect to the Intelligence Server. These sessions are used to retrieve the project access information and then closed immediately after, logged with a Network Address of ‘tempclient’.
Is the IPv6 address equivalent to the IPv4 127.0.0.1 address. Anything in the FE80::/10 range is a link-local address,
A connection from a client machine with Strategy Developer.
A connection from a configured Strategy Scheduler.
The FQDN of the machine used for the session.
With the transition to IPv6 from IPv4, the loopback address has been changed to 0:0:0:0:0:0:0:1 from 127.0.0.1. These entries indicate a localhost connection.
*Addresses in the fe80::/10 range are link-local addresses. These addresses are only significant to the link on which they reside. A device with multiple interfaces may have the same address as well as the same link-local network on all its interfaces.*
Related KB articles
KB32951 When having "Log in, then show the projects accessible by the supplied login" in Strategy Web 9.x the log in process takes a long time or longer than when displaying projects first.