There's a few reasons it could be detected while off the network.
Make sure you don't have the NLS server's record published in external DNS and that the server is not accessible via the Internet. Most people don't accidentally do that, but still it should be mentioned as a possibility.
The more common reason is that the NLS server was not added as an exemption in the NRPT table when DirectAccess was setup.
In the Remote Access Management console, Configuration view, edit the "Infrastructure Server Setup" (Step 3) and add the FQDN for each NLS. Do not specify a DNS server. That will effectively create an NRPT exemption so that the NLS cannot be reached when the DirectAccess client is connected remotely.
There's some good screenshots, and information, over at Richard Hicks's blog post:
Those would be my best guesses based on the description.
- Edited by RhinoBytes 13 hours 38 minutes ago Added information from Richard Hicks's blog
There's a few reasons it could be detected while off the network.
Make sure you don't have the NLS server's record published in external DNS and that the server is not accessible via the Internet. Most people don't accidentally do that, but still it should be mentioned as a possibility.
The more common reason is that the NLS server was not added as an exemption in the NRPT table when DirectAccess was setup.
In the Remote Access Management console, Configuration view, edit the "Infrastructure Server Setup" (Step 3) and add the FQDN for each NLS. Do not specify a DNS server. That will effectively create an NRPT exemption so that the NLS cannot be reached when the DirectAccess client is connected remotely.
There's some good screenshots, and information, over at Richard Hicks's blog post:
Those would be my best guesses based on the description.
- Edited by RhinoBytes Wednesday, September 09, 2015 5:43 PM Added information from Richard Hicks's blog
There's a few reasons it could be detected while off the network.
Make sure you don't have the NLS server's record published in external DNS and that the server is not accessible via the Internet. Most people don't accidentally do that, but still it should be mentioned as a possibility.
The more common reason is that the NLS server was not added as an exemption in the NRPT table when DirectAccess was setup.
In the Remote Access Management console, Configuration view, edit the "Infrastructure Server Setup" (Step 3) and add the FQDN for each NLS. Do not specify a DNS server. That will effectively create an NRPT exemption so that the NLS cannot be reached when the DirectAccess client is connected remotely.
There's some good screenshots, and information, over at Richard Hicks's blog post:
Those would be my best guesses based on the description.
- Edited by RhinoBytes Wednesday, September 09, 2015 5:43 PM Added information from Richard Hicks's blog