Welcome to Scribd. Sign in or start your free trial to enjoy unlimited e-books, audiobooks & documents.Find out more
Standard view
Full view
of .
Look up keyword
Like this
0 of .
Results for:
No results containing your search query
P. 1
Exchange Server 2003[1]

Exchange Server 2003[1]



|Views: 876|Likes:

More info:

Published by: tokumarshyam123@gmail.com on Aug 29, 2008
Copyright:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as DOC, PDF, TXT or read online from Scribd
See more
See less





Exchange Server 2003
Ports Used in Exchange Server 2003
The following table lists Exchange Server 2003 services and their corresponding ports. For moreinformation about how to configure Exchange front-end servers, including the ports that areassociated with various scenarios, see the technical article,Using Microsoft Exchange 2000 Front-End Servers. Although that article relates to Exchange 2000 Server, the information applies toExchange Server 2003 as well.
Ports used in Exchange 2003
Ports inboundPorts outbound (initiateconnections to) Notes
Microsoft ExchangeSystem Attendant135 & other RPCOther portsrequired for RPCover HTTPAll core Exchange services require the MicrosoftExchange System Attendant.For more information about RPC over HTTP portconfiguration, see the guide Exchange Server 2003RPC over HTTP Deployment Scenarios.Microsoft ExchangeInformation Store(Microsoft ExchangeSystem Attendant)135 & other RPCOther portsrequired for RPCover HTTPUser Datagram Protocol (UDP) packets to random ports for new mail notificationRuns the Exchange databases.For more information about RPC over HTTP portconfiguration, see the guide Exchange Server 2003RPC over HTTP Deployment Scenarios.Microsoft ExchangeMTA Stacks(Microsoft ExchangeSystem Attendant)135 & other RPC102 for X.400over TCP135 & other RPC102 for X.400 over TCPMicrosoft Exchange MTA Stacks are required for legacy connections to Exchange Server 5.5 servers.Port 102 opened only for active X.400 connections.Simple Mail Transfer Protocol (SMTP)(IIS Admin Service)2525Exchange store requires SMTPMicrosoft ExchangeRouting Engine(IIS Admin Service)691691Routing Engine serviceWorld Wide WebPublishing Service(IIS Admin Service)80 & 44380 on the front-end serverRequired for Outlook Web Access and public folder administrationExchange ActiveSync(IIS Admin Service)UDP 2883 on the front-endserver Required for SP2 Exchange ActiveSync Direct PushMicrosoft ExchangePOP3(IIS Admin Service)110 & 995 (SSL)110 on the front-end serverRequired for POP3 accessMicrosoft ExchangeIMAP4(IIS Admin Service)143 & 993 (SSL)143 on the front-end serverRequired for IMAP4 access Network NewsTransfer Protocol(NNTP)(IIS Admin Service)119 & (563 SSL)N/AMicrosoft ExchangeSite ReplicationService379, 135 & other RPC135 & other RPCDepends whether Exchange Server 5.5 servers are inthe organization.Active Directory NA379, 389, can be configuredDepends whether Exchange Server 5.5 servers are in
Connectorthe organizationMicrosoft ExchangeEvent(Microsoft ExchangeInformation Store) Not automatic by defaultExchange Management(WindowsManagementInstrumentation)This is not a required service; however, MicrosoftOperations Manager and other programs do notfunction without this service.
Port 445 is required for Message Tracking
Exchange Server 2003
Technical Details of Using RPC over HTTP to AccessExchange from an Outlook Client
RPC over HTTP allows Microsoft® Office Outlook® 2003 clients to access Microsoft Exchange serversby using the MAPI protocol to tunnel Outlook RPC requests inside an HTTP session, or tunnel.Typically, an Outlook 2003 client contacts an Exchange server over a TCP session.If you use RPC over HTTP, you can use Outlook 2003 to access Exchange Server over the Internet,because HTTP is a common Internet protocol. The HTTP session terminates at a server runningInternet Information Services (IIS) that has the Microsoft Windows Server™ 2003 RPC over HTTPProxy networking component installed. This server is called an RPC proxy server.It is recommended that your RPC proxy server is an Exchange front-end server. The RPC over HTTPProxy networking component extracts the RPC requests from the HTTP request and forwards theRPC requests to the appropriate server. The advantage of this approach is that only the RPC proxyserver has to allow access from the Internet. Back-end Exchange servers do not have to allowaccess from the Internet. You should use the Secure Sockets Layer (SSL) to establish the HTTPsession that you use to access Exchange Server over the Internet from an Outlook 2003 client.A common misconception is that the use of RPC over HTTP turns a Web request into an RPCrequest. Outlook 2003 sends the RPC request inside an HTTP tunnel. The actual RPC request doesnot change between the Outlook client and the Exchange server.The following figure shows an RPC request inside an HTTP tunnel.
RPC request inside HTTP tunnel
Protocol: LDAP
Port (TCP/UDP): 389 (TCP)
Description: Lightweight Directory Access Protocol (LDAP), used by ActiveDirectory, Active Directory Connector, and the Microsoft Exchange Server5.5 directory.
Protocol: LDAP/SSL
Port (TCP/UDP): 636 (TCP)
Description: LDAP over Secure Sockets Layer (SSL). When SSL is enabled,LDAP data that is transmitted and received is encrypted.
To enable SSL, you must install a Computer certificate on the domaincontroller or Exchange Server 5.5 computer.
Protocol: LDAP
Port (TCP/UDP): 379 (TCP)
Description: The Site Replication Service (SRS) uses TCP port 379.
Protocol: LDAP
Port (TCP/UDP): 390 (TCP)

Activity (13)

You've already reviewed this. Edit your review.
1 hundred reads
1 thousand reads
ypatil_639212631 liked this
Bharat Raj liked this
Suman Ganesh liked this
abusidik liked this
rajasmohan liked this
Bien Phung Van liked this
pkch151 liked this
sevn12345 liked this

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->