Task Servers are unable to register to themselves

Products

• Client Management Suite

Issue/Introduction

When Task Servers are unable to register themselves the Sym Agent logs show a Warning error like this:

Task Server Connection: Failed to request 'http:// <servername>:80/Altiris/ClientTaskServer/Register.aspx?lastResort=true&resTypeGuid={493435F7-3B17-4C4C-B07F-C23E7AB7781F}&sysType=Win64&version=8.6.4286&resourceGuid=xxxxxxxx-6afa-464c-xxxx-8a0245738042&crc=00080006000010BE', error: No connection could be made because the target machine actively refused it (0x8007274D)

You get the below message if you try to open the URL mentioned in the above log message:

<This page can't be displayed>

When you try accessing the lIS welcome page using the server name (for example, http://servername ), it threw the similiar error message like:

You cannot open the welcome page using this site server name.

Environment

ITMS 8.x

Resolution

First, look at all listeners using:

netstat -an

You may notice an entry for port 80 for 127.0.0.1, but not for the actual IP address of the Task server ( site server ) — nor for 0.0.0.0:80, which would be all IP addresses:

TCP 127.0.0.1:80 0.0.0.0:0 LISTENING

To fix this :

Open the Command prompt and run the below commands to verify and add the listener with the Task server  IP address:

C:\>netsh
netsh>http
netsh http>show iplisten

IP addresses present in the IP listen list:

127.0.0.1

netsh http>add iplisten ipaddress=192.0.2.2 ( here you need to type your Task server ip on which you are facing this issue ) 

IP address successfully added then:

netsh http>show iplisten

IP addresses present in the IP listen list:

127.0.0.1
192.0.2.2

netsh http>exit

C:\>iisreset

Attempting stop...
Internet services successfully stopped
Attempting start...
Internet services successfully restarted

Confirm if the port 80 is listening properly:

C:\>netstat -an
 TCP 192.0.2.2:80 0.0.0.0:0 LISTENING
 TCP 127.0.0.1:80 0.0.0.0:0 LISTENING

Or, another approach is to remove the 127.0.0.1 listener so there were no explicit IP addresses configured for the HTTP, which would have meant it would have listened on all IP addresses:

C:\>netsh
netsh>http
netsh http>show iplisten

IP addresses present in the IP listen list:

127.0.0.1

netsh http>del iplisten ipaddress=127.0.0.1

IP address successfully deleted

netsh http>exit

C:\>iisreset