Solved

Microsoft DirectAccess + Surface Pro 4s

Posted on 2016-08-16
6
98 Views
Last Modified: 2016-08-22
Hello All --

I am trying to test out DirectAccess with our Surface Pro 4 tablets.  I've gotten everything setup and it even connects via IP-HTTPS as per the screenshot:

Capture.PNG
I tried a few troubleshooting tools and guides (making sure domain firewall profile is applied to the internal network interface, pulling logs from the client, making sure port 443 is open on the firewall, etc) with no success.  It seems like the client is able to successfully connect but no data is being returned.  

Back tracking a bit, we have the following environment.  

Environment:
DirectAccess Server (Windows 2012 R2, 2 Network Interfaces with 1 DMZ and 1 Internal)
 * Public GoDaddy cert for IP-HTTPS
 * Self-signed the NLS
DirectAccess Client (Surface Pro 4 with Windows 10 Enterprise)
Cisco Meraki Environment (IPv4 only)

The only thing I can think of now is that it doesn't work in our environment since we have an IPv4 only environment.  The meraki firewall (MX) only passes IPv6 traffic in passthrough mode (which it is not).  However, when i'm reading the articles online, it appears that IPv6 just has to be enabled on the client and not the internal environment itself for DirectAccess to work.  Any one can clarify?  Any other troubleshooting steps I can take?

Thanks!
0
Comment
Question by:Edward Cho
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 2
6 Comments
 
LVL 58

Expert Comment

by:Cliff Galiher
ID: 41758590
DirectAccess does not support software that requires IPv4 end to end. The client end must not only have IPv6 enabled, but any software on the client end must also support IPv6. On the server end, if you are not gong to use IPv6, you must configure some sort of 6 to 4 topology.
0
 
LVL 3

Author Comment

by:Edward Cho
ID: 41759542
Thanks for the reply.  

I thought Server 2012 direct access server has built-in NAT64 and DNS64 support for accessing IPv4-only resources so I would think it's possible to have an IPv4 corp network only?
0
 
LVL 58

Assisted Solution

by:Cliff Galiher
Cliff Galiher earned 500 total points
ID: 41759557
On the server side, yes (assuming your infrastructure is properly set up.) but client software still requires IPv6 support as NAT64 is not running on the client side. Lync 2010 was a perfect example of software that didn't run over directaccess because the client didn't support IPv6.
0
Business Impact of IT Communications

What are the business impacts of how well businesses communicate during an IT incident? Targeting, speed, and transparency all matter. Find out more in this infographic.

 
LVL 3

Author Comment

by:Edward Cho
ID: 41759572
Gotcha but I should still be able to ping servers (including the DA server) and/or access file shares?  I am unable to do so and the W10 Enterprise client is stuck on this screen:

Capture.PNG
0
 
LVL 3

Accepted Solution

by:
Edward Cho earned 0 total points
ID: 41760377
Found out that the Surface Pro 4 I was testing with had issues with the Windows Firewall.  Reset Windows Firewall and everything started working.
0
 
LVL 3

Author Closing Comment

by:Edward Cho
ID: 41765045
Solved my own problem.
0

Featured Post

NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

You might have come across a situation when you have Exchange 2013 server in two different sites (Production and DR). After adding the Database copy in ECP console it displays Database copy status unknown for the DR exchange server. Issue is strange…
This past year has been one of great growth and performance for OnPage. We have added many features and integrations to the product, making 2016 an awesome year. We see these steps forward as the basis for future growth.
In this Micro Tutorial viewers will learn how to use Boot Corrector from Paragon Rescue Kit Free to identify and fix the boot problems of Windows 7/8/2012R2 etc. As an example is used Windows 2012R2 which lost its active partition flag (often happen…
This tutorial will walk an individual through the process of installing of Data Protection Manager on a server running Windows Server 2012 R2, including the prerequisites. Microsoft .Net 3.5 is required. To install this feature, go to Server Manager…

732 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question