matedwards
asked on
Can access DFSnamespace but not folders within it...
From workstations I can access the dfsnamespace (\\domain.local\dfsfolder\ ) but cannot open any folders within it (\\domain.local\dfsfolder\ WPstaffhom es).
So if I click on WPstaffhomes I get this message...
This only occurs from our workstations. On servers running DFS it all works fine.??!!
And all UNC paths work fine.
dfserror.JPG
So if I click on WPstaffhomes I get this message...
This only occurs from our workstations. On servers running DFS it all works fine.??!!
And all UNC paths work fine.
dfserror.JPG
ASKER
Yep.. \\servername\WPstaffhomes is fine. I can access with no problems.
Clients are Win7 (32bit) service pack1 and joined to the domain.
Clients are Win7 (32bit) service pack1 and joined to the domain.
There are DFS clients hotfixes for Windows 7 SP1.
https://support.microsoft.com/en-us/kb/968429
Specifically, I would look at KB3000483, which contains the latest version of the DFS client for Windows 7 SP1.
https://support.microsoft.com/en-us/kb/3000483
I recall having problems in the past, and a hotfix fixed the issue. It's now part of our WSUS.
https://support.microsoft.com/en-us/kb/968429
Specifically, I would look at KB3000483, which contains the latest version of the DFS client for Windows 7 SP1.
https://support.microsoft.com/en-us/kb/3000483
I recall having problems in the past, and a hotfix fixed the issue. It's now part of our WSUS.
ASKER
Thanks Kevin.. doing now..
oddly, your screenshot suggests the folders are not actually folders, but shortcuts to folders.
Is that intended? are the actual folders in the namespace shown or are you redirecting elsewhere?
Is that intended? are the actual folders in the namespace shown or are you redirecting elsewhere?
Steve,
The screenshot is correct for a DFS namespace, as the links redirect you to another UNC path, so they are very much like shortcuts.
The screenshot is correct for a DFS namespace, as the links redirect you to another UNC path, so they are very much like shortcuts.
Thats incorrect mate. They should not show as shortcuts and they do not redirect you anywhere.
If they are something is incorrectly configured.
Check the properties of these shortcuts and pay attention to where they 'link' to.
If they are something is incorrectly configured.
Check the properties of these shortcuts and pay attention to where they 'link' to.
@matedwards, have applying DFS client hotfixes to your Windows 7 machines fixed the issue?
ASKER
@kevinhsieh is right. The DFS shortcuts do point to a 'normal' directory (you would use in a UNC path). As in the first post from any DC they work fine and open the 'target' directory. Unfortunately the hotfixes didn't work. Still getting the error.
Can I ask about permissions. The permissions on the network home folders work fine in a UNC path.
Should there be different permissions on the DFS folder..?
Many thanks again.
Can I ask about permissions. The permissions on the network home folders work fine in a UNC path.
Should there be different permissions on the DFS folder..?
Many thanks again.
Apologies, I'd forgotten about this way of doing DFS namespaces and acknowledge this is one option, but that doesn't mean it's the best way to go about it :-)
Could I assume you're using a namespace server which links out to existing standard fileshare servers as opposed to having multiple DFS servers hosting a shared namespace across multiple servers?
Sounds like the namespace links are not setup correctly. Could you please export your config so we can check it?
See the beginning of this migration guide for info on how to export to XML.
https://blogs.technet.microsoft.com/askds/2008/01/15/migrating-your-dfs-namespaces-in-three-sorta-easy-steps/
Could I assume you're using a namespace server which links out to existing standard fileshare servers as opposed to having multiple DFS servers hosting a shared namespace across multiple servers?
Sounds like the namespace links are not setup correctly. Could you please export your config so we can check it?
See the beginning of this migration guide for info on how to export to XML.
https://blogs.technet.microsoft.com/askds/2008/01/15/migrating-your-dfs-namespaces-in-three-sorta-easy-steps/
Share permissions on the DFS namespace share should probably be everyone full, with NTFS permissions being everyone read, system full, and no special permissions (ie create). I hate it when random files and folders end up in the namespace root share, instead of inside the fileserver shat especially where they belong.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for all your help but I think I may have stumbled across the problem.
I have set an explicit permission in DFS properties for authenticated users to 'read' the DFS referral target. (attached)
I've never had to do this before and as it states 'all the domain\users should be able to see the Namespace by default - but mine can't, even though all UNC paths work with no problems..!
Thanks again for all the help.
I have set an explicit permission in DFS properties for authenticated users to 'read' the DFS referral target. (attached)
I've never had to do this before and as it states 'all the domain\users should be able to see the Namespace by default - but mine can't, even though all UNC paths work with no problems..!
Thanks again for all the help.
What client OS versions? I assume the clients are domain joined.