transport layer generic error

[aseman.ab]

hi

when I send licenses key task  for clients

I have this error

transport layer generic error

what is this?

what I do?

[aseman.ab]

hi please help me

[aseman.ab]

hi

when I send licenses key task  for clients

I have this error

transport layer generic error

what is this?

what I do?

[Victor C.]

Hi,

 

Transport layer generic errors are referring to connectivity issues. In order to deploy licenses to devices remotely from KSC, please ensure Network agent is installed and running on your client devices.

If require to troubleshoot Network agent connection to KSC server, please run Klnagchk. A utility for analyzing Network agent connection settings
http://support.kaspersky.com/9292
Graphic utility for Network Agent management - klcsngtgui
http://support.kaspersky.com/9319

I hope this helps.

[Or.kahn]

Hi,

 

Transport layer generic errors are referring to connectivity issues. In order to deploy licenses to devices remotely from KSC, please ensure Network agent is installed and running on your client devices.

If require to troubleshoot Network agent connection to KSC server, please run Klnagchk. A utility for analyzing Network agent connection settings
http://support.kaspersky.com/9292
Graphic utility for Network Agent management - klcsngtgui
http://support.kaspersky.com/9319

I hope this helps.

HI,

It is ok with klcsngtgui and Klnagchk but same error (transport layer generic error) when I send licenses key task  for clients.

 

[Victor C.]

Hi,

From information provided it seems that Network agent is connecting to KSC server. Now verify if KSC server is able to communicate to affected device by trying to ping and telnet over ports 13000 and 14000 to the device. This will ensure that outbound and inbound connection is working properly.

If workstation failed to connect to the Administration Server at <address_or_name>:<port> because the Administration Server is unavailable at this address.

Possible reasons:

      1. Connection is blocked by a firewall. The firewall may be installed on the problem workstation, or on the Administration Server host <address_or_name>, or somewhere between them;

      2. The Administration Server has another address or port;

      3. The Administration Server failed to initialize or isn't running on the host <address_or_name>;

      4. Address <address_or_name> cannot be resolved properly on the workstation side.

To resolve the problem try the following steps.

- On the computer with the Administration Server installed run netstat to check if the Administration Server really listens to TCP port <port>.

netstat -a -o -n -p TCP

Name of the Administration Server process is klserver.exe. If the Administration Server failed to open port 13000 the Kaspersky Event Log in .csv or .xml format from the computer with the Administration Server installed is required. 

- On the affected workstation try to ping the <address_or_name> with ping utility and see which ip address the utility shows. Then on the computer with the Administration Server installed run ipconfig utility and make sure that returned ip address is equal to one the ping utility has returned on the affected workstation.

- On the affected workstation try to connect to the Administration Server with the akconnect utility:

akconnect <address_or_name> <port>

 

If it fails then it is possibly a firewall issue. Look into firewall logs or try to temporarily turn off firewall and see if the problem can be reproduced without the firewall. Make sure that the firewall has correct rules.

If require further troubleshooting, please contact Kaspersky Business Support by opening a web ticket through the company's account portal: https://companyaccount.kaspersky.com/account/login. If none of the above solutions apply, the case should require a Kaspersky Support assistance.

I hope this helps.