- 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':
- Servers that do not patch have the full domain name (FQDN) displayed, while servers that work just have the server name.
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.
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.
This issue with the remediation is a customer defect and has been resolved, however, the fix will be released with LanGuard 12.6.
The release candidate was launched into the GFI Insider Group on December 7, 2021. The public release will follow after some days.
If you would like to get updates or access to new releases of GFI LanGuard, please Join the GFI Insider Program. You will require a valid Gmail account to join the group.