Jump to content

Drew

Members
  • Posts

    4
  • Joined

  • Last visited

    Never

Reputation

1 Neutral
  1. Hi The default profile of the network agent uses the internal host name of the KSC server. I have created a network profile to switch to using the external FQDN when the default gateway on the PC is 172.16.1.1, but it does not change to using the external FQDN. When the network changes, the network agent continues to try and contact the server on the internal address.Please see below for confirmation of settings. The PC is Win 10. I have changed the server name below for security C:\Program Files (x86)\Kaspersky Lab\NetworkAgent>ipconfig Windows IP Configuration Ethernet adapter Ethernet: Connection-specific DNS Suffix . : IPv4 Address. . . . . . . . . . . : 172.16.1.103 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 172.16.1.1 C:\Program Files (x86)\Kaspersky Lab\NetworkAgent>klnagchk.exe Starting utility 'klnagchk'... Checking command line options...OK Initializing basic libraries...OK Current device is 'Test-PC' Network Agent version is '10.5.1781 (a)' Reading the settings...OK Settings verification...OK Network Agent settings: Administration Server address: '<internal name>' Use SSL: 1 Compress traffic: 1 Numbers of the Administration Server SSL ports: '13000' Numbers of the Administration Server ports: '14000' Use proxy server: 0 Administration Server certificate: available Open UDP port: 1 Numbers of UDP ports: '15000' Profiles Profile name: 'New profile' Administration Server address: '<external name>' Use SSL: 1 Compress traffic: 1 Numbers of the Administration Server SSL ports: '13000' Numbers of the Administration Server ports: '14000' Use proxy server: 0 Switch to out-of-office mode: 0 Locations Location name: New description Profile to use: "New profile" Condition: default gateway, one of 172.16.1.1 Synchronization interval (min): 1 Connection timeout (sec): 30 Send/receive timeout (sec): 180 Device ID: <device ID> Attempting to connect to Administration Server...Transport level error while connecting to http://<internal name>:13000: general error 0x502. An attempt to send ICMP packet to the Administration Server Sending ICMP packet <internal name> [192.168.1.99]...Error - Sent = 3, Received = 0 Attempt to connect to the Network Agent...OK Network Agent is running Receiving the Network Agent statistical data...OK Network Agent statistical data: Total number of synchronization requests: 4 The number of successful synchronization requests: 4 Total number of synchronizations: 0 The number of successful synchronizations: 0 Date/time of the last request for synchronization:2020/04/21 07:52:41 GMT (2020/04/21 09:52:41) Deinitializing basic libraries...OK Thanks
  2. Hi Thanks this information is really useful! Can you please confirm one more thing for me? If KSC says that a device was on line did it “see” the device ID? ie. was there communication between the network agent and KSC and the device ID was checked. Or is there a possibility that KSC marks the device on line if it can resolve its host name only? Regards,
  3. Hi, Thanks for the reply, but as mentioned the laptop has been stolen so we cant run the utility on it. The laptop connected to the network via VPN as mentioned the client is convinced that KSC has incorrectly identified the laptop and that it was not the stolen one. There mus surely be some unique key that the network agent uses when it connects to KSC? Regards,
  4. I have a client who had a laptop stolen a few months ago. The laptop was never removed from KSC. Afew days ago the laptop connected to KSC. My client is convinced that the stolen laptop was not the PC that connected to KSC, but in fact it was one of the other PC’s in the organization, and that KSC incorrectly identified it through a bad or incorrect DNS entry. How can I prove that it was definitely the stolen laptop that connected to KSE? Version: 10.5.1781 Thanks Drew
×
×
  • Create New...