Solved

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

Posted on 2012-04-10
4
6,929 Views
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 (http://learn.iis.net/page.aspx/350/installing-and-configuring-webdav-on-iis/#002, 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 (http://ajweh.com/blog/?p=103) 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 AP2.law.local [::1] with 32 bits of data:
Replies...etc.

Open in new window

ping ap2.law.local

Pinging AP2.law.local [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 * http://ap2.law.local
System error 67 has occurred.

The network name cannot be found.

Open in new window

net use * http://192.168.16.10
System error 59 has occurred.

An unexpected network error occurred.

Open in new window

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

The network logon failed.

Open in new window

 net use * https://192.168.16.10 /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 * http://ap2.law.local
System error 59 has occurred....

Open in new window

net use * http://192.168.16.10
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.
0
Comment
Question by:Ubertam
  • 3
4 Comments
 
LVL 23

Expert Comment

by:Nagendra Pratap Singh
Comment Utility
0
 
LVL 5

Author Comment

by:Ubertam
Comment Utility
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.
0
 
LVL 5

Accepted Solution

by:
Ubertam earned 0 total points
Comment Utility
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.
0
 
LVL 5

Author Closing Comment

by:Ubertam
Comment Utility
Not quite a success.
0

Featured Post

Maximize Your Threat Intelligence Reporting

Reporting is one of the most important and least talked about aspects of a world-class threat intelligence program. Here’s how to do it right.

Join & Write a Comment

You might have come across a situation when you have Exchange 2013 server in two different sites (Production and DR). After adding the Database copy in ECP console it displays Database copy status unknown for the DR exchange server. Issue is strange…
Restoring deleted objects in Active Directory has been a standard feature in Active Directory for many years, yet some admins may not know what is available.
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
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…

771 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

Need Help in Real-Time?

Connect with top rated Experts

12 Experts available now in Live!

Get 1:1 Help Now