Solved

Outlook 2010 connecting to Exchange 2010

Posted on 2011-09-25
7
354 Views
Last Modified: 2012-05-12
Can anyone help me.  I'm trying to figure out the steps internally how Outlook 2010 [which is a MAPI client] connects to an Exchange 2010.

Does it go through the CAS first via RPC client Access service, then it re-directs it to the mailbox server.

I cannot find any documentation on this.
Thanks
0
Comment
Question by:techgenious
  • 3
  • 3
7 Comments
 
LVL 17

Expert Comment

by:Viral Rathod
ID: 36597293
With Exchange 2010, MAPI and directory access connections has also moved to Client Access Server role. This has been done by introducing a new Client Access Server service known as the RPC Client Access service.

That means that MAPI clients no longer connect directly to a Mailbox server when opening a mailbox. Instead they connect to the RPC Client Access service which then talks to Active directory and Mailbox server. For directory information, Outlook connects to an NSPI endpoint on the Client Access Server, and NSPI then talks to the Active Directory via the Active Directory driver.


http://www.msexchange.org/articles_tutorials/exchange-server-2007/planning-architecture/uncovering-new-rpc-client-access-service-exchange-2010-part1.html
0
 

Author Comment

by:techgenious
ID: 36601029
Here's a question for you and keep in mind my external networking skills are beginner.

If I want to RDP into say my network from home ,  and I want to access my Exchange 2010 server.
 
What is the process of that.  Keep in mind we have a edge server & a hub transport server.

Two Scenarios:
I connect through VPN first Cisco Any connect, then RDP into my desktop.  
Connect via OWA.

What is that process.

Thanks the article really helped.
0
 
LVL 8

Expert Comment

by:ActiveDirectoryman
ID: 36625215

you don't have to connect to via your vpn you could not forward the ports for rdp on your firewall so that when a request comes from the outside it gets forwarded to the internal port.    

yea if you are using vpn you use your vpn client to connect to your internal network and then you can RDP directly to your exchange server.  u don't event have to connect to your desktop since you would already be connected to your internal network.  You could also load exchange management tools on your workstation and manage your server that way once you are connected to your internal network. there are different ways to do it.
0
Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

 
LVL 8

Accepted Solution

by:
ActiveDirectoryman earned 125 total points
ID: 36625633
you don't have to connect to via your vpn you could forward the ports for rdp on your firewall so that when a request comes from the outside it gets forwarded to the internal port.    

yea if you are using vpn you use your vpn client to connect to your internal network and then you can RDP directly to your exchange server.  u don't event have to connect to your desktop since you would already be connected to your internal network.  You could also load exchange management tools on your workstation and manage your server that way once you are connected to your internal network. there are different ways to do it
0
 

Author Comment

by:techgenious
ID: 36692438
I understand but like what protocols are used, ports etc.   I guess it is more from a networking point of view on how to connect.

0
 
LVL 8

Expert Comment

by:ActiveDirectoryman
ID: 36704868



this question is broad keeping in mind that there are different vpn protocols out there.

lets just say you are using   pptp which stands for (point to point tunneling protocol).  from your vpn client on your home network you will establish a secure connection over port 1723 to your external firewall if that port is open.  a secure tunnel is created between the vpn client and the server. Once you are connected to your internal network you will make a remote desktop connection over port 3389 to your exchange server or whatever machine you would like to connect to.  In essence, you are making a connection then a tunnel is created between you and your network so no one can sniff through the packets going across the internet.  

0
 

Author Comment

by:techgenious
ID: 36712404
thx this helps alot you are the best
0

Featured Post

PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Not sure what the best email signature size is? Are you worried about email signature image size? Follow this best practice guide.
Marketers need statistics and metrics like everybody else needs oxygen. In this article we explain how to enable marketing campaign statistics for Microsoft Exchange mail.
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
This video discusses moving either the default database or any database to a new volume.

932 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

8 Experts available now in Live!

Get 1:1 Help Now