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 use Symlinks extensively on my file server to prevent duplication of directories and files. I've enabled remote evaluation of Symlinks by using fsutil behavior set SymlinkEvaluation L2L:1 R2R:1 L2R:1 R2L:1. However, now I'm getting a "The device is not ready" error when I browse the network share from a remote system.

The particular share I'm accessing is hosted on the D: drive and the Symlink on the host points to a directory created on the E: drive using mklink /D D:\Directory\Link E:\Directory since Junctions do not work across drives.

Is there anyway to "hide" the symlink completely to the client so that I don't have to configure every client accessing this share to follow symlinks? On the server, I have no problems navigating between folders/links.

share|improve this question
did you manage to solve this problem? – Kristof Tak Nov 15 '14 at 12:42
No. I ended up moving the shares that used Symlinks to a FreeNAS server with AD authentication. As far as the windows clients are concerned, it is just another file server that is accessed the same way other Windows servers are accessed. underneath that layer, I can create Symlinks and the clients are clueless that they are following Symlinks. – Julian Easterling Nov 26 '14 at 13:38

From Kaspersky:

If the encryption module is installed on a workstation, then upon clicking a symbolic link to a network resource the operating system displays the message: Device is not ready.

Beyond that, I've seen this issue when using an external drive as the target of the link, but have yet to determine why.

You might consider using DFS as an alternative, although I personally don't like that it hides the true location of the files. Makes troubleshooting a real pain. Depending on the layout of the drive E, you might also consider using a mount point and see what happens.

share|improve this answer

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.