IIS Management Console (unless you feel like doing everything remotely).You will also need a few server roles installed on your IIS server (you can do this through Server Manager), these are Your IIS server has your paid (and signed) SSL certificate imported.

You have a internal DNS record which points to the network adapter on your IIS server.You have a public DNS record which points to a IP address on your firewall which is in turn port forwarding 443 (HTTPS) to your IIS server (this also works through Web Application Proxys like the ones built into Smoothwall firewalls).In the previous article in this series we looked at the topology needed to setup a WebDAV infrastructure. This entry is part 2 of 3 in the series WebDAV - Access Windows File Shares outside the firewall on any device Using Windows authentication (instead of Basic Authentication) – I gave this a go when I was first setting up WebDAV but couldn’t seem to make it work all the same well worth a look.Basic setup of WebDAV on – (some interesting reading on here about download folder and large file support).Basic setup of a WebDAV site on IIS.net –.Using Cloud with iWorks - iOS (5.1 MiB, 1,488 hits)įor further reading take a look at the links below. Using Cloud - Windows 8 (327.6 KiB, 1,659 hits) Using Cloud - Windows Vista (166.2 KiB, 1,365 hits) Using Cloud - Windows 7 (149.3 KiB, 1,746 hits) Using Cloud - Windows XP (157.4 KiB, 1,399 hits) Using Cloud - Windows Phone (196.8 KiB, 1,458 hits) To help you along you feel free to edit the guides below to your particular requirements. So you now have your WebDAV server setup and its time to get this out to your users. This entry is part 3 of 3 in the series WebDAV - Access Windows File Shares outside the firewall on any device

Ordinal 42 fallout 3