locked
DAClient are not getting connected due to Teredo Tunneling Pseudo-Interface RRS feed

  • Question

  • Hi,

    I have configured Directaccess with IPHTTPS Interface, My most of the DAClient  are getting connected on the IPhttps Interface but some of the DAClinet are getting in Connecting stage instead of being Connected because they are searching for Teredo Interface which is not configured on my server end. Even though all the DAClient are on the same network some are stuck on Teredo tunnel and after the reboot some are moving towards IPhttps and getting connected. 

    But I have to resolve this as all the clients should go with IPhttps and get connected with the DA Server.

    How to resolve this. help will be appreciated.

    Thanks,

    Roshan

    Thursday, November 15, 2018 1:00 PM

All replies

  • The best thing to do whenever using only IP-HTTPS on the DA server is to disable both Teredo and 6to4 - but make sure to disable these ONLY ON THE CLIENTS. You don't want to disable these tunneling adapters on the DA server because that will likely cause you errors inside the console.

    The easiest way to do this is to create a new GPO and set its Security Filtering to be the same as the DA Clients GPO - that way this new GPO applies to all of the DA laptops that you put into your DA group. Then inside this new GPO, configure the following:

    Computer Config | Policies | Admin Templates | Network | TCPIP Settings | IPv6 Transition Technologies | 6to4 State = Enabled (then set it to "Disabled" inside the settings)

    Computer Config | Policies | Admin Templates | Network | TCPIP Settings | IPv6 Transition Technologies | Teredo State = Enabled (then set it to "Disabled" inside the settings)

    Putting these two settings into the GPO will then roll around to the clients, and will disable both the 6to4 and the Teredo adapters at the client level.

    Wednesday, December 19, 2018 4:42 PM