Hi Gary,
the quick answer to your previous post is, no, i couldnt connect. i got an error from when trying to log in:
"The session was ended. Communicator Web Access Server cannot log the user on to the Live Communications Server. (Error Code: 1)" (see attached: img.jpg)
i started over, and used the following guide to setup:
Download details: Microsoft Office Communicator Web Access Planning and Deployment Guide
i'm installing CWS on the same machine as we have our existing LCS server(lets call my server LCS01), as described in doco pg10: One Server for Both Internal and External users.
from pg 31, of doco:
steps
*(pg33)* download the CA certificatiojn path - DONE
*(pg34)* install the CA certification path - DONE
*(pg34)* Request the certificate -
step 5. In Certificate Template. select Web Server
> there was no Certificate template menu, nor was there the option to chose
"web server" (see attached img01.jpg)
so i used "Server Authentication Certificate"
*(pg34)* install the certificate on the server - DONE
step 6. in Identifying information for Offline Template, type the FQDN of the Communicator Web Access server
> again no such field, so i put the FQDN under the Identifying Information field, under "Name" (again see
(see attached img01.jpg))
*(pg34)* Install the certificate on the server
step 11. confirm that the certificate that you requested ... with it's FQDN is listed. if not, copy it from Personal\Certificates folder to the Trusted Root Certification Authorities\Certificates folder
> had to do manual copy as instructed as it was not in Trusted...\Certificates folder
*(pg36)* I then installed Communcator web access
*(pg36)* activated communicator web access
> created CWAservice AD account
> selected certificate (as just created above)
*(pg38)* created virtual server
>
Internal server (accessible by users who are within the corporate network - chose this option first to test that i could access CWA from internal network ie ensure connections were listening and communicating ok etc. before creating external server for I assume Blackberries?
or do Blackberries still use Internal server?)
> selected same certificate as created above for HTTPS connection
> IP=(all unassigned), port=443
and thats all i've done
i checked that the virtual server is connected (see attached img03.jpg)
even tried initiating a CWA connection from the CWA server itself to ensure no f/w/network issues and got the same error, as listed at the top.
hoping you can provide some guidance
cheers
Ben