internal clients connect to exchange 2010 through SCP in autodiscover service.-2010, 2013
in 2010 through RPC/TCP and in 2013 RPC/Https. what steps needs to check if internal outlook clients cannot connect both for exchange 2010, 2013
External clients using OWA connect through autodicover. domain.com. for exchange 2010 , if cannot connect through owa, what steps need to be checked.
external clients through OWA to exchange 2013-how it works
ExchangeOutlookWindows Server 2008
Last Comment
Amit
8/22/2022 - Mon
Amit
Goto to exrca.com website. Click on Client tab, install and run the tool. This will tell you the reason for failure.
Adam Farage
Your question is pretty fragmented, but I will say this..
If you have Exchange 2013 implemented in production, and users are there you should make Exchange 2013 the endpoint for your connections. This means changing the autodiscover scope to point to the Exchange 2013 CAS (SCP, DNS A records in the forward lookup zone, ect) along with DNS A records for OWA, EAS, ect.
Try that first and then check back.. unless you have something more specific you had in mind that is not working.
pramod1
ASKER
my question was how do outook clients whose computers are configured in domain connect to exchange 2013
as in exchange 2013 it is rpc/htts so they don't use RPC 135 ?
or they use outllok anywhere from inside the network. for users connecting from internet to exchange 2013
like using OWA, they connect to autodiscover and how they get exchange attributes ?
like internal clients get through SCP , how about external clients