Oaktech Posted July 12, 2019 Posted July 12, 2019 Ok, here goes. We have a Direct Access implementation om DomainA.local. Yes, I know Direct Access is deprecated, but I need to use it for another year and then I can go always on VPN. DomainA is in a working 2 way trust with DomainB. DomainA is a 192 domain DomainB is a 10. domain with a L3 switch doing the routing. Whilst on the corporate network Direct Access clients are able to see and access hosts from both DomainA and DomainB. If the direct access client is remote, they are not able to access DomainB. I assume this is a 6 to 4 translation issue? The DNS servers for Domain A have conditional forwarders to Domain B and vice versa. Does anyone know of a quick and dirty way to get around this? It's only going to be an issue for a few weeks until we migrate all the data off DomainB onto DomainA.
Oaktech Posted July 16, 2019 Author Posted July 16, 2019 Never mind, I've fixed it... In Remote Access Management , in Infrastructures servers, next through to DNS, then add DomainB.local, detect and then validate, Add and then next. Then add DomainB.local to the domain suffixes to use, then next and then finish. Finish the config to update the GPO and then reboot the client. It took 2 reboots over a non corporate network to pick the new config.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now