An installation of SCSP agent succeeds, but does not register with the managment server. In the SISIPSService.log, you can see the following type of message:
Management Server URL : https://<server_ip:port>/sis-agent/
Curl Error: AGENT COULDNT CONNECT. Verify server IP&sep1;port and server is running.
This problem may be caused by having multiple NICs (network adapters), or if you have multiple IP addresses assigned to one NIC. As stated in the Installation Guide, if your network card is bound to more than one IP address, the agent uses the first IP address on the network card.
If you look at the first line in the agentinitial.log and the SISIPSService.log on the agent, you will see the IP address being used.
Change the order of the NICs so that the IP address you need to use for SCSP as at the top of the list. You can do this from the Advanced Settings in Network Connections.
Move the network adapter which is configured with the relevant IP address to the top of the list. In this example, the "Local Area Connection 5" for the network adapter bound to the relevant IP address is moved to the top of the list.
Then, either re-install the agent, or manually register the agent to the management server using the sisipsconfig command.
The screenshots above are from Windows Server 2003, but the same applies to Windows Server 2008.
Note: If you try the “sisipsconfig –t” command to test connectivity from the agent system to the management server, you may see another error stating “Could not connect to server: Verify the agent certificate matches the server.” If it’s the case that the wrong IP address is being tried, then you will get this message even though you are actually using the correct certificate file.
Imported Document ID: TECH161364
Subscribing will provide email updates when this Article is updated. Login is required.