[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 162
  • Last Modified:

Windows 2003 DFS R2 question part 2

I looked over the links that I got from my previous post but i have a few more questions before i start implementing this and messing up the company.

currently I have files at the central location that people at a remote site need access to. These files can not be moved over since everyone at the central site also needs access to the files.

Now using DFS

My actually shares are

\\centralserver\sharefiles
\\remoteserver\sharefiles

and my DFS link for the two target from above is \\centralserver\sharefiles

If i understand this correctly, when the remote users click on the DFS link to access sharefiles, DFS point the users will  to the share that's located at the remoteserver and not the one at the centralserver (one of the benefits of DFS).

However the problem is that users from the remote site will still have to access the wan since the link is located at the central server. Is it possible have the DFS link at the remoteserver and at the centralserver?


2.) When first implement DFS, after all the shares setup do i need to move the files at the central location over to the remote location share or would replication process do the work for me? Meaning if I made the following shares

\\centralserver\sharefiles
\\remoteserver\sharefiles

but only centralserver\sharefiles has any data, the other one is just an empty share folder. Would replication replicate all the files over to the remoteserver share?
0
iamuser
Asked:
iamuser
  • 6
  • 6
1 Solution
 
NJComputerNetworksCommented:
yes, you have to enable replication.
0
 
iamuserAuthor Commented:
yes to which question? both 1 and 2?

0
 
NJComputerNetworksCommented:
"If i understand this correctly, when the remote users click on the DFS link to access sharefiles, DFS point the users will  to the share that's located at the remoteserver and not the one at the centralserver (one of the benefits of DFS)."   Yes, DFS uses your AD Sites to determine the closest DFS link.  So, clients should always be redirected to the local DFS link...(unless this link is offline, ...if offline, it will go over the WAN to other DFS links)

However the problem is that users from the remote site will still have to access the wan since the link is located at the central server. Is it possible have the DFS link at the remoteserver and at the centralserver?   If you replicate the data through DFS, then the client will preferrably automatically use the local content.

2.) When first implement DFS, after all the shares setup do i need to move the files at the central location over to the remote location share or would replication process do the work for me?

Yes, if you enable REPLICATION, the data will get copied to the other REPLICA's automatically.
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
iamuserAuthor Commented:
maybe i'm not making this clear or I'm not understanding this correctly, So i've up the points for the trouble.

What i meant is this

actual shares:

\centralserver\sharefiles
\\remoteserver\sharefiles

DFS link for the two target from above is \\centralserver\sharefiles

so ss you can see the dfs link is set at centralserver\sharefiles.  Which means users still have to cross the lan in order to know that that content is stored locally.

What i'm asking is can i do the following

\centralserver\sharefiles
\\remoteserver\sharefiles

one DFS link for the two targets above at \\centralserver\sharefiles
one DFS link for the two targets above at \\remoteserver\sharefiles

And while I understand replicatino has to be set, i assume that the second DFS link must be made first at the remoteserver. DFS does not do this for me automatically. Am i correct in this?




0
 
NJComputerNetworksCommented:
"so ss you can see the dfs link is set at centralserver\sharefiles.  Which means users still have to cross the lan <CORRECTION  --  WAN -- >  in order to know that that content is stored locally. "  the information is stored in Active Directory..  Do you have a DC in the remote site?  

\\centralserver\sharefiles
\\remoteserver\sharefiles

DFS link for the two target from above is \\centralserver\sharefiles  ... but you should direct you clients to use \\domainname.local\
0
 
iamuserAuthor Commented:
Nope we do not have a domain controller in the remote site. All domain logins are handled at the central location
0
 
NJComputerNetworksCommented:
You should still use this format:

DFS link for the two target from above is \\centralserver\sharefiles  ... but you should direct you clients to use \\domainname.local\


0
 
iamuserAuthor Commented:
ohhh i see, and then active directory would basically the users to whatever link is closer to them.

In the end there is no way for me to have it where remote users stay locally when accessing the link because the lack of a domain controller at the remote site.
0
 
NJComputerNetworksCommented:
In the end there is no way for me to have it where remote users stay locally when accessing the link because the lack of a domain controller at the remote site.  (Yes, this is my understanding of the product.)

Although, the clients will have to cross the WAN to get the \\domainname.local\ DFS information, the will be redirected to local DFS shares to obtain the data.
0
 
iamuserAuthor Commented:
thanks for the help,

lastly, since I have only one domain controller, I assume that my DFS link is not going to be fault tolerant. Meaning if the DFS link \domainname.local\
fails neither share will be accessible.

If i setup another domain controller either at the remote site or at my central site, can i make the DFS Link fault tolerant? And if possible would people see 2 links or the same one link?

0
 
NJComputerNetworksCommented:
lastly, since I have only one domain controller, I assume that my DFS link is not going to be fault tolerant. Meaning if the DFS link \domainname.local\
fails neither share will be accessible.  (right...not to mention, your whole domain is offline... )


If i setup another domain controller either at the remote site or at my central site, can i make the DFS Link fault tolerant? And if possible would people see 2 links or the same one link? (it becomes fault tolerant.... users will see one link...  )
0
 
iamuserAuthor Commented:
thanks for all the info
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 6
  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now