locked
DirectAccess stops working when non-corporate DHCP assigns a DNS suffix RRS feed

  • Question

  • WHen DirectAccess clients are on a non-corporate network and the DHCP server assigns the the computer a local DNS suffix, DA no longer works. It appears this is because the Teredo tunnel fails to initialize. For example, DA connects to company.com's network. If a corporate laptop is outside the network say on coffeshop.com. If the DHCP server at coffeeshop.com does not assign a local DNS suffix, DA works fine. If the DHCP server at coffeeshop.com is reconfigured to assign a local DNS suffix of coffeeshop.com, the Teredo adaptor disconnects and DA stops working.

    Is this a configuration problem with the DA server or with the laptop? What is the fix so that local DHCP servers don't break DA by assigning a local DNS suffix?

    Thanks,

    Jeff Cooper

    Friday, August 24, 2012 9:52 PM

All replies