Mark Minasi's Reader Forum
Mark Minasi's Reader Forum
Home | Profile | Register | Active Topics | Active Polls | Members | Search | FAQ | Minasi Forum RSS Feed
Username:
Password:
Save Password
Forgot your Password?

 All Forums
 Email, Databases, Sharepoint and more
 Exchange
 Exchange 2003/Outlook 2003 - Use alternate ports?
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

tombott
Welcome Newcomer

United Kingdom
19 Posts
Status: offline

Posted - 04/29/2004 :  10:28:02 AM  Show Profile  Visit tombott's Homepage  Reply with Quote
Hi,

I am trying to configure our Exchange 2003 server (Running on Windows 2000 Server) to use different ports for communicating with Outlook 2003 across the internet.

The remote users are in the USA, and the Exchange server is in the UK. In the last few days their ISP has closed ports 135-139 because of security, so I am trying to get around this.

I have come across these MS KB articles:

http://support.microsoft.com/default.aspx?kbid=270836

http://support.microsoft.com/?kbid=833799

I followed the instructions, and gave the following ports:
Exchange SA RFR Interface: 5012
Exchange Directory NSPI Proxy Interface: 5014
Exchange Information Store Interface: 5011
Exchange Site Replication Service (SRS): 5015

I have also assigned port 4950 to the NDTS (because this server is a global catalog server).

I then ran the script file mentioned in the above MS KB article on Outlook 2003, with the following values:
TCPExchangePort=5011
TCPReferralPort=5012
TCPDirectoryPort=5014

But Outlook will not connect to Exchange.

These ports, as well as port 135 have been opened on the firewall.

Any ideas? Maybe there is something I am doing terribly wrong.

The articles are not too specific on which ports to use, so I chose the above ones.

Regards,
Tom

ledson
Major Contributor

USA
1112 Posts
Status: offline

Posted - 04/29/2004 :  10:45:40 AM  Show Profile  Visit ledson's Homepage  Reply with Quote
That does not look too safe, have you looked into RPC over HTTP? If the client is Windows XP, & the server is Windows 2003/Exchange 2003, it will work perfectly, & you can encrypt the session. (SSL)

Luke Edson

CCIE, CISSP, MCITP: Enterprise Admin & Messaging, MCSE: Security & Messaging 2000 & 2003, MCSE 2003, 2000, 4.0

http://www.edsontech.com
Go to Top of Page

dfigueiredo
Here To Stay

Portugal
182 Posts
Status: offline

Posted - 04/30/2004 :  09:50:58 AM  Show Profile  Visit dfigueiredo's Homepage  Click to see dfigueiredo's MSN Messenger address  Reply with Quote
Or use a VPN?
Go to Top of Page

tombott
Welcome Newcomer

United Kingdom
19 Posts
Status: offline

Posted - 05/17/2004 :  06:13:51 AM  Show Profile  Visit tombott's Homepage  Reply with Quote
sorted cheers. using checkpoint firewall so secure in that area, vpn wasn't an option.

I managed to investigate assigning static ports to Exchange, and came across some more information in a newsgroup.

I have now made the configuration change and it seems to be working.

The problem was that I needed to set the TCP/IP Port for NTDS to the same as the port for the Directory Proxy Service.

I gave the following ports:
Global Catalog Referral Service: 4000
Directory Proxy Service: 4001
Information Store Service: 4002

NTDS: 4001

Edited by - tombott on 05/17/2004 06:19:44 AM
Go to Top of Page

saveline
Welcome Newcomer

1 Posts
Status: offline

Posted - 06/15/2004 :  12:49:04 PM  Show Profile  Reply with Quote
Do you have the exact names of the registry keys that you have to modify on both the Exchange 2003 server and the Global Catalog server?
Did the .prf file import work correctly per MS KB 833799?

Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
Mark Minasi's Reader Forum © 2002-2009 Mark Minasi Go To Top Of Page
This page was generated in 0.14 seconds. Snitz Forums 2000