If you browse to \\fqdn\someshare, where you end up is determined by DNS resolution.
\\contoso.com\NetLogon will be resolved to \\some.contoso.dc.ip\NetLogon and then your system will go there. *ASB **http://XeeMe.com/AndrewBaker* <http://xeeme.com/AndrewBaker> *Providing Virtual CIO Services (IT Operations & Information Security) for the SMB market…* * GPG: *1AF3 EEC3 7C3C E88E B0EF 4319 8F28 A483 A182 EF3A On Thu, Jan 7, 2016 at 7:32 AM, James Rankin <[email protected]> wrote: > A question for the AD masters out there… > > > > If I browse to the \\DOMAIN\netlogon share, how is the DC I browse to in > this instance defined? I’m fairly sure it isn’t the server specified in > the %LOGONSERVER% variable. Got users who are changing things in the > NETLOGON share and they’re finding big delays in seeing these updates > because they’re hitting servers in different physical sites. > > > > Am I right in thinking it depends in how subnets are configured in Sites > and Services? Or way off base? > > > Cheers, > > > > > > > > *James Rankin* > > EUC Director | HTG TaloSys | 07809 668579 | [email protected] > > One Trinity Green, Eldon Street, South Shields, Tyne & Wear, NE33 1SA > > Tel: 0191 481 3489 > > Email address: [email protected] > > Website: www.talosys.co.uk > > [image: phpy9YoGNAM] > > >
