DirectAccess - Win7 client - Corporate network names cannot be resolved

I have a single Windows Server 2012 R2 Essentials with a single ethernet connection sitting behind a NAT firewall with ports 80 and 443 open to the server.

I've run through the DirectAccess wizard and almost have it working but am stuck. 

Windows 7 Ultimate client with DirectAccess Connectivity Assistant 2.0 installed and displaying " Corporate network names cannot be resolved". 

It looks like it might be a certificate issue as the output of netsh name show policy has a blank "Certification authority". The DNS suffix DirectAccess DNS Server is showing the correct IPv6 entry though.

Anyone shed any light on this? 

Thanks!


June 30th, 2015 12:26am

OK, so I've now got the IP-HTTPS tunnel up and the client is connected and authenticated. I'm still not getting DNS resolved though.

Where do I start troubleshooting this?

Thanks 

Free Windows Admin Tool Kit Click here and download it now
June 30th, 2015 3:19pm

Hi,

According to your description, my understanding is that DirectAccess wizard has been completed, but Windows 7 Ultimate client with DirectAccess Connectivity Assistant 2.0 installed and displaying " Corporate network names cannot be resolved".

This error message indicates that Windows cannot resolve names of resources on the corporate network. You may try to reference official documents for further troubleshooting.

General Methodology for Troubleshooting DirectAccess Connections:
https://technet.microsoft.com/en-us/library/ee624058(v=ws.10).aspx

If the problem still exits, reference Problems with DirectAccess Connections:
https://technet.microsoft.com/en-us/library/ee844125(v=ws.10).aspx

Best Regards,
Eve Wang
July 1st, 2015 10:15pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics