locked
DirectAccess - Client is on similar network (behind NAT) as the corporated RRS feed

  • Question

  • Hello,

    Currently have I following situation:

    A customer network of range address 172.16.X.X.

    DirectAccess is configured and working well, except for clients which are working on a remote site. With an IP address similar to the ones used internally at the company.

    For example the client is connect with an address of 172.16.35.3 and can successfully reach the internet. But can not set up a DirectAccess connection. The same client works fine if placed behind a NAT with a range of for example 192.168.2.3

    Could it be that it confused to similar networks??

    Any Ideas??

    Thursday, May 31, 2012 1:00 PM

All replies

  • No, all DirectAccess traffic from the client's perspective is going IPv6, so the local network's IPv4 scheme doesn't matter at all.

    More likely is that this other network has a domain, and that Teredo is recognizing that domain and not successfully connecting (I see this quite a bit). On one of the DirectAccess client machines, try running netsh interface teredo set state enterpriseclient from a command prompt, and then try going to this network again. See if that makes a difference.

    There could be something else on this network blocking DA from connecting, but let's start with that since it's easy to test.

    Thursday, June 7, 2012 6:59 PM