I'm not sure if this is the right forum for asking this question, but bear with me.
I have installed the new WebDAV module for IIS 7 and am having some difficulties in setting up access over the internet, but not over the local intranet.
I can do the following over the intranet:
Map http://server/documents/ or https://server/documents/
Browse Directory to http://server/documents/ or https://server/documents/
I can do the following over the internet:
Browse Directory to http://www.example.com/documents/ or https://www.example.com/documents/
But I cannot Map http://www.example.com/Documents/ or https://www.example.com/Documents
I have tried doing this both with the internal mapping in Vista/2008, and also with the client built into Office 2007 (which allowed https webdav locations to be opened with IIS6)
I was previously able to do this under IIS 6 quite easily and nothing has been changed except upgrading to 2008/IIS7.
Any thoughts? I have checked the Windows Firewall and ensured that the ports are open, but I can't see how the directory browsing and the directory mapping are somehow not working.
Many Thanks!
EDIT: It gets weirder;
On a Windows XP machine not connected to the domain:
Using the software WebDrive, connection to the server is as painless and automatic as previously. I am able to access and write to all files.
Using Office 2007 (on the same machine) gives the error 'Documents in this folder are not available. The folder have been moved ...' when using the https address. When using the http address, I get 'You do not have permission to make changes to this document. Do you want to open a read only copy' (when trying to browse the folder)
Browsing FQDN gave this error every time, using IP did not the first time. After opening and closing one document, the IP gives the same error as FQDN.
I can still access https://www.example.com/documents/ in IE or Firefox with authentication and browse the directory.
On a Windows 7 and Vista Machine connected to the domain:
Using Office 2007 repeatedly prompts for credentials, then times out, then opens the output from IIS directory listing as seen if browsed in IE or Firefox.
Mapping on this machine also continues to prompt for credentials. and then gives any number of errors.
Mapping using the command prompt gives a wide variety of errors every time I connect, such as:
System error 1790 has occurred, then System error 59 has occurred.
I think it is almost time to dump IIS7 and return to IIS6!