Net use WebDAV on Windows 2008 R2 results in error 59 or 67...GAH!

Posted on 2012-04-10
Last Modified: 2013-12-06
Freshly installed VM.  Installed Application Server and IIS server roles.  Prepping to install SCCM 2007, and part of that is getting WebDAV working.  Seems simple enough.  I've followed a couple tuts online (, for example) and it's set up properly, I think.

WebDAV is installed and enabled on IIS.
Authoring rules are set up.
Authentication is set to Anonymous and Windows Authentication on the server and the site.
WebDAV Settings are set up according to SCCM requirements.
    -The settings in IIS at one point did NOT match WebDAV_schema.xml (which was odd, but what one person ( acknowledged could be an issue.  I set the options to the same as they are in IIS Manager.

I'll type out the commands I'm trying and the errors I'm getting below.

On the local machine:
ping localhost

Pinging [::1] with 32 bits of data:

Open in new window


Pinging [fe80::1dd3:c081:37:3025%11]
Replies, etc.

Open in new window

net use * http://localhost
System error 67 has occurred.

The network name cannot be found.

Open in new window

net use *
System error 67 has occurred.

The network name cannot be found.

Open in new window

net use *
System error 59 has occurred.

An unexpected network error occurred.

Open in new window

 net use *
**Pop-up asking for which cert; I select mine**
System error 1790 has occurred.

The network logon failed.

Open in new window

 net use * /user:law\accountname password
System error 1244 has occurred.

The operation being requested was not performed because the user has not been authenticated.

Open in new window

From a Windows 7 machine on the domain:
net use *
System error 59 has occurred....

Open in new window

net use *
System error 59 has occurred....

Open in new window

I'm a domain admin and have full control of the website root and I fall under All Users under the authentication rules in IIS.

I've tried adding my account under auth rules.
I've tried giving all users read, source, and write to WebDAV.
I've tried disabling IPv6 (by unchecking it on the network adapter's properties), but even then it still pinged localhost as [::1].

I'm at my wits end.  I had SCCM 2007 installed on another VM, but I'm pretty sure this didn't work right; I just went ahead with the install and ignored it, then ran into issues later on that I'm trying to get right this time.
Question by:Ubertam
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
LVL 24

Expert Comment

by:Nagendra Pratap Singh
ID: 37831851

Author Comment

ID: 37835439
That didn't work.  I even completely uninstalled IIS, rebooted the server, reinstalled and used the script to configure WebDAV and I get the same error 59.

Accepted Solution

Ubertam earned 0 total points
ID: 37872654
I created a new web site and bound port 80 to it (unbound from default) and it worked swimmingly.  Had to re-bind 80 to default and it's back at error 59.  I don't think it's harming anything right now, and the webdav site is up at :808, so I'll leave it at that until the issue pops up its ugly head at some point in the future.

Author Closing Comment

ID: 37890903
Not quite a success.

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

New Windows 7 Installations take days for Windows-Updates to show up and install. This can easily be fixed. I have finally decided to write an article because this seems to get asked several times a day lately. This Article and the Links apply to…
After seeing many questions for JRNL_WRAP_ERROR for replication failure, I thought it would be useful to write this article.
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…

729 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question