Shortcut in Outlook with RPC over HTTP
Created: 17 May 2007 | Updated: 21 May 2010 | 1 comment
Hello,
I prepare test environment for Exchange archiving for first time and I am confused with Outlook shortcut behavior. I use back end – front end topology without ISA server. Front end server has two network interfaces, one to inside LAN, second to outside. OWA from outside works fine, every link to attachment in shortcut is “translate” to outside address (from http://evserver/.. to https://mail.test.local/...) and EV buttons works. Outlook in LAN works fine too, but when is connected through RPC over HTTPS from outside, links in attachments points to internal address and items are inaccessible. EV buttons in Outlook works. I can’t find in documentation which functions are accessible with RPC over HTTP and if this behavior is correct.
I prepare test environment for Exchange archiving for first time and I am confused with Outlook shortcut behavior. I use back end – front end topology without ISA server. Front end server has two network interfaces, one to inside LAN, second to outside. OWA from outside works fine, every link to attachment in shortcut is “translate” to outside address (from http://evserver/.. to https://mail.test.local/...) and EV buttons works. Outlook in LAN works fine too, but when is connected through RPC over HTTPS from outside, links in attachments points to internal address and items are inaccessible. EV buttons in Outlook works. I can’t find in documentation which functions are accessible with RPC over HTTP and if this behavior is correct.
Thanks
PB
Discussion Filed Under:
Comments 1 Comment • Jump to latest comment
We are seeing it in our environment also. Symantec support recommends that we use OWA in cases like this. The EV is not "aware" of RPC over HTTP. We asked this for EV 2007 but so far, we hear only silence.
Would you like to reply?
Login or Register to post your comment.