Thank you for reading my post firstly.
I am working on a very simple site setup. One head office, one branch, connected with a site to site VPN.
Networks (HO 192.168.1.0/24) (BO 192.168.2.0/24)
Have added the subnets in AD sites and services, have also made sure that a DC is present in both HO and BO.
I am seeing some anomalies with my sites and services where-by a PC will log in correctly and identify itself as being in the branch office for example and report the correct site name, write the correct entry to DynamicSiteName, yet as soon as I browse to look at shares for example in our HO the DNS query thrown out for the server name that hosts the shares leads the site name to change back to the HO.
I am not sure and I presume it's not set this way by design, once a client has correctly identified itself as being in the right site for authentication regardless of what your accessing in another site, shouldn't the DynamicSiteName stay the same?
All pointers suggestions greatly welcomed. From everything I have read about ADSS you don't ever modify the DynamicSiteName key and there shouldn't really be any need ( if your subnets are set correctly ) to modify the SiteName key- ideally I'd like it to just work out of the box so to speak!
Can provide any info required.