Phone Lines icon GFI Support Home

Articles in this section

See more

Defect: Patching fails with error 'The network path was not found' on server with FQDN

Author: Rama Ali Updated

Overview

  • User experiences remediation issues when patching servers/desktops/laptops with Languard. 
  • Gets a fail message saying 'The network path was not found' or 'The network name was not found':Capture_censored__1_.jpg
  • Servers that do not patch have the full domain name (FQDN) displayed, while servers that work just have the server name.

 

Solution

Diagnosis

When a user runs manual remediation for a target without FQDN in the DNS records, the remediation fails because LanGuard sees the target to be an FQDN of another domain. You can verify this by running nslookup for the hostname to confirm if hostnames resolve correctly.
Running auto-remediation for the same target works without FQDN in DNS. Let's say you remediate target A and it is in the abc domain (A.abc), it fails with an error A.xyz (xyz is another domain being scanned with LanGuard also). This error isn't seen when you perform auto-remediation for A. If the wrong FQDN A.xyz is placed in the DNS record, it resolves the issue.
Expected behavior:
Manual remediation should work without putting a wrong FQDN entry in the DNS records. Or at least, LanGuard should give an error for the correct FQDN which is missing.

Solution

This issue with the remediation is a customer defect and has been resolved in LanGuard 12.6. 

Follow the steps to upgrade LanGuard to the latest version.

Was this article helpful?
0 out of 0 found this helpful

Related articles