futureman0
asked on
Direct Acccess Troubleshooting
I recently setup a Windows Server 2012 R2 machine for direct access. I'm testing it on two client machines at the moment. Both are Windows 8.1 Enterprise, one can connect with out a problem and the direct access connection appears to work fine. The other not so much. Both are using the same wifi network and used the same installation media for 8.1 Enterprise.
During my troubleshooting on the client having problems, I ran Get-DAConnectionStatus in powershell. This returns "Network Connectivity Assistant is stopped or not responding". I've tried to manually start the service it still won't start. From my research this is caused when an Pro, non-Enterprise, client tries to use direct access - but in my case both are enterprise.
This is what I've tried so far
Any idea what else to try?
During my troubleshooting on the client having problems, I ran Get-DAConnectionStatus in powershell. This returns "Network Connectivity Assistant is stopped or not responding". I've tried to manually start the service it still won't start. From my research this is caused when an Pro, non-Enterprise, client tries to use direct access - but in my case both are enterprise.
This is what I've tried so far
Initially it was running 8.1 Pro, but apparently direct access is only for Enterprise
I upgraded the machine to enterprise, same error message
Then I did a clean install and formatted the computer and installed 8.1 Enterprise, same error as before
Any idea what else to try?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER