Hi !!
Recently added a member server to small branch office. The office has a different IP subnet to the main office and the two are connected via a site to site VPN (users authenticate to a domain controller in the main office). With this scenario what would I need to setup in AD S&S to ensure that the main office DC's acknowledge the remote site
I am currently getting the following event logged on the main office Domain Controller:
There are x many connections to this Domain Controller from client machines whose IP addresses don't map to any of the existing sites in the enterprise.
Would I need to setup:
1. A new site.
2. A new subnet - pointing it to the new site?
Cheers
Recently added a member server to small branch office. The office has a different IP subnet to the main office and the two are connected via a site to site VPN (users authenticate to a domain controller in the main office). With this scenario what would I need to setup in AD S&S to ensure that the main office DC's acknowledge the remote site
I am currently getting the following event logged on the main office Domain Controller:
There are x many connections to this Domain Controller from client machines whose IP addresses don't map to any of the existing sites in the enterprise.
Would I need to setup:
1. A new site.
2. A new subnet - pointing it to the new site?
Cheers