Windows Server 2008 R2 DFS Soft-Links won't display in IIS WebDAV

I'm running Windows Server 2008 R2 DFS on one of my file servers, using DFS to provide users with a single point of access to network shares spread out over multiple servers.  Users are having no problems navigating the DFS structure using Windows Explorer over the network (or similar technologies).  The problem I'm experiencing comes from users who attempt to connect to the file server's IIS Default Site, which is using WebDAV to present the DFS tree in their web browsers.  

To put some finer points on the problem, my DFS Namespace structure looks like this:
<domain name>\root\pub\apps
<domain name>\root\pub\archive
<domain name>\root\pub\depts
... etc.

Now, let's take "apps" up there.  \root\pub\apps is a DFS link that points to Q:\Apps (shared with R access to all and R/W to admins)  on the same server that's hosting DFS.  Using Windows Explorer I can drill down through DFS and see what's in apps.  However, if I use a browser to open http://localhost/pub/apps, I receive the following error:
HTTP Error 500.19 - Internal Server Error
The requested page cannot be accessed because the related configuration data for the page is invalid.

Just to check, I tried browsing with IE and Firefox one directory up, to https://localhost/pub, and it displays the directories just fine.  I can click around to other directories on the server which are being served via WebDAV without any problem.  The only time I receive the above error is whenever I try to click on any DFS link that points to another share (like localhost/pub/apps pointing to the local directory Q:\Apps).  

Has anyone encountered this before?  It doesn't appear to be a security permissions problem, but rather an issue with IIS following DFS redirects/soft links.  

Any advice is appreciated, and I can add any more information that might be helpful.


Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

TooMuchLinuxConnect With a Mentor Author Commented:
Found the solution.  The DFS link needed to be pointed to the actual DFS share, instead of the Windows share.  I had to create an additional DFS share for apps to make this work.
All Courses

From novice to tech pro — start learning today.