Re: Another another virt directory web site with OWA on SSL?

From: p (abefuzzleduser2@yahoo.com)
Date: 10/11/02 

From: "p" <abefuzzleduser2@yahoo.com>
Date: Thu, 10 Oct 2002 17:15:10 -0500

For "insecure" I just meant a non ssl IIS machine it does work.

Here is what I do on the SSL machine site.
Add virtual directory "WebFiles"
Point to c:\inetpub\ftproot, permissions on ftproot are everyone full
control
Add IIS virt dir permissions for read, write and dir browsing
Disable default doc
Dir security is basic.
Dir security, secure comm , edit , Req SSL and ignore client certs are
checked.

Open browser on my machine (not machine with ssl) and still get the 503.

https://secure.blah.com/WebFiles/

Try adding the network connection and it says the folder is bad?

Does this dav use a different port than ssl 443 or port 80?

Thanks
P

""Chris"" <chrisadonline@microsoft.com> wrote in message
news:GIKhyUKcCHA.1904@cpmsftngxa06...
> Hey,
>
> I am not sure where OWA comes into play here, but all you simply need to
do
> you seem to have done. In IIS, create a virtual directory (or a physical
> directory using Explorer) and ensure that the NTFS\Share permissions allow
> read\write to the appropriate user(s). After doing this, you disabled the
> default document and enabled directory browsing. This is correct.
>
> The use of SSL shouldn't matter in this step, but I don't understand what
> you mean by an un-secure webserver?
>
> I just tested this on my IIS server, for what it is worth, and it worked.
> My steps were:
> 1). Created a User called TestWebDav
> 2). Created directory on c:\ called TestWebDav
> 3). Created virtual directory in IIS and pointed to c:\TestWebDav
> 4). Click Documents, disable Default Document
> 5). Clicked Directory Security and Clicked Edit for Secure Comm --
Said
> Require SSL (ignore client certs)
> 6). Opened My Network Place -- Double clicked New Network Place and
> typed https://machinename/share
> a). Entered Credentials
> b). Copied txt file and it worked
>
> Thus, this shouldn't be an issue. However, ensure that all the above
steps
> have been completed. Also, make sure that you are not attempting to
write
> files to the "logical" M drive created by E2K. That I know nothing about
> except that will probably not work...
>
> Hope this helps,
>
>
> ~Chris
> Microsoft IIS Technical Lead
>
> "Please do not send email directly to this alias. This is our online
> account name for newsgroup participation only."
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> You assume all risk for your use. © 2001 Microsoft Corporation. All rights
> reserved
>

Relevant Pages

  • Re: OWA forwarding - message body lost
    ... Have you configured Exchange virtual directory in IIS to use SSL? ... Whether this issue happens on every OWA client. ...
    (microsoft.public.windows.server.sbs)
  • Re: OWA forwarding - message body lost (Bill Peng)
    ... Have you configured Exchange virtual directory in IIS to use SSL? ... Whether this issue happens on every OWA client. ...
    (microsoft.public.windows.server.sbs)
  • Re: Do I really need a wild card certificate ?
    ... Looks like you and Funkadyleik are correct it is a network issue, ... When I browse to the SSL enabled virtual directory from within my work ... Wildcard cert is typicall more expensive then normal SSL cert, ...
    (microsoft.public.inetserver.iis.security)
  • Re: SSL broken after Windows 2003 upgrade
    ... The svchost.exe you reference is "IIS". ... routes them to the appropriate w3wp.exe based on configuration from WAS ... WFetch can make both a normal SSL request as well as a Client-Certificate ...
    (microsoft.public.inetserver.iis)
  • Re: Cannot access Public Folders through ESM
    ... IIS and ran IISRESET to stop/start the services. ... > Do you have SSL required on the ExAdmin virtual directory too? ...
    (microsoft.public.exchange2000.admin)
Quantcast