Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

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

Client: Windows 7 Premium, Office 2010 Pro Plus, both fully patched.

Server: Samba 3.5.10 on CentOS6 (SELinux enabled), Shadow copies enabled. Link speed: 1MBps.

As Windows 7 doesn't like me to use a network folder as a "Library" without making it offline, I used the trick of symlinking' them (like mklink /d c:\share\documents \server\documents)

Everything works fine - I can open the documents via: c:\share\documents (the symlink) \server\documents (the network path) and X:\ (after a net use X: \server\documents ....)

Now comes the interesting part: When I open an Office 2010 document - most noticeably an older Word version (97, 2000) which is being opened with Word 2010, via the symlink or, respectively, the "Library", opening the document is practically impossible. It takes minutes to open a small document. BUT, when I open the SAME document via the direct path or network letter, the speed is satisfactory.

Did anyone come across this? Anything I'm missing?

share|improve this question

You don't mention whether or not the same behavior exists with other files and since you didn't I'm going to assume that it doesn't.

Is it possible that you are seeing an issue with Office File Validation? I suggest you use a combination of ProcMon, TCPView and Wireshark/TCPDump to try and get a view into what Office is doing when you try to open documents via your symlinked directory. Additionally, crank the logging level up on Samba to 10 and see what it's doing.

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.