Unfortunately, IIS issues a certificate with a common name that is your server’s name. This can be done easily if you go to your IIS server and click Server Certificates. If you want to enable HTTPS, you need to create a self-signed certificate for your server.So, when you need to configure a website’s physical folder for WebDAV access, you just have to do the following: There will be a WebDAV icon in the IIS which allows you to configure everything.
#Microsoft webdav redirector download#
It’s included automatically in R2, but for Windows Vista you have to download it from here. And it becomes quite secure when you use HTTPS.įortunately, Microsoft has developed a great IIS 7 extension that adds WebDAV capabilities to websites. It’s also pretty “comfortable” as it relies on HTTP. So that’s the way to go! It’s also a standard and many systems can connect to WebDAV. Fortunately, Windows clients can map network drives to WebDAV drives. FTPS is a great way to go but unfortunately Windows clients cannot directly map network drives to FTPS (it only supports plain FTP which is insecure). There were 3 options to use for accessing remotely files on Windows: VPN and SMB, FTP or FTPS and WebDAV. Of course, I would like to be able to access my files remotely and without any effort (such as downloading a third-party application). These days I’m trying to configure my new Windows Server 2008 R2.
0 kommentar(er)
