Stump the Panel » End Users and Information Workers

How come some Windows XP clients can map SharePoint drive and others cannot?

(2 posts)
  1. Here is the deal, I have two SharePoint 2007 MOSS servers, both running Windows 2003 server. All of our clients are running Windows XP with SP2 installed. On some PC's users can map SharePoint folders as drives, but on others they cannot. I believe I have eliminated both the servers, and permissions as issues as I have taken the following steps. The same user who can map a drive on one XP client, if they login to a broken XP client, they can no longer map the same drive, and they can no longer UNC to the same server or drive.

    I have several users up and running who are mapped to SharePoint drives with no issues on their PC's, but than I have about 1/3 of my other users who cannot map to any SharePoint folder or drive. This is totally PC based, as the users who cannot map, when the login to a users PC who can map, they can also now map the drive without issue. The error I am getting when a broken XP client tries to UNC to a sharepoint folder is this; Windows cannot find http://portal/TeamSite/

    I have looked at the WebClient service, and it is started on every XP client. I have also looked at what I believe to be the WebClient files which are located here; C:\WINDOWS\system32\drivers" and are the file MRXDAV.SYS to make sure we are all using the same version, and we all have the same version, 5. 1. 2600. 5512.

    I have also tried to to add a DWORD registry edit on the windows XP client within HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/WebClient/Paramters/UseBasicAuth

    I changed the value to "1" on that new registry edit, but it did not change a thing. I am not sure why this registry edit would change anything as the PC's who can map a drive did not have to add this registry edit.

    We are all on the same domain. Any ideas how some Windows XP clients cannot map a SharePoint drive while others can?

    Posted 2 days ago #
  2. This usually comes down to the persistent cookie set by SharePoint. Depending on your auth mechanism, you may need to "save password" or set the default browser to log in with current credentials for client apps to use the cookie.

    Posted 2 days ago #

RSS feed for this topic

Reply

You must log in to post.