| Author |
Message |
Daern's Instant Fortress
Guest
|
 Posted:
Thu Dec 02, 2004 3:03 pm Post subject:
DFS problem with multiple domain controllers |
|
|
I am having a crazy problem with DFS on my network and I wonder if anyone
can help. It's a bit of a ramble, but please try to stick with it!
Let me set the scene...
I have a domain, previously an NT4 domain, now upgraded to AD2003. Assume
for this example that the legacy domain name is "domain" and that the AD
domain is domain.mycompany.co.uk.
I have two domain controllers, DC01 and DC02, one of which (DC01) is also a
file server.
I have configured a single root file server share, \\DC01\MyFiles, and a
simple DFS root, \\domain.mycompany.co.uk\files which has a single target,
\\DC01\MyFiles.
Both DCs are also AD integrated DNS servers and all clients are configured
with both DNS servers.
All workstations are WinXP SP2, with Windows Firewall *disabled* (we use
BlackIce instead)
Right, scene is set, now onto the problem...
When workstations are connected to the local LAN, all works well. The
problems start when users access the file server using the VPN and the DFS
root becomes inconsitently inaccessible.
Now it seems that when a workstation fails to connect to the DFS root and I
try and ping it (i.e. ping domain.mycompany.co.uk) it resolves to DC02,
which I'm assuming isn't a problem as the DFS root is published in AD, so I
assume it will find the redirection from DC02 and point the workstation to
\\DC01\MyFiles. Unfortunately, it doesn't.
I am absolutely stumped by this. In every other way, my infrastructure works
perfectly. I believe that my DNS setup is correct, but I may br wrong. All I
know is that 50% of the time, my remote workers can't access the file
server, which sucks :-(
Any suggestions?
Sorry for the ramble!
Daern |
|
| Back to top |
|
 |
Daern's Instant Fortress
Guest
|
| Posted:
Mon Dec 06, 2004 2:54 pm Post subject:
Re: DFS problem with multiple domain controllers |
|
|
Anyone? :-( |
|
| Back to top |
|
|
Dan Lovinger [MSFT]
Guest
|
| Posted:
Tue Dec 07, 2004 6:53 am Post subject:
Re: DFS problem with multiple domain controllers |
|
|
Are the client machines (across the VPN) joined to the domain?
--
Dan Lovinger
Microsoft Corporation
Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only.
"Daern's Instant Fortress" <daern@hotmail.com> wrote in message
news:%23XCa92E2EHA.3616@TK2MSFTNGP11.phx.gbl...
| Quote: | I am having a crazy problem with DFS on my network and I wonder if anyone
can help. It's a bit of a ramble, but please try to stick with it!
Let me set the scene...
I have a domain, previously an NT4 domain, now upgraded to AD2003. Assume
for this example that the legacy domain name is "domain" and that the AD
domain is domain.mycompany.co.uk.
I have two domain controllers, DC01 and DC02, one of which (DC01) is also
a file server.
I have configured a single root file server share, \\DC01\MyFiles, and a
simple DFS root, \\domain.mycompany.co.uk\files which has a single target,
\\DC01\MyFiles.
Both DCs are also AD integrated DNS servers and all clients are configured
with both DNS servers.
All workstations are WinXP SP2, with Windows Firewall *disabled* (we use
BlackIce instead)
Right, scene is set, now onto the problem...
When workstations are connected to the local LAN, all works well. The
problems start when users access the file server using the VPN and the DFS
root becomes inconsitently inaccessible.
Now it seems that when a workstation fails to connect to the DFS root and
I try and ping it (i.e. ping domain.mycompany.co.uk) it resolves to DC02,
which I'm assuming isn't a problem as the DFS root is published in AD, so
I assume it will find the redirection from DC02 and point the workstation
to \\DC01\MyFiles. Unfortunately, it doesn't.
I am absolutely stumped by this. In every other way, my infrastructure
works perfectly. I believe that my DNS setup is correct, but I may br
wrong. All I know is that 50% of the time, my remote workers can't access
the file server, which sucks :-(
Any suggestions?
Sorry for the ramble!
Daern
|
|
|
| Back to top |
|
|
Daern's Instant Fortress
Guest
|
| Posted:
Thu Dec 09, 2004 8:09 pm Post subject:
Re: DFS problem with multiple domain controllers |
|
|
They are indeed. And they work very well when connected directly to the LAN
:-(
"Dan Lovinger [MSFT]" <danlo@online.microsoft.com> wrote in message
news:ungF5c$2EHA.3452@TK2MSFTNGP14.phx.gbl...
| Quote: | Are the client machines (across the VPN) joined to the domain?
--
Dan Lovinger
Microsoft Corporation
Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only.
"Daern's Instant Fortress" <daern@hotmail.com> wrote in message
news:%23XCa92E2EHA.3616@TK2MSFTNGP11.phx.gbl...
I am having a crazy problem with DFS on my network and I wonder if anyone
can help. It's a bit of a ramble, but please try to stick with it!
Let me set the scene...
I have a domain, previously an NT4 domain, now upgraded to AD2003. Assume
for this example that the legacy domain name is "domain" and that the AD
domain is domain.mycompany.co.uk.
I have two domain controllers, DC01 and DC02, one of which (DC01) is also
a file server.
I have configured a single root file server share, \\DC01\MyFiles, and a
simple DFS root, \\domain.mycompany.co.uk\files which has a single
target, \\DC01\MyFiles.
Both DCs are also AD integrated DNS servers and all clients are
configured with both DNS servers.
All workstations are WinXP SP2, with Windows Firewall *disabled* (we use
BlackIce instead)
Right, scene is set, now onto the problem...
When workstations are connected to the local LAN, all works well. The
problems start when users access the file server using the VPN and the
DFS root becomes inconsitently inaccessible.
Now it seems that when a workstation fails to connect to the DFS root and
I try and ping it (i.e. ping domain.mycompany.co.uk) it resolves to DC02,
which I'm assuming isn't a problem as the DFS root is published in AD, so
I assume it will find the redirection from DC02 and point the workstation
to \\DC01\MyFiles. Unfortunately, it doesn't.
I am absolutely stumped by this. In every other way, my infrastructure
works perfectly. I believe that my DNS setup is correct, but I may br
wrong. All I know is that 50% of the time, my remote workers can't access
the file server, which sucks :-(
Any suggestions?
Sorry for the ramble!
Daern
|
|
|
| Back to top |
|
|
Wendy Derman
Guest
|
| Posted:
Fri Dec 17, 2004 4:11 am Post subject:
Re: DFS problem with multiple domain controllers |
|
|
Have you tried configuring a second root target (note: not the same thing as
a normal target) on DC02? I found that a lot of mysterious problems cleared
up when I simply replicated my DFS root across all domain controllers. This
doesn't replicate the data, just the top level.
"Daern's Instant Fortress" wrote:
| Quote: | They are indeed. And they work very well when connected directly to the LAN
:-(
"Dan Lovinger [MSFT]" <danlo@online.microsoft.com> wrote in message
news:ungF5c$2EHA.3452@TK2MSFTNGP14.phx.gbl...
Are the client machines (across the VPN) joined to the domain?
--
Dan Lovinger
Microsoft Corporation
Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only.
"Daern's Instant Fortress" <daern@hotmail.com> wrote in message
news:%23XCa92E2EHA.3616@TK2MSFTNGP11.phx.gbl...
I am having a crazy problem with DFS on my network and I wonder if anyone
can help. It's a bit of a ramble, but please try to stick with it!
Let me set the scene...
I have a domain, previously an NT4 domain, now upgraded to AD2003. Assume
for this example that the legacy domain name is "domain" and that the AD
domain is domain.mycompany.co.uk.
I have two domain controllers, DC01 and DC02, one of which (DC01) is also
a file server.
I have configured a single root file server share, \\DC01\MyFiles, and a
simple DFS root, \\domain.mycompany.co.uk\files which has a single
target, \\DC01\MyFiles.
Both DCs are also AD integrated DNS servers and all clients are
configured with both DNS servers.
All workstations are WinXP SP2, with Windows Firewall *disabled* (we use
BlackIce instead)
Right, scene is set, now onto the problem...
When workstations are connected to the local LAN, all works well. The
problems start when users access the file server using the VPN and the
DFS root becomes inconsitently inaccessible.
Now it seems that when a workstation fails to connect to the DFS root and
I try and ping it (i.e. ping domain.mycompany.co.uk) it resolves to DC02,
which I'm assuming isn't a problem as the DFS root is published in AD, so
I assume it will find the redirection from DC02 and point the workstation
to \\DC01\MyFiles. Unfortunately, it doesn't.
I am absolutely stumped by this. In every other way, my infrastructure
works perfectly. I believe that my DNS setup is correct, but I may br
wrong. All I know is that 50% of the time, my remote workers can't access
the file server, which sucks :-(
Any suggestions?
Sorry for the ramble!
Daern
|
|
|
| Back to top |
|
|
Daern's Instant Fortress
Guest
|
| Posted:
Tue Dec 21, 2004 11:14 pm Post subject:
Re: DFS problem with multiple domain controllers |
|
|
"Wendy Derman" <WendyDerman@discussions.microsoft.com> wrote in message
news:8EE26A7B-E32F-43C6-961E-32F1CF595580@microsoft.com...
| Quote: | Have you tried configuring a second root target (note: not the same thing
as
a normal target) on DC02? I found that a lot of mysterious problems
cleared
up when I simply replicated my DFS root across all domain controllers.
This
doesn't replicate the data, just the top level.
|
Thanks Wendy. I'll give that a go :-)
DIF |
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in