I set up a DFS namespace just before Christmas and proved that replication is working a treat.
What isn't working is the whole point of DFS: Specifically that a client will access the DFS'd files/folders from the most local server that's taking part in the DFS replication.
The root is our London server. Data is replicated to (and presumably from) our HK and NY servers. When I test this from a PC in New York the DFS Namespace opens but is slow. When I look at the properties of one of the files to establish why it's slow I see it's resolving to the server in London.
Grr.
Point well and truly defeated.
What do I need to do to get DFS to behave as nature intended?
JJ
[small][purple]Variables won't. Constants aren't[/purple]
There is no apostrophe in the plural of PC (or PST, or CPU, or HDD, or FDD, or photo, or breakfast...and so on)[/small]
What isn't working is the whole point of DFS: Specifically that a client will access the DFS'd files/folders from the most local server that's taking part in the DFS replication.
The root is our London server. Data is replicated to (and presumably from) our HK and NY servers. When I test this from a PC in New York the DFS Namespace opens but is slow. When I look at the properties of one of the files to establish why it's slow I see it's resolving to the server in London.
Grr.
Point well and truly defeated.
What do I need to do to get DFS to behave as nature intended?
JJ
[small][purple]Variables won't. Constants aren't[/purple]
There is no apostrophe in the plural of PC (or PST, or CPU, or HDD, or FDD, or photo, or breakfast...and so on)[/small]
