Article ID: 2388749 - View products that this article applies to.
When using a load balancer to distribute client requests across multiple web front ends, the Explorer View functionality may fail to operate properly. The failure may be represented to the client as repeated prompts for authentication, or the client may receive a generic "Page cannot be displayed" error message.
This problem may appear inconsistent across clients depending on the configuration of the client computer. This is because the Explorer View feature relies on IE Web Folder Behaviors
(http://msdn.microsoft.com/en-us/library/ms531432(VS.85).aspx)to provide it’s functionality. The IE Web Folders Behavior can leverage either of two possible protocols to produce the Explorer View experience:
Clients which do not have the Web Extender Client components installed will experience this problem, while clients that do have these components installed may be immune. The Web Extender Client components were originally shipped as part of the Office suite and within 32-bit versions of the Microsoft Windows operating systems. Starting with Windows Vista, these components were no longer provided with the operating system.
The SharePoint Explorer View feature requires certain standard WebDAV verbs to provide its expected functionality. Any load balancer need to be configured to forward these verbs to the SharePoint Web Front End servers in order for the Explorer View feature to work correctly.
Configure the load balancer to forward all of the following verbs:
GET, POST, OPTIONS, HEAD, MKCOL, PUT, PROPFIND, PROPPATCH, DELETE, MOVE, COPY, GETLIB, LOCK, UNLOCK
(http://go.microsoft.com/fwlink/?LinkId=151500)for other considerations.
Article ID: 2388749 - Last Review: September 22, 2010 - Revision: 6.0