Outlook Anywhere and open ports (Full Version)

All Forums >> [Microsoft Exchange 2007] >> General



Message


matarvai -> Outlook Anywhere and open ports (3.Nov.2008 11:34:00 PM)

I understand that when using Outlook Anywhere feature I only need 443 (https) port open. However in our environment I needed to open also 135, 587 and 1029 ports to get it work. Is this always necessary, or is this some kind of error in installation?




Elan Shudnow -> RE: Outlook Anywhere and open ports (4.Nov.2008 12:08:47 AM)

You only need 443 from client to server. Other ports will need to be opened for server to server communications.

If you're ever curious as to what ports are needed for anything Exchange 2007 related, go here:
http://technet.microsoft.com/en-us/library/bb331973(EXCHG.80).aspx




matarvai -> RE: Outlook Anywhere and open ports (4.Nov.2008 12:24:24 AM)

What could be problem, cause I need those other ports open, if those ain't open I cannot login to Outlook with outlook anywhere.




Elan Shudnow -> RE: Outlook Anywhere and open ports (4.Nov.2008 12:28:14 AM)

Sounds like you're not really logging into Outlook Anywhere.  Try holding Control + Click on Outlook icon in Notification Area and then choose Connection Status.  What does it show under the Conn column?  Does everything show as HTTPS?




matarvai -> RE: Outlook Anywhere and open ports (4.Nov.2008 12:30:23 AM)

Everything shows as HTTPS




Elan Shudnow -> RE: Outlook Anywhere and open ports (4.Nov.2008 12:35:04 AM)

Well for one, RPC doesn't need to be opened.  The whole point of RPC/HTTPs (Outlook Anywhere) is that RPC gets tunneled over HTTPs.  587 is for POP3/IMAP4 SMTP.  1029 isn't even on the Data Security Path reference.  Is Outlook completely up to date?  Does this happen on all clients or just one client?  Have you tried another machine with Outlook on it?




matarvai -> RE: Outlook Anywhere and open ports (4.Nov.2008 12:37:35 AM)

Yes, I have tried 2003 and 2007 clients. And it happens on every computer. I will update the server and clients later and try again after that.




Page: [1]