Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a Windows 7 amd64 box where one directory is shared:

  • local path is d:\drop\
  • remote path is \\aloism\drop
  • from SMB point of view, Everyone has Read and Write permission
  • ACLs for the folder are set so that all authenticated users have read and write permissions:
    NT AUTHORITY\Authenticated Users:(OI)(CI)C (which is inherited to all levels below)

Now I create a symbolic link within the structure of the directory:

D:\drop>mklink /d tools2 tools
symbolic link created for tools2 <<===>> tools

The problem is that I can't access this new directory from any of the remote machines (a Windows 7 box and a Windows XP box—both behave the same way):

C:\>dir  \\aloism\drop\tools2\
Volume in drive \\aloism\drop is droot
Volume Serial Number is FA73-1897

Directory of \\aloism\drop\tools2

File Not Found

How can I make it work? Possibly also for files?

share|improve this question

I think that you should use DFS for this kind of mappings. Another alternative would be NTFS junction point

share|improve this answer
I have changed these links to junctions and actually I do get to access the folder. – Alois Mahdal Mar 26 '12 at 11:51
On the other hand, DFS is not really relevant for desktop, although it is inplace here. So I suggest splitting the answer into two Answers so I can +1 the other one as well .-) – Alois Mahdal Mar 26 '12 at 11:53

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.