DFS, multiple subnets, and the opposite issue of everyone else..

i have issue opposite of people have been posting here regards dfs , multiple sites. few places show this.. i'm not sure if limitation of ad ds, dfs, both, or if missed extremely simple...this entire dfs project has been learning experience me. apologize before ahead of time if have. here's issue:

i have 1 2k8 level domain (mydomain.local) , many sites (site a=10.25.x.x/24, site b=10.26.x.x/24, site c=10.27.x.x/24, etc). dfs set @ 'site a', , set host our group drives, mapped users via gpo using namespace location. example, executive group drive mapped e drive, location \\mydomain.local\groups\executive, via gpo, executives. exec's @ 'site a' drives mapped fine, goes off without hitch. exec's site b, c, and d fail when gpo's applied. event viewer shows 'the network path \\mydomain.local\groups\executive cannot found..please check path , try again." ok. easy fix right? sure. remote user's box @ 'site b', see error in event viewer, try manually travers \\mydomain.local\groups\executive , bam. explorer shows it. right there. path indeed exist , user @ 'site b' can indeed see it. can manually map drive namespace \\mydomain.local\groups\executive , works until user relogins in , kaboom it's fubar'd again. hmm. if go \\mydomain.local from 'site b' computer? shows the dc at 'site b'. aww man.

running net view 'site b' lists correct namespace. target servers list dfs server. the dfs server set lowest cost option, , folder target is "first target among targets".... going happy 'dfs has issue spanning subnets' , work around until found traverse , manually map namespace location , worked fine until user rebooted. it's error of 'network path not found' being able traverse network path killin me here..

as can see - it's little opposite. other people have issue of machine 'site b' randomly pointing 'site a' instead of staying insite. mine won't go 'outsite' , need them to. :)

so can offer appreciated! if limitation of ad ds, dfs, best practice way resolve it?

thanks
dustin

hello,

you donot need brand new namepsace. need create fault tolerant namespaces on each dc have each dc host similar namespaces..to need create similar share folder same share , ntfs permission on site namespace on each dc. example, on each dc create folder called groups, share , give same ntfs , share permission in group folder on site dc.

then either command line or dfs mgmt console, create additional similar namespaces on each dc using groups root share.once done, if go dfs mgmt console, under namespaces, should see dcs under \\mydomain.local\groups, such \\dc1\groups, \\dc2\groups etc

once done, users , site can connect executive folder using namespace path of \\mydomain.local\groups.

hope helps,

---

isaac oben mcitp:ea, mcse,mcc view mcp certifications

Windows Server  >  File Services and Storage