Windows 7: WebDAV / Add a network location / path not valid error

Hi, I can connect to my WebDAV folder on my online server by BitKinex for example, but when I want to add a Network Location to the explorer it fails with the error message that the path is not valid ... but it is valid though.





Any help solving this very appreciated ...

Thx,
Frank

... got email answer with promising solution, but didn't work for me yet :

Hi there...have you seen this?... Many recent versions of Windows (including Windows 7) will not allow for basic authentication (cleartext) over non-SSL connections. This restriction makes security sense, however, the user interface simply fails without explaining why. You can override this security with a registry change: http://support.microsoft.com/kb/841215

Outtake:


To work around this behavior, enable Basic authentication on the client computer. To do this, add the
UseBasicAuth
registry entry to the following registry subkey, and then set the entry to a non-zero value:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WebClient\Parameters
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 key:
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.




The funny thing is that I had it working after I installed BitKinex (without using BitKinex) in 2 of the attempts, but then never again.

Frank

Conversation:

Frank,

You added the wrong value to the registry. A Dword subkey not a Qword subkey



Hi Ryan,
Thx for the tip. I changed it, but still not coming yet :



Regards,
Frank

-----Original Message-----
Frank...

The problem with attaching a drive to a WebDAV resource using the built in windows redirector is that the server must be using port 80. A nonstandard port WebDAV servers often use is 4444 and in many cases the web browser is used to connect to shares. WebDAV and windows is a hit or miss at best and SSL connections are supposed to be supported using the redirector as you have done prior. Judging by the server address I would have to assume that basic authentication is being used without SSL. Windows is probably just having a hard time receiving a response from the server for authentication. Prior to attaching a drive you can manually authenticate the share with the NET USE command. You have to be aware that without SSL passwords are sent in clear text and authenticating this way can leave the session open to a hi-jack. I have to also assume that auto response has been disabled by the server to minimize authentication by bots.

If the below is successful then you can create a batch script to run each time you logon to windows to make the process verbose. NET USE has a command line switch that makes it verbose but I haven't had much luck with it working in the past so I use a .bat at logon and place it in the startup folder. I would give the below a shot first and if that fails then you might want to manage the connection with a 3rd party client software.


Start
Run
Type cmd and press enter

At the command prompt type
NET USE * Index of /uploads password /USER:username Make sure to replace password and username with your actual username and password and press enter. You should see "command completed successfully"

Type exit and press enter

Now try mapping a drive as you did before.


To be honest... If this is your solution for offsite file storage and serving it is inefficient, slow and very insecure as WebDAV is nothing more than a glorified FTP server. You would be much better off with a virtual private server or network connection VPS(N).



**** Reply ******
Hi Ryan,
Thx for explanation.

I tried the net use command but received an error 67 "network name cannot be found"


Ya, SSL seems pretty necessary to be used with it. I've seen I can turn on SSL with BitKinex and also I saw SSL being mentioned in the wiki of my hoster (dreamhost) ... not knowing yet which end or if both need to turn it on.

I once saw an article where instead of auth basic it was said to use auth "something else" (can't remember the term)

Regarding 3rd party, BitKinex works drag & drop a file, but couldn't find out (google) yet how to add a network drive with it ... which is essential to work for me.

Regards,
Frank

First, you should use a WebDAV server that supports Digest authentication. Messing with the registry is not a good option and it makes it insecure.

You need Windows 7 or later. XP and Vista does not work well.

You cannot use a secure connection if you do not have a valid certificate on the server. See the following for more info:
mapping_windows7_drive