Quote:
Originally Posted by OverK1LL 
Now, forgive me if I am being a complete rook here - but...
Would disabling "Obtain DNS server address automatically" and setting my own (of 10.10.0.10/8.8.8.8) be causing the issue (as you mentioned earlier)?
I set DNS to auto on LAN 2 and DNS to 8.8.8.8/8.8.4.4 in my Airport Extreme (per your recommendation) and everything seems to be working the way it should.
Is this the way I should be configuring my remote locations? If so, I think you guys solved this and we can put this thread out of it's misery.

- Localnet DHCP is handled by an Airport Extreme.
- Domain DHCP is handled by the Domain Controller (SBS08)
- VPN is RAS (SBS08)
Now, forgive me if I am being a complete rook here - but...
Would disabling "Obtain DNS server address automatically" and setting my own (of 10.10.0.10/8.8.8.8) be causing the issue (as you mentioned earlier)?
I set DNS to auto on LAN 2 and DNS to 8.8.8.8/8.8.4.4 in my Airport Extreme (per your recommendation) and everything seems to be working the way it should.
Is this the way I should be configuring my remote locations? If so, I think you guys solved this and we can put this thread out of it's misery.
Setting 8.8.8.8 may be causing the problem because the local link comes up before the VPN is connected. DNS to 10.10.0.10 will not be available and Windows will be using 8.8.8.8 (and may never switch back).
Easiest thing to do is point everyone to the same DNS server (10.10.0.10) - as long as it can resolve internet names, you're good to go
Do this ALL via DHCP. Don't disable "Obtain DNS server address automatically"Edited by tompsonn - 11/7/12 at 4:54pm





