During the past few months I was heavily engaged with different DirectAccess implementations and passed by several interesting issues/problems. The Direct Access Wizard is so simple and normally things get working from the first time however sometimes things can go wrong. In this article series I will try to go through several troubleshooting items moving from the basic commands to more advanced issues.
First of all we need to ensure that the Direct Access components on the Windows 7 client are running and functioning normally. The basic steps are as follows:
Netsh dnsclient show state
Which Transition Technology is my DA client using?
The Three main Netsh Commands that should be used for Troubleshooting are:
The main Netsh command for IPHTTPS is:
3. If the DA client is behind a NAT device then it should connect using Teredo provided that Port 3544 (UDP) is enabled and allowed all the way to the DA Server
The main Netsh command used with Teredo is:
4. If the Teredo didn’t work (Clients behind NAT) then the DA client will fall Automatically to the IPHTTPS option (Step 2) For more details on UAG 2010 Portal and Direct Access please check my blog http://itcalls.blogspot.com/