• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 5818
  • Last Modified:

outlook anywhere ports

what ports (exchange 2007 , outlook anywhere) using for external user .

Example :

i have users outside office using microsoft outlook 2007 or 2003 to connect to our exchange server 2007 using RPC (outlook anywhere) i need to know which port exchange 2007 using for outlook anywhere , because i need to configure firewall and allow only this ports
0
rabih_saleh
Asked:
rabih_saleh
  • 8
  • 4
  • 2
1 Solution
 
Sourabh-ExcahngeCommented:
only port 443 needs to be open on the firewall
0
 
rabih_salehAuthor Commented:
port 443 agree for HTTPS , but still not working because the client using RPC , (if i open all the ports it's working fine), i checked from internet i found this port 135 but still what i know there is random ports using for outlook anywhere .
0
 
MesthaCommented:
If you have to open other ports then the feature is not working correctly. It is designed to go over port 443 only. The client will attempt to make a connection on port 135, but when that fails it will connect on the HTTPS port. If that doesn't happen then something else is wrong with the setup.

You do NOT want port 135 open to the internet - not unless you want to be hacked in a few hours anyway.

Simon.
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
Sourabh-ExcahngeCommented:
if your outlook anywhere is not working that is some thing which we can troubleshoot.
dont open port 135 on the firewall.
try and brows https://owaurl/rpc/rpcproxy.dll from outside if it is giving you a blank page your firewall configuration is perfect
0
 
rabih_salehAuthor Commented:
So i can do now , i will block every thing and i will keep only 443 port ? when i type like https://my site/rpc/rpcproxy.dll i'm getting to enter user name and password it's correct like that ? or no ? and what the best solution to do ? and what port i will keep open for the outlook anywhere (client use microsoft outlook 2003 or 2007)
0
 
rabih_salehAuthor Commented:
i did now test i keep only this port 443 , only web access working perfect but the client using outlook anywhere (microsoft outlook 2003 or 2007) it will not work , but if i open all the port (because i don't know exchange 2007 which port using) it's working fine with out any problem but it's not secure at all , and regarding this link
( https://my site/rpc/rpcproxy.dll ) if i blocked all the port except 443 still i'm getting to enter user name and password , it's true or no ????


please i need your help
0
 
MesthaCommented:
Username and password prompt is fine. It will never succeed because you are not Outlook.
The test to the /rpc directory is only to prove certificate acceptance. If the certificate generates a prompt then it will not work correctly.

Test the site remotely using the Microsoft test site.
https://testexchangeconnectivity.com/

Simon.
0
 
rabih_salehAuthor Commented:
1. you told me to block this port 135 , can u explain to me this port what doing ?
2. when i block this port 135 , no any user from outside can user microsoft outlook 2007 or 2003 , what i will do now ?
0
 
rabih_salehAuthor Commented:
please can you tel me what port i need to open to keep user accessing exchange server 2007 ( web access and from microsoft outlook2007 or 2003).

443 for web access

what about microsoft outokk 2007 or 2003 using RPC from internet ?
0
 
MesthaCommented:
443 is the ONLY port you need to have open. No other port is required. Port 443 will give you access to Outlook Web Access, Exchange ActiveSync and Outlook Anywhere. It all runs over port 443.

Port 135 is the NETBIOS port.

Simon.
0
 
rabih_salehAuthor Commented:
sorry , still not working , i closed all the port except 443 , web access working perfect but microsoft outlook not working
0
 
MesthaCommented:
Outlook Anywhere either works, or it doesn't.
It has been presumed that you have installed the relevant Windows component and then enabled the feature in Exchange.

Did you test it using the test site I posted above? That will give you some diagnostic information. Stating that it "doesn't work" doesn't help anyone to resolve the issue.

Simon.
0
 
rabih_salehAuthor Commented:
Thank you very much for all it's working fine , i don't know what's happen but what i did i restart the firewall and it's working fine now
0
 
rabih_salehAuthor Commented:
thank you
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

  • 8
  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now