Hi Everyone, I'm sorry if this has been asked but it seems most of the posts I have read seem to have the opposite problem to what I am having. I am running Small Business Server 2003 with Outlook 2007/2010 clients. When I turn on Outlook Anywhere the clients can access exchange externally with no problems but cannot connect to exchange from internally. I have run outlook.exe /rpcdiag under a few scenarios: 1. Internal with no Outlook Anywhere - Conn = TCP/IP 2. External with Outlook Anywhere - Conn = HTTPS 3. Internal with Outlook Anywhere - Conn = --- Internally with Outlook Anywhere on the clients are in a constant state of Disconnect. Also if I turn OFF Outlook Anywhere, internal clients can no longer access the exchange server and are in a constant state of Disconnect. The Clients are not set to reverse the order for Fast or Slow networks so should be going TCP/IP then HTTPS One thing I noticed as I have been writing this I noticed that Internally the server name is "SERVER" and Externally the server name comes up as "SERVER.gta.local". In the Certificate under IIS/SERVER/Web Sites/Default Website/Rpc the Issuer and Subject have CN = ourexternaldomainname.com.au CN = companyweb CN = SERVER CN = localhost CN = SERVER.gta.local So I would assume (maybe wrongly) that the client should try all those names til it gets a correct hit? Does anyone know how I go about fixing this? Thanks Nik

Hello Please check this link for outlook connectivity issue. http://social.technet.microsoft.com/Forums/en/exchangesvrgeneral/thread/00f22eb9-9a21-4af2-86bc-6961f74b238a http://support.microsoft.com/kb/831051/en-usThanks Mhussain

Hello Please check this link for outlook connectivity issue. http://social.technet.microsoft.com/Forums/en/exchangesvrgeneral/thread/00f22eb9-9a21-4af2-86bc-6961f74b238a http://support.microsoft.com/kb/831051/en-usThanks Mhussain

Hi Nik, The issue might be caused by the incorrect internal DNS record. Please change your internal DNS A record and point your proxy server URL (I assume it is SERVER.gta.local) to your CAS server’s external IP address. Or you may change the local host file first for a test. Best regards, Fiona Liao

Hi Fiona, Thanks for that. Actually feel a bit silly! It was a DNS issue but it was more the actual DNS server the client was using. We are a small network so the router was handling the dns so it was using external dns servers to resolve the internal server name. I just changed the clients to use the DNS server and voila its going! :) Thanks again