Solved

DirectAccess only works one way

Posted on 2016-09-26
3
51 Views
Last Modified: 2016-09-27
Hello,

I have a pretty standard DirectAccess setup and everything works from the client side. Clients on DA connection can ping/access all internal resources. However, the reverse does not work.

Internally, my DC is showing DA Client's IPV6 address, however, it cannot ping or access the client. The only resource internally that can access DA client is the DA server.

Can anyone tell me how to resolve this issue? I want to have full access to DA clients from any devices within the internal network with the right permission.

Thanks
0
Comment
Question by:Wangstaa
3 Comments
 
LVL 38

Accepted Solution

by:
Adam Brown earned 500 total points
Comment Utility
Is your internal network configured for native IPv6? If not, you have a lot of stuff you need to accomplish to get that going. Unless your DHCP is handing out IPv6 addresses to all clients and DNS had IPv6 records for all systems, you have to do a lot more stuff to get the Manage Out functions of direct access working. https://www.packtpub.com/books/content/configuring-manage-out-directaccess-clients has more details.
0
 
LVL 15

Expert Comment

by:Ivan
Comment Utility
Another great site for DA is made by Richard Hicks. You can always find new info regarding that technology.

https://directaccess.richardhicks.com/

Regards,
Ivan.
0
 

Author Closing Comment

by:Wangstaa
Comment Utility
The guide you linked worked perfectly! Thanks, not quite the work like what you described
0

Featured Post

Threat Intelligence Starter Resources

Integrating threat intelligence can be challenging, and not all companies are ready. These resources can help you build awareness and prepare for defense.

Join & Write a Comment

Network ports are the threads that hold network communication together. They are an essential part of networking that can be easily ignore or misunderstood, my goals is to show those who don't have a strong network foundation how network ports opera…
The recent Microsoft changes on update philosophy for Windows pre-10 and their impact on existing WSUS implementations.
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…

762 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

Need Help in Real-Time?

Connect with top rated Experts

11 Experts available now in Live!

Get 1:1 Help Now