| Author |
Message |
StefanHammar
Guest
|
Posted:
Mon Dec 05, 2005 5:58 pm Post subject:
RPC over https and Outlook profiles |
|
|
Hello Experts
I have configured RPC over https with help of ISA 2003 sp1 and Exchange 2003
sp1 in a Exchange frontend - backend environment.
Must the user have two Outlook profiles?
- A lan Outlook profile for RPC connection to Exchange
- An Internet Outlook profile for RPC over https
Does Exchange 2003 sp2 have any improvements about RPC over https
or Safe RPC?
Any help or tip would be appreciated
/Stefan
|
|
| Back to top |
|
 |
mac.watson@gmail.com
Guest
|
Posted:
Mon Dec 05, 2005 5:58 pm Post subject:
Re: RPC over https and Outlook profiles |
|
|
If you want all users on the LAN to connect via RPC, yes, two profiles
are required. ALL of our RPC/HTTPS users connect via HTTP everywhere
(on the LAN and over the Internet) and that works fine for us. |
|
| Back to top |
|
 |
StefanHammar
Guest
|
Posted:
Mon Dec 05, 2005 5:58 pm Post subject:
Re: RPC over https and Outlook profiles |
|
|
Hello Mac
Thanks for your answer
What about authentication and split DNS for the host name?
When the users are on the coporate network,
- IS the http host-name refaring to the frontend server or the backend?
- Must the user authenticate when starting Outlook?
Thanks
Stefan
"mac.watson@gmail.com" wrote:
| Quote: | If you want all users on the LAN to connect via RPC, yes, two profiles
are required. ALL of our RPC/HTTPS users connect via HTTP everywhere
(on the LAN and over the Internet) and that works fine for us.
|
|
|
| Back to top |
|
 |
mac.watson@gmail.com
Guest
|
Posted:
Mon Dec 05, 2005 5:58 pm Post subject:
Re: RPC over https and Outlook profiles |
|
|
We run an internal "sub-zone" for the world reachable FQDN
(exchange.domain.com) of the proxy server; that way, the users have the
same name reachable in the office or out of the office.
When they are on the corporate LAN, the host name points at the
front-end (or RPC proxy, FE isn't actually required). In our case, the
front end is reachable from inside as exchange.domain.com and outside
as exchange.domain.com using the "sub-zone" mentioned above.
I'm not sure I follow; our users are on an AD, so they authenticate
through the directory; Outlook uses NTLM hased on logon to authenticate
against the mail servers.
Hope that helps. |
|
| Back to top |
|
 |
|
|
|
|