Yes the great unknown of the internet is in between. Umm this is in test lab for "academic" purposes to see if I can make it work. I guess maybe it sounds silly but I felt that if I understood it properly then I would be able to make it work thereby confirming that I understand what I am doing versus following a step by step tutorial.
For production yes we'll do RPC over HTTPS. Thanks JB ________________________________ From: Carl Houseman [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 17, 2008 10:32 AM To: MS-Exchange Admin Issues Subject: RE: Exchange & Outlook Communication When you say "across a firewall" is one side of that firewall the greater unwashed Internet? And if so, why mess with anything but RPC over https ? That's why it was created. Carl From: John Bonner [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 17, 2008 9:29 AM To: MS-Exchange Admin Issues Subject: Exchange & Outlook Communication Good Morning, So I think I messed up my exchange install last night. Here are the specs: Windows 2003 R2 SP2 Exchange 2003 SP2 When anyone on the local LAN connects everything works just fine. Over VPN same result. However for several reasons we are also toying with for now connecting Outlook across a firewall. We have RPC port 135 opened as well as 1025 and 2472 PAT to exchange server. When we first setup the mail profile we get initial handshake (prompt for username and password) but then the exchange server name gets changed in the mail profile from XXX.XXX.XXX (a routable published dns name) to yyy.yyy.add which is the internal name of the exchange server. When we open Outlook we get the dreaded you must first connect to the exchange server before you can synchronize. I suspect that server name getting changed is causing outlook to not get passed initial handshake. Any way I can get Outlook to hold the name I enter over the name it enters after initial handshake? TIA JB ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja ~
