NAT64 connectivity failed. DirectAccess clients might not be able to access IPv4-only servers in the corporate network.
NAT64 connectivity failed. DirectAccess clients might not be able to access IPv4-only servers in the corporate network.
1. NAT64 is not enabled on the server.
2. The NAT64 server cannot be reached.
3. Web probe addresses cannot be reached.
1. Verify that NAT64 is enabled on the server.
2. For native IPv6 connectivity, verify that the NAT64/DNS64 prefix is configured in the DirectAccess settings.
3. In the Remote Access Server Setup Wizard, ensure that the default NRPT entry points to the internal address of the NAT64/DNS64 server.
Target | Microsoft.Windows.RemoteAccess.DirectAccessServer.Class | ||
Parent Monitor | System.Health.AvailabilityState | ||
Category | Custom | ||
Enabled | True | ||
Alert Generate | True | ||
Alert Severity | Error | ||
Alert Priority | Normal | ||
Alert Auto Resolve | True | ||
Monitor Type | Microsoft.Windows.RemoteAccess.Monitor.Heuristic.MonitorType | ||
Remotable | True | ||
Accessibility | Public | ||
Alert Message |
| ||
RunAs | Default |