This can happen if something has changed with the GPOs that DirectAccess uses. There should be a "DirectAccess Client Settings" and a "DirectAccess Server Settings" GPO linked at the top of your domain, unless you specified otherwise during the wizards.
Check and see if those exist, and if they are populated with settings. Particularly if those GPOs get deleted by somebody accidentally, that can cause this kind of behavior.
Hi, Yes the GPO's were there and appear to be correct.
I have removed direct access from the server totally, wait a few hrs for group policy to apply etc, re installed direct access and still get the same error so it looks like maybe the server is causing this error to occur. Is there any logs etc that
can be checked, its very vague and very poor error reporting on Microsoft's side as it does not even give an error code.
Microsoft is conducting an online survey to understand your opinion of the Technet Web site. If you choose to participate, the online survey will be presented to you when you leave the Technet Web site.