I am running SharePoint 2007 off a Windows 2008 R2 server and it seems to be running fine.
We're using another Windows 2008 R2 server for clients to login to (using remote desktop) and connect to the SharePoint site. However, whenever a client tries to use the "Open in Windows Explorer"-feature when handling documents, nothing happens. I have
run through all the posts here and checked that all services, webdav modules, etc. are as they should be.
I found a fix recently, but it does not make a lot of sense. If I go directly to the site after logging in, it does not work (as expected). However, if I type in the direct path to the documents folder, \\sitename\cases, it opens just fine and if I open
a new browser AFTER that, the "Open in Windows Explorer" feature now works perfectly fine.
Is there some way to fix this behavior other than adding a "net use" command to all startup scripts for all the users? It seems like I'm circumventing the problem rather than fixing it.
EDIT: We disabled UNC paths (because of security issues on the client server), but even if we tells you the path is disallowed, simply typing it in triggers the function to work (and still gives you access through SharePoint). Very odd.
View Complete Post