"Miha Pihler" <mihap-news@atlantis.si> wrote in message
news:e3CYfOsvEHA.3228@TK2MSFTNGP12.phx.gbl...
> Hi Vassilis,
>
> If you have standalone setup of your CA you can manually import the CA
> certificate.
>
> Open Web Interface for your CA server and go to Download a CA certificate,
> certificate chain or CRL. Here click on Download CA certificate. Save the
> file and transfer it on the client (all your clients and servers that will
> work with your Exchange server). Double click on it and follow the wizard.
> Default values should be OK. Once you install it, all the certificates
> issued on this CA will be trusted.
>
> I hope this helps,
>
> Mike
>
> "Vassilis" <vcon@hate_spam_hol.gr> wrote in message
> news:%23QFocAovEHA.1292@TK2MSFTNGP10.phx.gbl...
> > done that but i don't receive any error during the test.
> >
> > i try to install the certificate ton the trusted root CA of the server
but
> > even though it says import succesfully the certificate i do not see it
on
> > the store. Is their any way to make the server trust the CA ?
> > i think thats the problem
> >
> > tnx
> >
> > "Ganesh Anekar [MSFT]" <Ganesh@online.microsoft.com> wrote in message
> > news:OQsLBygvEHA.2316@TK2MSFTNGP15.phx.gbl...
> >> Hi,
> >>
> >> You can download following tool and run it on the webserver to verify
> >> certificate is good and there is private key associated with that
> >> certificate.
> >>
> >>
> >
http://www.microsoft.com/downloads/details.aspx?FamilyID=cabea1d0-5a10-41bc-83d4-06c814265282&DisplayLang=en > >>
> >> Look for server side errors.
> >>
> >> HTH.
> >> --
> >> Ganesh Anekar
> >> Microsoft Developer Support
> >> Internet Information Server
> >> *********************************************************************
> >> >>Please do not send email directly to this alias. This is an 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.
> >>
> >> © 2004 Microsoft Corporation. All rights reserved.
> >> *********************************************************************
> >> "Vassilis" <vcon@hate_spam_hol.gr> wrote in message
> >> news:%23mse3zbvEHA.2116@TK2MSFTNGP14.phx.gbl...
> >> > w2k3, exchange2k3 sp1
> >> >
> >> > So far i was using a certificate with wrong common name from an other
> >> > authority. OWA SSL was working fine but in order for RPC to work i
> > needed
> >> > a
> >> > certificate with the same common name as the DNS name. So from
another
> >> > win2k3 server with a certification authority installed i issued a
> >> > certificate for my server.
> >> >
> >> > Now, the certificate is correctly installed BUT it takes ages to load
> > the
> >> > page with https. If i go to my server on IIS and on directory
security
> > and
> >> > click on view certificate the server hangs for a while and then it
> >> > displays
> >> > the certificate with an explamation icon saying "do not have enough
> >> > information for the certificate" or something like that.
> >> >
> >> > The same thing happens to the client. from IE we type the address it
> > takes
> >> > ages to display the security notification dialog, we click on view
> >> > certificate, again the computer hangs and then after a while it
> >> > displays
> >> > the
> >> > certificate and even though we install it to the client we still get
> >> > the
> >> > security windows among others.
> >> >
> >> > Any ideas about this ?
> >> >
> >> > thank you
> >> >
> >> >
> >> >
> >> >
> >>
> >>
> >
> >
>
>