Exchange 2013 Client Proxy
Is there a way to disable the HTTP proxy for those who are connecting internally and only use it for those who are not part of the internal AD?
i.e. internal desktops connect not using the proxy, however laptops or remote locations that are not tied into the forest connect via the proxy (setup using autodiscover).
i.e. internal desktops connect not using the proxy, however laptops or remote locations that are not tied into the forest connect via the proxy (setup using autodiscover).
ASKER
Hmm well I guess a better question would be how to fix it so that the users stop getting the cannot connect to proxy error when they start up outlook.
The proxy shows up as mail.domain.local. Think A selfsigned cert would suffice?
The proxy shows up as mail.domain.local. Think A selfsigned cert would suffice?
IT is better to know the root cause so you can resolve the issues permanently...
Please check the connection status by the method mentioned above. how does client trying to connect ? http or tcp ?
Please check the connection status by the method mentioned above. how does client trying to connect ? http or tcp ?
in exchange 2013 does not use MAPI anymore, all clients connect using outlook anywhere from both inside and outside
SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
Would I need to change the server name itself (computer name) to mail.domain.org or just leave that as mail.domain.local and set the name via the ECP?
Sorry for the slow response, had 40 things hit me at once for some projects I am working on.
Sorry for the slow response, had 40 things hit me at once for some projects I am working on.
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
Sorry sorry sorry for the late response! I am the only IT person for 315 users and almost 450 devices across 9 counties and they have been running me ragged.
By split DNS, I assume you mean having mail.domain.org on the external DNS and on the internal have a CNAME for mail.domain.org -> mail.domain.local? or just an A record for mail.domain.org to go to the IP of mail.domain.local?
By split DNS, I assume you mean having mail.domain.org on the external DNS and on the internal have a CNAME for mail.domain.org -> mail.domain.local? or just an A record for mail.domain.org to go to the IP of mail.domain.local?
The second option.
ASKER
Apologies on the abandoned question! I am the only IT for 325 users in 11 localities so I get called alot.
Also you can check the stats of the current connection whether it uses http ot TCP (rpc) by holding CTRL and right click on outlook icon in system try (beside clock icon).
Capture.PNG