Exchange connection to remote sites

I have an exchange server at one location and have 3 remote sites.  There are DC's at all sites and are setup as Global Catalogs.  When I setup an email for new users, OWA works but configuring Outlook I cannot connect the the exchange server.  It tells me that the server is not online or not responding.  They can ping the exchange server, they can even open shared files on the exchange server.  The remote sites are connected with a T1 connection to the main office.  What port does Outlook use to connect to an Exchange server.  I was thinking it might be with the router not letting a certain packets in due to a port not opened or configured?
infranetsupportAsked:
Who is Participating?
 
dlangrConnect With a Mentor Commented:
in one of my previous posts i said:

forward https to an external ip of the main office to the exchange server in your firewall/router and configure the exchange server so that it accepts https connections.

This was written down a bit to hasty, what i meant is:

In your firewall, forward https of an external ip (at the main office) to the internal exchange server and configure the exchange server so that it accepts https connections.
0
 
knightrider2k2Commented:
It is probably port 135

http://support.microsoft.com/kb/833799
0
 
dlangrCommented:
forward https to an external ip of the main office to the exchange server in your firewall/router and configure the exchange server so that it accepts https connections.

see http://office.microsoft.com/en-us/ork2003/HA011402731033.aspx for client configuration

see http://www.msexchange.org/tutorials/Implementing-RPC-over-HTTPS-single-Exchange-Server-2003-environment.html for configuring your exchange server

It can be done without https, but then i would recommend setting up a vpn between the offices (if not already implemented)

If you do have an vpn, you will have to open up quite some ports if the traffic tunneld trough the vpn between the 2 locations is filtered.
0
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

 
dlangrCommented:
>Both Microsoft Outlook and Microsoft Exchange use the remote procedure call (RPC) >protocol to communicate. When an Exchange server starts, each of its services are >dynamically assigned to a port. The port number that each Exchange server listens >on can change every time that the Exchange server starts. When an Exchange server >starts, it registers itself with the End Pont Mapper, and prompts the End Pont Mapper >to assign it a port number.

>When Outlook starts, it must determine the port where the TCP/IP end-point on the >Exchange server has been assigned. To find the port number that Outlook must >communicate with, Outlook contacts the Exchange server's End Pont Mapper that >tracks what service is listening on what port. The End Pont Mapper always listens on >port 135.

as stated above, it uses a lot of ports, not just port 135. unless all unprivileged ports are already open, opening port 135 will probably not solve your problem.
0
 
dlangrCommented:
for a more complete list of ports and things to do, see "Preparing Exchange Server 2003 for OWA" at http://www.msexchange.org/tutorials/OWA_Exchange_Server_2003.html

It also describes a way to limit the amount of ports used.
0
 
dlangrCommented:
Did you resolve your issue? Let us know how so others can learn from it.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.