The basic problem is that after moving to Windows file servers, users can't browse to a folder to which they have access. If they know the full, exact path, they can map a drive letter to it, but they can't browse to it.
This has created a lot of confusion and support tickets, as most users do not have a photographic memory and can't necessarily remember a long path.
Our file server is running Windows 2008 server using DFS. The clients are Windows 7 and are both joined to the domain. The Windows share is \\server\share. Both clients have the letter G: mapped to \\server\share.
User A has created a folder, G:\DEPT1\SUBDIR\SUBDIR\DATA. The IT Dept. has given User B full access to the 'DATA' folder.
When User B opens Explorer and looks at G:\, he does not see 'DEPT1' and so can't just browse down the tree to the shared folder. However if user B maps a driver letter to the full path, \\server\share\DEPT1\SUBDIR\SUBDIR\DATA, he can use the folder and read/write data to it.
This is a very inconvenient situation and users do not like it. On our old file server (Netware), User B would be able to browse to the 'DATA' folder. User B would not have been able to see any of the contents of the other folders in the path, or make any changes to the folders, but it allowed the user to be able to browse to a subfolder without needing a photographic memory.
Is there a configuration change we could make that would allow users to browse to folders to which they have access? Thanks in advance!