Direct Access: General Poblems / Questions RRS feed

  • Question

  • I have deployed DA without UAG. Internal Servers are all R2 based. I have problems to reach the public IPs of the DA. I see no traffic from external clients. When I am on the internal network (wit WLAN or cable) I can't resolve any internal name.

    It seems something with the GPO....

    MS Support didn't find the issue...

    Friday, October 15, 2010 9:51 PM


All replies

  • Did the GPO propagate to the DA clients?

    When you connect your client to the internet, what do you get when you run "netsh n s e"?

    Friday, October 15, 2010 10:53 PM
  • Hi,


    Without clear information, this would be difficult. Let's start to analyse the problem with the DirectAccess troubleshooting guide :


    As Yaniv said, are you sure your client computer is aware to use correct internal IPv6 DNS computers when outside?


    Have a nive day.

    BenoitS - Simple by Design
    Saturday, October 16, 2010 7:04 AM
  • Hi Eniac,

    You might want to try DirectAccess in a test lab first so that you can get a better understanding of how it works. That will make it a lot easier to troubleshoot once you get it into production.

    Check out the UAG DirectAccess Test Lab Guides over at:



    MS ISDUA/UAG DA Anywhere Access Team Get yourself some Test Lab Guides!
    • Proposed as answer by MrShannon Tuesday, October 19, 2010 2:11 PM
    Monday, October 18, 2010 10:51 AM
  • After you've gone through Tom's guides (also where I got started, thanks Tom!) you can also browse through mine ;]

    MrShannon | TechNuggets Blog | Concurrency Blogs
    • Marked as answer by Erez Benari Monday, October 25, 2010 10:03 PM
    Tuesday, October 19, 2010 2:11 PM
  • Hi Shannon,

    Really great stuff!!!! I'll blog it.



    MS ISDUA/UAG DA Anywhere Access Team Get yourself some Test Lab Guides!
    Tuesday, October 19, 2010 3:04 PM