locked
UAG SP1 Directaccess Teredo Problems RRS feed

  • Question

  • First of all thanks for taking the time to read this LOVE UAG and keep up the good work. im having an issue that is the same as this post well end of this post

     http://social.technet.microsoft.com/Forums/en/forefrontedgeiag/thread/081e6de3-c477-4ecf-a7a8-8cd806c206e7

    but i am using the new SP1 RC for UAG and am testing DirectAccess i have followed the walkthrew and its all working except the client is connecting to IPHTTPS instead of the teredo Tunnel if i netsh int teredo set state enterpriseclient or sometimes when comming out of sleep it works or as other perople has said but as default client it isnt working... i cheaked the dns thing that the other posts says but didnt return anything.. when set to client it just says

    "Client is in a managed network" and will never connect... dose anyone have any ideas how to get the client to auto see the terdo without hard setting to enterpiseclient.. as laptops do move inside and outside by them selves.. thanks

     

    David

    Thursday, November 4, 2010 4:30 AM

Answers

All replies

  • Hi,

    We had this same issue on UAG Update1 also. One user has home network that had same subnet that was listed in Ad sites. The user got always info that the client is in managed network.

    When he changed his home network to other subnet (like 192.168.1.0 -> 192.168.2.0) it started to work correctly.

    I don't know if this is relevant or not.

    BR, TommiK

    Thursday, November 4, 2010 8:24 AM
  • Thanks for sharing your info

     

    in this case i only have two subnets listed in sites and services 10.0.0.0/16 and 10.36.0.0/16 so not sure its this but i do have a cross domain trust but UAG dosent know anything about it so i dont think this is it.. but thanks again... this thing is  real pain in the ____..

     

    Dave

    Thursday, November 4, 2010 10:48 AM
  • Why don't you define the Teredo enterpriseclient setting in GPO for all DA clients?

    http://blogs.technet.com/b/tomshinder/archive/2010/05/27/directaccess-and-teredo-adapter-behavior.aspx

    Cheers

    JJ


    Jason Jones | Forefront MVP | Silversands Ltd | My Blogs: http://blog.msedge.org.uk and http://blog.msfirewall.org.uk
    • Marked as answer by David Belyea Thursday, November 4, 2010 11:48 PM
    Thursday, November 4, 2010 12:00 PM
  • From what i have been reading as most of the clents spend most of there time inside the domain it will cause intermntent dns issues.. isnt this the case? 
    Thursday, November 4, 2010 12:39 PM
  • Not that I am aware of, can you provide more information? You may have read fom Tom's article that MSIT use this approach, so I would imagine it is recommended practice...

    If you have flaky NLS servers, I guess it could cause problems...


    Jason Jones | Forefront MVP | Silversands Ltd | My Blogs: http://blog.msedge.org.uk and http://blog.msfirewall.org.uk

    Thursday, November 4, 2010 12:46 PM
  • Thanks i have marked u as answered but im still cant workout why its not working by default i understand about the domain on the dns server if at another company or home but when on a 3g connection or connected to a test adsl connection cant work out why its doing that.. anyway ill just have to live with enterprise clients.....

     

    thanks again

     

    Dave

    Thursday, November 4, 2010 11:50 PM
  • Yes - enterprise client is what we use and what I generally recommend because of this issue.

    It will not create a problem for DirectAccess clients when they return to the corpnet.

    HTH,

    Tom


    MS ISDUA/UAG DA Anywhere Access Team Get yourself some Test Lab Guides! http://blogs.technet.com/b/tomshinder/archive/2010/07/30/test-lab-guides-lead-the-way-to-solution-mastery.aspx
    Friday, November 5, 2010 1:43 PM