Exchange 2010 - what is an ''internet-facing Client Access server ?"

Line One
Line One used Ask the Experts™
on
I keep reading in Exchange 2010 setup guides references to : " internet-facing Client Access server".

What is the difference between an " internet-facing Client Access server" and a non- internet-facing Client Access server?  

Is there some special networking considerations/configuration for one versus the other - e.g. one has to have a public IP and the other a private?

Can I have both kinds in an Exchange 2010 environment?

Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Awarded 2009
Top Expert 2010
Commented:
An internet facing client access server is one that is accessed from the internet.  A non-internet facing client access server is not accessed from the internet directly but provides Outlook and re-directed OWA access.
JamesSenior Cloud Infrastructure Engineer
Commented:
The internet facing client access server provides services for external services such Microsoft Active Sync, OWA, Outlook Anywhere etc.
Ensure you’re charging the right price for your IT

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

Author

Commented:
Thanks. I think I understand the differences.  However still not sure about the answer to my two questions:

Is there some special networking considerations/configuration for one versus the other - e.g. one has to have a public IP and the other a private?

Can I have both kinds in an Exchange 2010 environment?

And  a new thought building from that: If I can have both simultaneously in the same Exchange deployment, is there any special configuration for the two of them to inter-communicate? Is there any need for that? Coordinating/synchronizing a user's internal and external mail?
Awarded 2009
Top Expert 2010
Commented:
>>Is there some special networking considerations/configuration for one versus the other - e.g. one has to have a public IP and the other a private?

No, your public IP is assigned to the router, not the Exchange Server.

>>Can I have both kinds in an Exchange 2010 environment?

Yes, but it's unlikely if you don't have multiple sites.

Let me give you an example.

You have 2 Buildings connected via a WAN/VPN etc.  This connection uses your WAN for internet access and doesn't have a dedicated internet service.

You have Exchange and you have a mailbox server & client Access server at the site that doesn't have internet access.  This CAS server is servicing your outlook clients at this site.  This is a non-internet facing Client Access Server because it doesn't have internet access from that site and your users don't access the CAS from the internet.

You have a main site that does have internet access, and all of your users use this connection to get access to OWA, ActiveSync, Outlook Anywhere, this site has an Internet-Facing Client Access Server.  It will proxy requests to the non-internet facing client access server should a mailbox reside on the other site and a user accesses it externally.

Author

Commented:
Thanks. That makes it quite a bit clearer.  If I understand it correctly having a non-Internet facing CAS by itself doesn't make much sense.  I would always have an Internet-facing CAS in any Exchange environment and any non-Internet-facing CAS would be in addition to that as circumstance dictated e.g. multiple sites.
Awarded 2009
Top Expert 2010

Commented:
correct :)

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial