We had similar issues. After hours of googling, we found there are multiple possible causes and solutions. This sort of feature appears to be simple but must be rather complex under the hood. We went through trial and error with each solution and eventually found a combination that worked for us. One key solution is to ensure that the "Webclient" service is started on your Windows XP client. You may have to have admin rights on your workstation to start it. Our XP policy turned this service off at startup because of perceived performance issues when using a VPN. To override this, I added the following batch Windows commands as a "bat" file to my Windows command startup: exit sc config webclient start= auto net start webclient My response was also, "you're kidding". I guess Murphy was an optimist after all. Best wishes.
打开webclient服务！
