We are running WSS 3.0 on Windows Server 2008.I have a number of clients accessing Sharepoint using either Windows XP with IE7, Windows Vista with IE8 or Windows 2008 with IE8.We are experiencing problems with using Explorer Views on Document Libraries when using IE8, the message we are seeing is "your client does not support opening this list with Windows Explorer".I have ensured that the 'WebClient' Service is started on the SharePoint Server and alsoensured that the WebDav Web Service Extension is allowed in IIS (not sure that this is required though).I do not know how to proceed. My users really need some kind of explorer based access to the Sharepoint Document Libraries, it doesn't necessary need to be via Sharepoint, athough that would be preferable. Cheers,Kate

I don't know if opening a local drive in Windows Explorer would be enough for you.(Use Net Use X: \\servername\pathtodoclib\doclib to get the doc lib as X: for those users)The problem is that they then forget that this is files in a document library that they are looking at.WSS FAQ sites: http://wssv2faq.mindsharp.com and http://wssv3faq.mindsharp.com Total list of WSS 3.0 / MOSS 2007 Books (including foreign language) http://wssv3faq.mindsharp.com/Lists/v3%20WSS%20FAQ/V%20Books.aspx

Yes I have tried this, without success. This is a Sharepoint Site, so what is 'pathtodoclib', I presume that is is a Web Share, but I can't work out how to create a Web Share for a Sharepoint Managed Website

I have been fighting with this issue for the past 2 weeks and have literally tried many, many things with no success until I reset IE8 back to the default settings. I finally determined IE was in an unstable condition, to heed the warning it has :)My details,Win7 beta 7225, O14, Ie8 Internal to our corporate network on one SharePoint environment I could not open explorer view returning the message, "your client does not support opening this list with Windows Explorer" I was also unable to open many documents unless I had been the one to place them on the site. XLS files would tell me they could not be found, Word documents would just not open.on other internal SharePoint environments I had no issue. External to our corporate network The problematic site would open in explorer view Opinion Once I reset the site prompted me for credentials which it previously had not done. I believe this may be tied to a cached password though I could not identify for sure. I hope this helps you.

Hi,The only problem we are seeing is not being able to use Explorer View with IE8. I have no reason to think that all of our machines have unstable IE8 installations.I have done more research and have realised that many many people are reporting the same issue with IE8, however I can't find anything to suggest any fix.Just to cover all the bases, today I have updated WSS 3.0 to Service Pack 2. This has not made any difference to the Explorer View issue.Still searching....

Hello Everyone,This is a known issue that was recently reported and I believe there is a fix due in the fall. Please contact IE Support and someone will assist you in getting it resolved. Thank you,Aseem Nayar - MSFTThis posting is provided "AS IS" with no warranties, and confers no rights

Try this http://www.microsoft.com/downloads/details.aspx?familyid=C523AC7A-5724-48BE-B973-641E805588F4&displaylang=en

Take a look here:http://tihomirignatov.blogspot.com/2009/08/sharepoint-error-message-your-client.htmlTihomir Ignatov

I spent DAYS on the phone with Microsoft's Level 1 tech support last year trying to find a solution to this problem. The issue deals with VISTA/Windows 7/Windows 2008 not accepting an unsigned certificate from a trusted source. The Microsoft Technician painstakingly walked me through the process of creating a certificate that would fool the browser and all me to use Windows Explorer mode. (The problem will be present even if you accept the certificate when you first login.) I was so frustrated with the entire process that I did not take the time to write down the steps necessary to fix the problem if/when I had to reinstall the OS. I had to reload my server and I am now stuck with my VISTA/Win7/2008 machines not able to use Windows Explorer mode..AGAIN! (This issue is not *normally* present on XP or 2003 clients.)

Take a look here: http://tihomirignatov.blogspot.com/2009/08/sharepoint-error-message-your-client.html Tihomir Ignatov Tihomir.. Your solution works FLAWLESSLY when there is no SSL involved. Using SSL, I receive a prompt asking which Certificate I'd like to use... I am 99.9% sure this is happening because the browser does not like the self signed certificate I created on the Win2008 server.

Nothing has worked for me yet. I have two sharepoint servers, one MOSS, the other WSS3 and a third server as the backend database server for both.The MOSS server works in explorer mode without issue.Originally the WSS3 server was working fine in explorer mode as it was a requirment of deployment. All servers are running Windows 2008r2Any pointers to look for would be appreciated.sgf:)

Nothing has worked for me yet. I have two sharepoint servers, one MOSS, the other WSS3 and a third server as the backend database server for both.The MOSS server works in explorer mode without issue.Originally the WSS3 server was working fine in explorer mode as it was a requirment of deployment. All servers are running Windows 2008r2Any pointers to look for would be appreciated. sgf:) Also should note on the wss3 installation, xp can get into explorer mode, but windows 7 / vista can't. All have ie8. When XP goes into explorer mode, user gets prompted to log in, which can simply be "canceled" and explore mode still occurs (whether user logs in or not) at that prompt.????sgf:)

Nothing has worked for me yet. I have two sharepoint servers, one MOSS, the other WSS3 and a third server as the backend database server for both.The MOSS server works in explorer mode without issue.Originally the WSS3 server was working fine in explorer mode as it was a requirment of deployment. All servers are running Windows 2008r2Any pointers to look for would be appreciated. sgf:) Also should note on the wss3 installation, xp can get into explorer mode, but windows 7 / vista can't. All have ie8. When XP goes into explorer mode, user gets prompted to log in, which can simply be "canceled" and explore mode still occurs (whether user logs in or not) at that prompt.???? sgf:) Okay another point to note. Further review of the two servers shows a webdav object on the wss3 server. I believe this was added when we added FTP service to the server. I also believe explorer mode stopped working when we added the FTP services to the server. sgf:)

Nothing has worked for me yet. I have two sharepoint servers, one MOSS, the other WSS3 and a third server as the backend database server for both.The MOSS server works in explorer mode without issue.Originally the WSS3 server was working fine in explorer mode as it was a requirment of deployment. All servers are running Windows 2008r2Any pointers to look for would be appreciated. sgf:) Also should note on the wss3 installation, xp can get into explorer mode, but windows 7 / vista can't. All have ie8. When XP goes into explorer mode, user gets prompted to log in, which can simply be "canceled" and explore mode still occurs (whether user logs in or not) at that prompt.???? sgf:) Okay another point to note. Further review of the two servers shows a webdav object on the wss3 server. I believe this was added when we added FTP service to the server. I also believe explorer mode stopped working when we added the FTP services to the server. sgf:) Found the solution to my problem here http://netindonesia.net/blogs/andriyadi/archive/2010/01/04/wss-3-0-sp2-on-windows-server-2008-r2-open-with-windows-explorer-failed.aspxThis problem occured after installing FTP services on the server, which probably got this extra component in iis manager...sgf:)

Nothing has worked for me yet. I have two sharepoint servers, one MOSS, the other WSS3 and a third server as the backend database server for both.The MOSS server works in explorer mode without issue.Originally the WSS3 server was working fine in explorer mode as it was a requirment of deployment. All servers are running Windows 2008r2Any pointers to look for would be appreciated. sgf:) Also should note on the wss3 installation, xp can get into explorer mode, but windows 7 / vista can't. All have ie8. When XP goes into explorer mode, user gets prompted to log in, which can simply be "canceled" and explore mode still occurs (whether user logs in or not) at that prompt.???? sgf:) Okay another point to note. Further review of the two servers shows a webdav object on the wss3 server. I believe this was added when we added FTP service to the server. I also believe explorer mode stopped working when we added the FTP services to the server. sgf:) Found the solution to my problem here http://netindonesia.net/blogs/andriyadi/archive/2010/01/04/wss-3-0-sp2-on-windows-server-2008-r2-open-with-windows-explorer-failed.aspxThis problem occured after installing FTP services on the server, which probably got this extra component in iis manager... sgf:) Okay, further removed webdav from the server 2008r2 features and all windows auth explorer modes work versus using aboves method.However, WSS3 Forms Based Auth explorer mode which used to work prior to installing FTP services still does not workVery frustrating and time COMSUMING. Okay, editing this to acknowledge my bad... In order for explorer mode to work on an FBA site, you have to check the box (sign me in automatically). During the problem period i had been forgetting to check that darn box. All is good now. sgf:)

We are running WSS 3.0 on Windows Server 2008. I have a number of clients accessing Sharepoint using either Windows XP with IE7, Windows Vista with IE8 or Windows 2008 with IE8. We are experiencing problems with using Explorer Views on Document Libraries when using IE8, the message we are seeing is "your client does not support opening this list with Windows Explorer". I have ensured that the 'WebClient' Service is started on the SharePoint Server and also ensured that the WebDav Web Service Extension is allowed in IIS (not sure that this is required though). I do not know how to proceed. My users really need some kind of explorer based access to the Sharepoint Document Libraries, it doesn't necessary need to be via Sharepoint, athough that would be preferable. Cheers, Kate I've been surging through multiple internet forums including microsoft forums and I finally came upon a fix that worked for me and thought that I would share the knowledge. I basically exported the registry change suggested and then restarted the webclient service to correc the issue in VISTA. My windows 7 machine had no problems but I only came across this error when IE8 was updated on all my vista machines. http://blogs.msdn.com/sharepoint/archive/2008/01/18/known-issue-office-2007-on-windows-vista-prompts-for-user-credentials-when-opening-documents-in-a-sharepoint-2007-site.aspx http://support.microsoft.com/?id=943280 Additionally, before I had tried to reinstall IE7, Add to the trustsites, install the webfolders fix, restart the webclient services, Add the Basic authentication level 2 in the registry...etc. I'm just glad I finally found something that worked. :) Best of luck, hope this helped some people. Derek

Hey Aseem have you find any solution for this issue . Its been long time now and i hope they have released some update\fix by now . IE8 /win7 explorer view issue . thanks

here is solution: http://support.microsoft.com/kb/972584 thanks -wsSharePoint administrator, MCTS,MCITP

Article says solution is for the OS below . I tested on win7 did not work . Prerequisites To install this hotfix, you must have Internet Explorer 8 installed on one of the following operating systems: Windows XP SP2 or Windows XP SP3 Windows Server 2003 SP2

Hi, I have Windows XP SP3 and IE 8 and wss 3.0. I had to download KB974455 on the user machine and it then worked. My WSS 3.0 Server is Windows 2003.

I have the same issue on windows 7 with MSS 2010, fixed by doing below. Please try to start webclient service: Click Start, click Run, type services.msc,then try to start the webclient service as shown in the screen-shot below