DirectAcces Client Settings problem
-
Sunday, November 18, 2012 6:38 PM
Hi,
I did a simple DirectAccess lab I already made work couple of times ago. For reasons, this time it did not work. I did some troubleshooting and the commands below show weird settings :
- netsh dns show state
- netsh namespace show effectivepolicy
I did some googling and found that the link below tries to troubleshoot similar problem :
http://support.risualblogs.com/blog/2010/12/23/direct-access-issues-on-a-specific-windows-7-client-network-location-behavior-never-use-direct-access-settings/.
That link suggests to do some setting in the registry :
Key: Software\Policies\Microsoft\Windows NT\DNSClient or System\CurrentControlSet\services\Dnscache\Parameters<1>
Value: "EnableDAForAllNetworks"
I tried and it and it did not solve my problem. Anyway ; my aim is not this kind of fine troubleshooting. I just need to know why I fall in this trouble and how to avoid it next time I do the lab. I want to make the lab work (of course) !
Thanks in adavance for any help !
All Replies
-
Sunday, November 18, 2012 7:34 PM
On Sun, 18 Nov 2012 18:38:13 +0000, kayoumt wrote:
I did a simple DirectAccess
DirectAccess questions should be posted here:
http://social.technet.microsoft.com/Forums/en-US/forefrontedgeiag/threads
Paul Adare
MVP - Forefront Identity Manager
http://www.identit.ca
CPU: A juvenile way of telling your dog he missed the paper.- Marked As Answer by K_evin ZhuMicrosoft Contingent Staff, Moderator Monday, November 26, 2012 2:11 AM
-
Sunday, November 18, 2012 11:08 PM
Thanks Paul.
I transferred the question to the forum you suggested me.

