Connection Failed Physical Error Kaspersky Administration Kit
Contents |
Kit 8.0→Server Management Product Select Knowledge Base Installation and Removal License Management General Info Updating Server Management Host Management Tools and Utilities Reports and Notifications Troubleshooting Downloads & Info System Requirements Common Articles How-to Videos Forum Contact
Kaspersky Connection Failed Physical Error Network Agent
Support Safety 101 Kaspersky Administration Kit 8.0 Why Administration connection to administration server failed kaspersky kit Agent fails to establish connection with the Administration Server Back to "Server Management" 2013 Jul 11 ID: 3250
Connection Failed Physical Error Kaspersky Update
Possible signs of a connection loss between the Network Agent and the Administration Server are as follows:- policies do not apply to client computers;- manual synchronization with a client computer fails;- pale computer icon(s) in the Administration Console;- the Connecting to Server field does not contain the current date and time (+/- 15-30 minutes) (for a running workstation).Use the klnagchk.exe utility to find out why the connection fails. This utility has been developed to analyze connections between the Network Agent and the Administration Server.The utility should be run on problematic computers from the Network Agent setup directory (C:\Program Files\Kaspersky Lab\NetworkAgent 8) under a local administrator account. It is recommended to save its results into a log file.A connection may fail due to one of the following reasons: There is no Network Agent installed on the client computer. An incorrect Administration Server address or port was specified during the local installation of the Network Agent on the client computer. Kaspersky Network Agent service is not running on the client computer. Kaspersky Administration Server service is not running on the Administration Server. There are several workstations with the same name within the network and a wrong workstation has been dragged into the group (by mistake). Use the Search command in the Server context menu. Select Find client computers and try to find computers with the identical name – enter the PC name with *. For example, COMPUTER*. This client computer is already connected to another Administration Server within the same Windows network. The client computer is currently switched off. The Administration Server is inaccessible from the client computer. Use ping command on the client computer to verify it. TCP 13000 and/or 14000 ports are blocked on the Administration Server. You can check if the ports are open using the following utilities: fpor
the Community! Creating your account only takes a few minutes. Join Now ◄ Prev 1 2 3 4 Next ► 96 Replies Cayenne OP Garnock12 Mar 6, 2015 at 4:58 UTC OK I have successfully successfully deployed the SP1 in my lab - moving it to production today!! 1 Cayenne OP Garnock12 Mar 6, 2015 at 5:48 UTC OK the move to production is proceeding perfectly - so to update my proceedure I performed the followingExported http://support.kaspersky.com/us/3250 exclusions and allowed apps from the policy in the container with my PCs (I have separate containers for servers and workstations and I also break down my workstations by department.Deleted the workstation policyBacked up the KESUninstall the KES server - rebootUninstall v8 for servers from the KES server - rebootRun the installer - select extract from the opening screenOnce https://community.spiceworks.com/topic/815060-kaspersky-endpoint-security-10-service-pack-1-for-windows?page=3 files are extracted I ran setup.exe from the server folder in the extracted filesRestore the KES server settingsInstall the plugins for KES10 and KAV8 for serversReboot - this reboot took a little longer while all the new services startedLaunch KES and run through the quick start wizardLoad additional license keysMove the KES10 policy from "managed computers" to my "workstation container"Import the apps and exclusions into the policy (I appended so I could keep the default entries)Deploy v8 for servers to the KES serverDeploy the network agent to the PC'sDeploy KES v10 SP1 to the PC'sCleaned up the expanded folders and backups. 0 Serrano OP TagYourIT Mar 18, 2015 at 4:39 UTC I updated to SP1. Some of my clients are having issues with getting updates. Everything was running awesome with MR1. Now with SP1 the install updates tasks fails on these clients due to a "physical connection error" or/and "error interacting with security console." Not sure how this is possible when everything was great before. No hardware changes either... During trouble shooting:
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a https://www.experts-exchange.com/questions/22975513/Kaspersky-administration-kit-update-error.html Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Kaspersky administration kit update error Want to Advertise Here? Solved Kaspersky administration kit update error Posted on 2007-11-21 Anti-Virus Apps 1 Verified Solution 3 Comments 6,916 Views Last Modified: 2013-11-22 I have connection failed Kaspesky corporate eddition, I am trying to update administation kit, the updates work but it do not finish and give me the following error: Failed Severity: Error Application: Kaspersky Administration Kit Version number: 6.0.1565 Task name: admin update Computer: Administration Server