WebDav System Error 67 in Windows XP

Issue: I'm having issues getting WebDav to work in the command line on Windows XP, both Service Pack 2 and Service Pack 3.

C:\>net use z: https://mywebsite.com/software/
System error 67 has occurred.

The network name cannot be found.

I have tested this with two webdav server. Both Ubuntu Apache and I Windows Server 2003 IIS. Both get the same result.

Things That Haven't Worked:

1. I've installed the following Microsoft KB on my XP machines with no avail.

2. I've also found the following reg key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WebClient\Parameters UseBasicAuth REG_DWORD 1

3. I try the following when trying to use a few work around I've dug up on the web, all producing the same result.

   net use z: https://mywebsite.com/software
   net use z: https://mywebsite.com/software#
   net use z: https://mywebsite.com/software/
   net use z: https://mywebsite.com/software/#
   

4. I've also tried all the above combinations adding a user into it /user:user and /user:user@domain.

5. I've also tried using http:// rather than https://.

6. I've tried "\\server.com@ssl:443\folder"

7. I've gone over networking related issues as @WesleyDavid had pointed out.

Things that do work:

• I can connect to the webdav folder via the URL and with mapping in Network Place, with XP. But the command line doesn't work (I need a drive letter).
• Windows 7 works perfectly with the same command.

My Delemma:

I need this to work with a drive letter. What else can I try to get this working?

Using WedDAV enabled on OS X Lion Server, the syntax in XP is:

NET USE * http://server url/webdav/username password /user:username

This works, but can not figure out how to choose from multiple shares for the same user (it always defaults to the user account directory)...

I had the same problems for a HTTP WebDav connection (did not try with HTTPS yet but it should work too). Please try the following, it worked for me:

To enable Basic authentication on the client computer, follow these steps:

1. Click Start, and then click Run.
2. In the Open box, type regedit, and then click OK.
3. Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WebClient\Parameters
4. On the Edit menu, point to New, and then click DWORD Value.
5. Type UseBasicAuth, and then press Enter.
6. On the Edit menu, click Modify.
7. In the Value data box, type 1, and then click OK. Note Basic authentication is enabled if the UseBasicAuth registry entry is set to a non-zero value. Basic authentication is disabled if the UseBasicAuth registry entry is not present or if the UseBasicAuth registry entry is set to 0 (zero).
8. Exit Registry Editor, and then restart the computer.

Note that the key is called BasicAuthLevel in Vista and newer

Then connect

net use X: "http://mywebsite.com/software" /User:username password

Source http://support.microsoft.com/kb/841215/en-us

Zero Guess: I just edited this in here. Get rid of the trailing slash in net use z: https://mywebsite.com/software/ so that it reads net use z: https://mywebsite.com/software

First guess:

I don't like the look of /user:user@domain. I've seen sketchy things happen with that in some Windows CLI tools (even though, yes, it should work fine). Did you try the format /u:domain\user?

Second Guess:

1. Go into hardware management and select to View >> "Show Hidden Devices"
2. Open the "Non Plug and Play Drivers" Node
3. Disable IP Network Address Translator

That has been known to cause error 67, which is the heart of the problem. A communications error.

Third Guess

Winsock corruption! It happens. Look into netsh winsock reset and netsh winsock reset catalog

You can read more at this KB article.

Fourth Guess:

Sometimes error 67 can be caused by a hardware level issue on both the client and server side, usually involving the drivers. Two possibilities:

1. Reset the TCP/IP stack on the client using netsh int ip reset. I know, I know - it's cargo cult administration. Just try it. =)
2. Update to the latest network drivers for the exact card model number on all machines involved. Even the servers. In my mind somewhere, I seem to recall error 67 being thrown on clients and the server network card being updated to solve the issue.

Fifth guess

We're getting down to thin pickins down here. Try this in Safe Mode with Networking. WebDAV connections should be able to be made. I'm wondering if some interfering extraneous network driver is interfering, although that should have been taken care of my updating the drivers in Guess #1.

You can't map a network drive to an https connection pre Windows Vista, at least not with the Net command. This has to do with an issue with the WebDav mini redirecter. Please check the following: http://www.autohotkey.com/forum/topic44471.html