RE: Port 135 - 139

  • From: "Mulnick, Al" <Al.Mulnick@xxxxxxxxxx>
  • To: "'[ExchangeList]'" <exchangelist@xxxxxxxxxxxxx>
  • Date: Thu, 10 Jun 2004 14:55:49 -0400

What that article is doing, is allowing you to pre-specify the ports that
RPC will give back to the client.  Normally, this is a process where the
client attaches to the RPC negotiator and negotiates a port in the ephemeral
range (above 1024).   If you make those settings on your Exchange server(s)
and GC(s), you're just telling the negotiator to hand out the same ports
each time.  You still need the negotiation which occurs on those potentially
blocked ports.

RPC/HTTP operates over TCP 443 but requires new OL2003 clients on
XP+SP1+hotfix and Windows2003/Exchange 2003 infrastructure making it not as
popular if you haven't upgraded so far.  One of the more popular features as
I understand it ;)


-----Original Message-----
From: Leonard [mailto:lmwangi@xxxxxxxxxxx] 
Sent: Thursday, June 10, 2004 1:51 PM
To: [ExchangeList]
Subject: [exchangelist] RE: Port 135 - 139

Am looking at deploying RPC/HTTP but the article that Microsoft has
specifies changing the Exchange SA TCP ports

But in my exchange server registry i dont have TCP/IP key entries. Should I
add this keys or does anyone has a suggestion on hoe to go around it?


List Archives:
Exchange Newsletters:
Exchange FAQ:
Other Internet Software Marketing Sites:
World of Windows Networking: Leading
Network Software Directory:
No.1 ISA Server Resource Site: Windows Security
Resource Site: Network Security Library: Windows 2000/NT Fax Solutions:
You are currently subscribed to this Discussion List as:
al.mulnick@xxxxxxxxxx To unsubscribe visit

Other related posts: