Y
yoweigh
Hello. I am attempting to configure a replicated Distributed File
System between one Win2K domain controller (primary) and two new Win2K3
R2 servers. For the purpose of this help request, pretend like I've
only got one Win2K3 guy. Once one's going the other will be a pice of
cake. I'll try to make this as easy to understand as possible by
dividing the question into four sections: 1) background 2) purpose and
intended final result 3) the problem I'm having 4) steps I've already
taken
1) BACKGROUND:
I work for a small/medium business in New Orleans. We're using a
Win2K Server machine as our domain controller, with approx. 50 (rough
estimate) concurrent users. About half of those are in our main office
downtown. I'll term these my 'primary users.' Another 20 or so are at
satellite offices accessing network resources through persistent VPN
tunnels. They're my 'remote users.' I also have an unspecified number
of people using individual VPNs from random remote locations. They're
my 'roaming users.'
Our domain controller is also handling DNS, DHCP, and fileshares.
I am in the process of deploying additional domain controllers to
the satellite offices.
Relevant info:
Domain: sales.x-x-x.net (withholding company name)
Controller: xxxfs2.sales.x-x-x.net (Win2K)
New Controller: xxxfswarehouse.sales.x-x-x.net (Win2K3 R2 x64)
2) PURPOSE/INTENT:
The idea here is to eliminate (as much as possible) the remote
users' dependence on internet connectivity. Under the current
configuration, those users have to do EVERYTHING through the VPN
tunnels. Authentication, DHCP, DNS resolution, grabbing files, etc. If
their pipe to the net decides to hiccup, they can't do a damn thing. No
authentication means they can't even log on. At that point, computer =
paperweight. I would like to add that I was not responsible for this
network implementation. I only started working here after Katrina, so
I'm trying to wrap my head around someone else's work here in addition
to rolling out a 'hurricane-proof' network infrastructure.
In order to end the net dependency, I'm deploying additional domain
controllers to the satellite offices. Users at those locations will
obtain services from the local controller, which replicates the
primary's AD through the VPN tunnel to downtown. I've got that working,
I think, but have not tested through the tunnels yet. Everything was
going (relatively) smoothly until I started to setup DFS.
3) PROBLEM:
Up to the present. I've got these domain controllers just about
ready to go, but I want to make sure that remote users can still access
fileshares during moments of connectivity loss. Here's the general
structure of my shares:
\\xxxfs2 (domain controller)
\\xxxfs2\sales
\\xxxfs2\admin
\\xxxfs2\warehouse
\\xxxfs2\users
\\xxxfs2\configura
I'm attempting to create COMPLETE mirrors of this data to the new
remote controllers. As I understand it, DFS will enable users to get
needed files from the most readily available source, which in this case
woule be the local controller.
My problem here is that the Win2K server will not allow me to configure
a replication policy. I have created a DFS root named 'files,' AKA
\\sales.x-x-x.net\files. This is all subject to change, BTW, since what
I'm doing right now is really a pre-deployment test more than anything
else. My root currently has three links: warehouse, admin and sales.
These are local shares, which I linked by giving their In the context
menu for both the root and the links, the 'replication policy' option
is greyed out.
4) STEPS TAKEN:
I have done quite a bit of googling today to no avail, trying
anything I found along the way. I have ensured the following:
-all drives involved are NTFS
-the Win2K server (xxxfs2) is running the File Replication Service,
which I also attempted restarting, as well as the Distributed File
System service
-the Win2K3 server I'm configuring (xxxfswarehouse) has already
installed AD and replicated the directory from xxxfs2
-xxxfswarehouse is also running the FRS and DFS services, along with a
'DFS replication' service
I have attempted the following stuff:
1) Copying the warehouse share to the xxxfswarehouse server and linking
it from aosfs2's DFS management thingy.
2) Configuring replication from xxxfswarehouse with the New Replication
Group Wizard. I get an error telling me xxxfs2 is not running the DFS
Replication Service, which is completely true. (I did not expect this
to work)
Anybody have any idea why I can't setup a replication policy? Should
Win2K have a DFS Replication Service? Would DFS even be the ideal way
to accomplish my goal of connectivity independence? If not, what
alternatives would you recommend? Profuse thanks go out to anyone who
can (and does) help me.
-Yoweigh
System between one Win2K domain controller (primary) and two new Win2K3
R2 servers. For the purpose of this help request, pretend like I've
only got one Win2K3 guy. Once one's going the other will be a pice of
cake. I'll try to make this as easy to understand as possible by
dividing the question into four sections: 1) background 2) purpose and
intended final result 3) the problem I'm having 4) steps I've already
taken
1) BACKGROUND:
I work for a small/medium business in New Orleans. We're using a
Win2K Server machine as our domain controller, with approx. 50 (rough
estimate) concurrent users. About half of those are in our main office
downtown. I'll term these my 'primary users.' Another 20 or so are at
satellite offices accessing network resources through persistent VPN
tunnels. They're my 'remote users.' I also have an unspecified number
of people using individual VPNs from random remote locations. They're
my 'roaming users.'
Our domain controller is also handling DNS, DHCP, and fileshares.
I am in the process of deploying additional domain controllers to
the satellite offices.
Relevant info:
Domain: sales.x-x-x.net (withholding company name)
Controller: xxxfs2.sales.x-x-x.net (Win2K)
New Controller: xxxfswarehouse.sales.x-x-x.net (Win2K3 R2 x64)
2) PURPOSE/INTENT:
The idea here is to eliminate (as much as possible) the remote
users' dependence on internet connectivity. Under the current
configuration, those users have to do EVERYTHING through the VPN
tunnels. Authentication, DHCP, DNS resolution, grabbing files, etc. If
their pipe to the net decides to hiccup, they can't do a damn thing. No
authentication means they can't even log on. At that point, computer =
paperweight. I would like to add that I was not responsible for this
network implementation. I only started working here after Katrina, so
I'm trying to wrap my head around someone else's work here in addition
to rolling out a 'hurricane-proof' network infrastructure.
In order to end the net dependency, I'm deploying additional domain
controllers to the satellite offices. Users at those locations will
obtain services from the local controller, which replicates the
primary's AD through the VPN tunnel to downtown. I've got that working,
I think, but have not tested through the tunnels yet. Everything was
going (relatively) smoothly until I started to setup DFS.
3) PROBLEM:
Up to the present. I've got these domain controllers just about
ready to go, but I want to make sure that remote users can still access
fileshares during moments of connectivity loss. Here's the general
structure of my shares:
\\xxxfs2 (domain controller)
\\xxxfs2\sales
\\xxxfs2\admin
\\xxxfs2\warehouse
\\xxxfs2\users
\\xxxfs2\configura
I'm attempting to create COMPLETE mirrors of this data to the new
remote controllers. As I understand it, DFS will enable users to get
needed files from the most readily available source, which in this case
woule be the local controller.
My problem here is that the Win2K server will not allow me to configure
a replication policy. I have created a DFS root named 'files,' AKA
\\sales.x-x-x.net\files. This is all subject to change, BTW, since what
I'm doing right now is really a pre-deployment test more than anything
else. My root currently has three links: warehouse, admin and sales.
These are local shares, which I linked by giving their In the context
menu for both the root and the links, the 'replication policy' option
is greyed out.
4) STEPS TAKEN:
I have done quite a bit of googling today to no avail, trying
anything I found along the way. I have ensured the following:
-all drives involved are NTFS
-the Win2K server (xxxfs2) is running the File Replication Service,
which I also attempted restarting, as well as the Distributed File
System service
-the Win2K3 server I'm configuring (xxxfswarehouse) has already
installed AD and replicated the directory from xxxfs2
-xxxfswarehouse is also running the FRS and DFS services, along with a
'DFS replication' service
I have attempted the following stuff:
1) Copying the warehouse share to the xxxfswarehouse server and linking
it from aosfs2's DFS management thingy.
2) Configuring replication from xxxfswarehouse with the New Replication
Group Wizard. I get an error telling me xxxfs2 is not running the DFS
Replication Service, which is completely true. (I did not expect this
to work)
Anybody have any idea why I can't setup a replication policy? Should
Win2K have a DFS Replication Service? Would DFS even be the ideal way
to accomplish my goal of connectivity independence? If not, what
alternatives would you recommend? Profuse thanks go out to anyone who
can (and does) help me.
-Yoweigh