I have tried to Map Network Drive from the client's laptop (from my office) which is a member of the domain, and from my desktop PC. The problem occurs when I attempt to connect across the Internet. I got them a Static IP address from Verizon and have Port Forwarding configured on the Verizon router for TCPĪfter I enabled Directory Browsing for the Default Web Site in IIS, I can now browse to and its subfolders from within IIS, Internet Explorer, and Google Chrome on the server. Note: I cannot use their domain name address (https:\since their website is hosted by an external provider. The mapped network drive could not be created because the following error has occurred:Ī device attached to the system is not functioning. Same error if I use the administrator username/password. I get challenged, enter my domain username and password 2 or 3 times, and receive the following error. When I attempt to Map Network Drive using this path: I followed these articles to install WebDAV, create Certificate Signing Request (CSR), create Root and SSL Certificates using OpenSSL, install the SSL Certificate into IIS on the server and bind to port 443, set Port Forwarding on their Verizon router for portĤ43 to the server's LAN IP, and import the Root Certificate into the Trusted Root Certificate Store of the client PC. I am trying to set up Secure WebDAV access to a file share on their file server (Windows Server 2012 (not R2)).įirst off, why is there no straightforward documentation from Microsoft on how to share one folder via WebDAV?! Why is this so complicated? I understand some need granular control of settings, but geez, why can't a newb just 'flip a switch'Īnd share a folder via WebDAV? Okay, rant over, please help me figure this out.

I cannot figure out what I've done wrong and the client is getting impatient. Hi, I am an IT Consultant, but this is my first time setting up WebDAV for a client.

Webdav server on windows 7