Maybe someone can help. I have one machine, pretty beefy but, the company
will not let me spend more money on a new server But, they want IM features.
So, I downloaded the trial (to see if I can get working before buying it).
One of the features we do need, is remote access, the web feature looked
idea for this, and get our employees away from using unsecure systems
(AIM/Yahoo/MSN) for business stuff. Also so if needed, the higher ups can
monitor/log sessions.
So far, installed it, local domain users can chat, it all works so far,
accept for externaly, or even one or the other. Exchange web access (2003,
with all service packs), works fine now, over https. I install LCS 2005 sp1,
get it running install the web client, now just problems.
If I disable LCS, OWA works fine, if enable it,
OWA(https://domain.com/exchange) goes to "You are not authorized to view
this page" and if I try to access https://domain.com/cwa I just get
"Directory Listing Denied". I need them both to live on 443 (our secure
site), so port 80 is out of the question. All certificates are in place, and
there should not be any problems there. I do not get any errors with it, and
double checked to make sure they are ok.
I'm sure I am doing something wrong here but, after spending an hour on
google looking, I just find people with the same problem with no answer to
fix this one. Is there someplace that goes though all the details of getting
these 2 to work in harmony ?
Please help if you can...need to get this working ASAP
Thank you in advance !
There is information in the Communicator Web Access deployment guide on
this and using the application isolation feature in IIS 6.0.
hth
Mark
Is it possable to make it run on a vurtual server with OWA ?
https://domain.com/exchange
https://domain.com/cwa
Is it possable to have this configuration ? This is what "company owners"
want....
I'm going to look hard over the web access deployment guide to see if that
helps but, only one machine....so, some of the extras wont work for me...
"markh" <markh...@gmail.com> wrote in message
news:1150900298.4...@y41g2000cwy.googlegroups.com...
"Someone" <Som...@someplace.com> wrote in message
news:euZlfIgl...@TK2MSFTNGP02.phx.gbl...
Maybe try using an additional IP (both external and internal).
For example your OWA can listen to 192.168.1.5:443 (existing IP)
Your CWA can listen to 192.168.1.6:443 (new IP)
Then modify your firewall to map the new external IP to the new internal IP.