SimonDMZ
Guest
|
 Posted:
Fri Jan 07, 2005 12:01 am Post subject:
Accessing Dfs shares using Windows 2000 and Windows XP |
|
|
We have a Domain based Dfs with over two Windows 2000 servers. All
works well and all files have replicated.
Our set up is as follows:-
There are a number of same named shared DFS folders on the two servers.
For example:- dfsDATA as the Dfs Root share and Company as Dfs Link
Name.
The Dfsroot is domain.name\dfsDATA
And a Dfs Link is called Company
Using Windows 2000 clients we can Run \\domain.name\Company and the
Company Dfs shared folder opens.
However in Windows XP, running the same command we get an error box
popup "Configuration information could not be read from the domain
controller, either because the machine is unavailable, or access has
been denied."
If we run \\domain.name\dfsdata\company we get the company share.
Yet if we run \\domain.name\sysvol we do get the SYSVOL dfs share.
Could it be permissions? The SYSVOL on C: and Dfs root and links on D:?
| Quote: | From a clients' point of view, and for clarity, when using mapped
drives company on 'domain.name' (T:) looks more friendlier than |
company on 'domain.name\dfsdata' (T:)
Any ideas would be appreciated. Regards, Simon |
|
Dan Lovinger [MSFT]
Guest
|
| Posted:
Fri Jan 07, 2005 5:37 am Post subject:
Re: Accessing Dfs shares using Windows 2000 and Windows XP |
|
|
\\domain.name\dfsdata\company is DFS.
\\domain.name\company is not. That could have accidentally worked because
Active Directory registers domain.name in DNS with the addresses of the
domain's DCs as its discovery mechanism. It would never work if you specify
the NetBIOS name (it has to resolve with DNS). It can't work unless a share
called "company" is on each DC, but it was never a supported or intentional
access mechanism.
The reason it fails in XP (and beyond) is that DFS owns the parsing of all
\\domain paths and since there is no DFS root "company", it fails the
request at that level. The reason it owns it is that its the remote
filesystem component which does the load levelling and site cost sorting of
the multiple targets \\domain will expand to in the general case.
Sorry.
SYSVOL (and NETLOGON) have dedicated support in DFS, which is why they work.
If you look at the DFS referal cache with the DFSUTIL tool (dfsutil
/pktinfo) you can see this.
--
Dan Lovinger
Microsoft Corporation
Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only.
"SimonDMZ" <SimonDMZ@aol.com> wrote in message
news:1105034460.596111.287950@c13g2000cwb.googlegroups.com...
| Quote: | We have a Domain based Dfs with over two Windows 2000 servers. All
works well and all files have replicated.
Our set up is as follows:-
There are a number of same named shared DFS folders on the two servers.
For example:- dfsDATA as the Dfs Root share and Company as Dfs Link
Name.
The Dfsroot is domain.name\dfsDATA
And a Dfs Link is called Company
Using Windows 2000 clients we can Run \\domain.name\Company and the
Company Dfs shared folder opens.
However in Windows XP, running the same command we get an error box
popup "Configuration information could not be read from the domain
controller, either because the machine is unavailable, or access has
been denied."
If we run \\domain.name\dfsdata\company we get the company share.
Yet if we run \\domain.name\sysvol we do get the SYSVOL dfs share.
Could it be permissions? The SYSVOL on C: and Dfs root and links on D:?
From a clients' point of view, and for clarity, when using mapped
drives company on 'domain.name' (T:) looks more friendlier than
company on 'domain.name\dfsdata' (T:)
Any ideas would be appreciated. Regards, Simon
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in