Net use webdav ошибка 67

Remove From My Forums

Вопрос
Коллеги здравствуйте.

Знакомлюсь в webdav,

Установил на новую вирт машину 2012r2 а далее СТРОГО по инструкции (ссылка) выполняю настройку роли iis и
фичи webdav.

Но на моменте проверки и подключения сетевого диска командой net use * http://localhost/

благородно посылаюсь —

Интернет рекомендует следующее —

The following list of error conditions is designed to help troubleshoot situations that you might see when working with WebDAV.
1. When attempting to map a drive to a WebDAV site, you receive the following error:
  System
  error 67 has occurred.
  
  The network name cannot be found.
  
  This can be caused by one of the following conditions:
  - IIS is not installed or is not running on the server that you are attempting to connect to.
  - You have not installed the WebDAV Redirector on your client system.
  - The WebClient service is not running on your client system.
  - You have not enabled WebDAV on your web site.
  - You are using Basic Authentication and connecting to your web site using HTTP instead of HTTPS.
  - You are connecting to a web site on your local network that is using Fully-Qualified Domain Names (FQDNs) for name resolution, your web site uses Windows Authentication, and you have not added the web site’s FQDN to the proxy server bypass list on your client.
Только я в толк не возьму почему у меня не работает?

Ответы

Здесь
пишут, что нужно установить компонент Desktop Experienc и проверить запущен ли сервис Web Client.

С другого компьютера подключиться удается?
- Помечено в качестве ответа
  
  27 февраля 2015 г. 6:54

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:

I’ve installed the following Microsoft KB on my XP machines with no avail.
I’ve also found the following reg key: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesWebClientParameters UseBasicAuth REG_DWORD 1

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/#

I’ve also tried all the above combinations adding a user into it /user:user and /user:user@domain.
I’ve also tried using http:// rather than https://.
I’ve tried "\server.com@ssl:443folder"
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?

asked Sep 5, 2011 at 2:25

NixphoeNixphoe

4,5647 gold badges34 silver badges51 bronze badges

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)…

answered Dec 8, 2011 at 16:24

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:

Click Start, and then click Run.
In the Open box, type regedit, and then click OK.
Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesWebClientParameters
On the Edit menu, point to New, and then click DWORD Value.
Type UseBasicAuth, and then press Enter.
On the Edit menu, click Modify.
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).
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

answered Oct 22, 2012 at 13:13

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:domainuser?

Second Guess:

Go into hardware management and select to View >> «Show Hidden Devices»
Open the «Non Plug and Play Drivers» Node
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:

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. =)
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.

answered Sep 7, 2011 at 22:44

WesleyWesley

32.4k9 gold badges80 silver badges116 bronze badges

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

answered Nov 21, 2011 at 17:46

EliotEliot

111 bronze badge

Please try

C:>net use z: http://user:password@mywebsite.com/software

The other thing that I see is:

net use * z: https://mywebsite.com/software password /user:username

answered Sep 8, 2011 at 20:14

gWaldogWaldo

11.9k8 gold badges41 silver badges68 bronze badges

Mmm. How about:

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

Also, when you attempt to do ‘net use z: http://mywebsite.com/software/’ (point 5 of what hasnt worked) is port 80 active on your target server? Clearly this is an XP problem — can we isolate it to XP and HTTPS or is it XP and Webdav? Do your event logs show anything?

Also: Might the net use command be using the windows internet security settings for mapping the drive? You may need to place https://mywebsite.com in your trusted sites. Look in IE -> tools -> security, or your control panel.

answered Sep 13, 2011 at 17:17

RobWRobW

2,7661 gold badge17 silver badges22 bronze badges

Webdav ON IIS: net use * http://WEBSITE/DavWWWRoot PASSWORD /user:USER@DOMAIN

if you use IIS the Root folder have this name DavWWWRoot , some client resolve automaticaly ( windows 10 and windows 7 ) but in other case you must specify (windows xp).
This work form me

answered Nov 30, 2017 at 17:22

Источник

Remove From My Forums

Question
User-821689857 posted

Hi: I followed the installation directions for webDAV on IIS7, but the final step:

net use * http://localhost/

returns

System error 67 has occurred.

The network name cannot be found.

I googled error 67 and found some docs related to disabling IP Nat, but they referred to server2003 and I couldn’t locate anything for server2008. I’m installing on 2008-RC0, which has both the webserver and domain controller roles installed.

Answers

User1073881637 posted

Hi e1ny,

I’m running into the same problem and don’t know a solution. The article
http://go.microsoft.com/fwlink/?LinkId=105146 shows the error 67 and possible solutions. I’ve not been able to workaround this issue, I’m running RC1 Enterprise edition. I can use
Windows XP and add a «New Network Place» and use wedDAV. Which up until now, I’ve never messed with WebDAV. It’s pretty cool!

After I disabled WebDAV, I was no longer able to connect using my Windows XP machine. I can’t connect locally, but remotely works fine, so it’s either a bug or a missed step in the instructions. I’ve looked over the instructions a few times, tried
a few other things like granting anonymous access at the global level, doing an iisreset.

You have not installed the WebDAV Redirector on your system. I’m assuming this statement is when you «install the WebDAV» module. I had no issues installing or enabling, this shows the power of extending IIS 7.0. I’ll be curious
if others can run the net use command successfully.

Steve
- Marked as answer by
  
  Tuesday, September 28, 2021 12:00 AM
User1073881637 posted

One additional test. I was able to connect to my W2k8 rc1 box using Vista Ultimate RTM with no issues. The ‘mapped’ drive looks like DavWWWRoot(\IPAddress){Z:}. I didn’t map using
the net use command, but another feature of mapping drives in Vista. Hmm…
- Marked as answer by
  Anonymous
  Tuesday, September 28, 2021 12:00 AM

Источник

Remove From My Forums

Question
When I attempt to connect to a Webdav server from a Windows 8.1 box it fails with
System Error 67 has occurred.
The network name cannot be found.

I am using the net.exe USE command with the following syntax:
net.exe use Z: https://dav.DomainYaya.com/ <PASSWORD> /user:USERNAME

This exact syntax works for Windows 7.
I have more than one Windows 8.1 box where this fails.

There are various suggestions found all over the internet for various other situations. They do not apply or do not work.
For example, you will find an issue involving sending Basic authentication over http where there are suggestions about changing HKEY_LOCAL_MACHINESYSTEMCurrentControlSetservicesWebClientParameters

That does not work. There is also discussion about the Webclient service. (it is running). One can find discussion of the redirector. (The SYS file is present and is installed with Windows 8+ anyway.)

Using HTTP only fails similarly but with error 53 (but I only did that as a test.) The issue is the HTTPS version.

I have BTW tried this with two different webdav servers.

Any help is appreciated.

Joe

Answers

Hi Joe,

Based on our research, the error 67 have the following several possable causes:

•IIS is not installed or is not running on the server that you are attempting to connect to.

•You have not installed the WebDAV Redirector on your client system.
•The WebClient service is not running on your client system.
•You have not enabled WebDAV on your web site.
•You are using Basic Authentication and connecting to your web site using HTTP instead of HTTPS.
•You are connecting to a web site on your local network that is using Fully-Qualified Domain Names (FQDNs) for name resolution, your web site uses Windows Authentication, and you have not added the web site’s FQDN to the proxy server bypass list on your client.

For more information, please refer to the article as below:
Using the WebDAV Redirector
http://www.iis.net/learn/publish/using-webdav/using-the-webdav-redirector

According to the test, I am able to reproduce this issue in my lab. By default, the Webclient service is not running on windows 8.1 client. But for windows 7 client this service is running by default.

So please try to start the WebClient service on windows 8.1 client to check if it helps.

If you have any question, please don’t hesitate to let us know.

Karen Hu
TechNet Community Support
- Proposed as answer by
  
  Tuesday, January 27, 2015 2:47 AM
- Marked as answer by
  FangZhou Chen
  Wednesday, January 28, 2015 1:47 AM

Источник

Remove From My Forums

Question
When I attempt to connect to a Webdav server from a Windows 8.1 box it fails with
System Error 67 has occurred.
The network name cannot be found.

I am using the net.exe USE command with the following syntax:
net.exe use Z: https://dav.DomainYaya.com/ <PASSWORD> /user:USERNAME

This exact syntax works for Windows 7.
I have more than one Windows 8.1 box where this fails.

There are various suggestions found all over the internet for various other situations. They do not apply or do not work.
For example, you will find an issue involving sending Basic authentication over http where there are suggestions about changing HKEY_LOCAL_MACHINESYSTEMCurrentControlSetservicesWebClientParameters

That does not work. There is also discussion about the Webclient service. (it is running). One can find discussion of the redirector. (The SYS file is present and is installed with Windows 8+ anyway.)

Using HTTP only fails similarly but with error 53 (but I only did that as a test.) The issue is the HTTPS version.

I have BTW tried this with two different webdav servers.

Any help is appreciated.

Joe

Answers

Hi Joe,

Based on our research, the error 67 have the following several possable causes:

•IIS is not installed or is not running on the server that you are attempting to connect to.

•You have not installed the WebDAV Redirector on your client system.
•The WebClient service is not running on your client system.
•You have not enabled WebDAV on your web site.
•You are using Basic Authentication and connecting to your web site using HTTP instead of HTTPS.
•You are connecting to a web site on your local network that is using Fully-Qualified Domain Names (FQDNs) for name resolution, your web site uses Windows Authentication, and you have not added the web site’s FQDN to the proxy server bypass list on your client.

For more information, please refer to the article as below:
Using the WebDAV Redirector
http://www.iis.net/learn/publish/using-webdav/using-the-webdav-redirector

According to the test, I am able to reproduce this issue in my lab. By default, the Webclient service is not running on windows 8.1 client. But for windows 7 client this service is running by default.

So please try to start the WebClient service on windows 8.1 client to check if it helps.

If you have any question, please don’t hesitate to let us know.

Karen Hu
TechNet Community Support
- Proposed as answer by
  
  Tuesday, January 27, 2015 2:47 AM
- Marked as answer by
  FangZhou Chen
  Wednesday, January 28, 2015 1:47 AM

Источник

Net use webdav ошибка 67

Вопрос

Ответы

Question

Answers

Question

Answers

Question

Answers

А вот еще интересные материалы: