Home
  •  

NLS URL Availability

Microsoft.Windows.RemoteAccess.Monitor.DA_NLS_HEURISTIC_URL_AVAILABLE (UnitMonitor)

There is no response from the network location server URL. DirectAccess connectivity might not work as expected, and DirectAccess clients located inside the corporate network might not be able to reach internal resources

Knowledge Base article:

Summary

There is no response from the network location server URL. DirectAccess connectivity might not work as expected, and DirectAccess clients located inside the corporate network might not be able to reach internal resources.

Causes

1. The network location server website is unavailable.

2. Network issues are causing connection issues.

3. The network location server is not running on a highly available server.

4. The IIS server is unavailable, or there is no response from the network location server URL.

Resolutions

1. Configure the network location server on a server that is highly available to clients on the internal network.

2. If the network location server is running on the Remote Access server, ensure that IIS is running, and that the URL is available.

Element properties:

TargetMicrosoft.Windows.RemoteAccess.Class.NetworkLocationServer
Parent MonitorSystem.Health.AvailabilityState
CategoryCustom
EnabledTrue
Alert GenerateTrue
Alert SeverityError
Alert PriorityNormal
Alert Auto ResolveTrue
Monitor TypeMicrosoft.Windows.RemoteAccess.Monitor.Heuristic.MonitorType
RemotableTrue
AccessibilityPublic
Alert Message
NLS URL unreachable

Error Description - {0}
Error Cause - {1}
Error Resolution - {2}
RunAsDefault

Source Code:

<UnitMonitor ID="Microsoft.Windows.RemoteAccess.Monitor.DA_NLS_HEURISTIC_URL_AVAILABLE" Accessibility="Public" Enabled="true" Target="Microsoft.Windows.RemoteAccess.Class.NetworkLocationServer" ParentMonitorID="Health!System.Health.AvailabilityState" Remotable="true" Priority="Normal" TypeID="Microsoft.Windows.RemoteAccess.Monitor.Heuristic.MonitorType" ConfirmDelivery="true">

  <Category>Custom</Category>

  <AlertSettings AlertMessage="Microsoft.Windows.RemoteAccess.Monitor.DA_NLS_HEURISTIC_URL_AVAILABLE_AlertMessageResourceID">

    <AlertOnState>Warning</AlertOnState>

    <AutoResolve>true</AutoResolve>

    <AlertPriority>Normal</AlertPriority>

    <AlertSeverity>Error</AlertSeverity>

    <AlertParameters>

      <AlertParameter1>$Data/Context/DataItem/Property[@Name='ErrorDesc']$</AlertParameter1>

      <AlertParameter2>$Data/Context/DataItem/Property[@Name='ErrorCause']$</AlertParameter2>

      <AlertParameter3>$Data/Context/DataItem/Property[@Name='ErrorResolution']$</AlertParameter3>

    </AlertParameters>

  </AlertSettings>

  <OperationalStates>

    <OperationalState ID="UIGeneratedOpStateId4c38a629ffe9475cb38b831d1f4c8a95" MonitorTypeStateID="Error" HealthState="Error"/>

    <OperationalState ID="UIGeneratedOpStateId149d375ce0344c3ca5a3188dcf38d239" MonitorTypeStateID="Warning" HealthState="Warning"/>

    <OperationalState ID="UIGeneratedOpStateIde4e51ffe11c14744b93e64a870c23fd8" MonitorTypeStateID="Healthy" HealthState="Success"/>

  </OperationalStates>

  <Configuration>

    <Interval>300</Interval>

    <SyncTime/>

    <ComponentName>Network Location Server</ComponentName>

    <HeuristicId>2148335618</HeuristicId>

  </Configuration>

</UnitMonitor>