[THIN] Re: OT: Exchange thru internet

  • From: Henry Sieff <hsieff@xxxxxxxxxxxx>
  • To: "'thin@xxxxxxxxxxxxx'" <thin@xxxxxxxxxxxxx>
  • Date: Wed, 27 Aug 2003 16:07:20 -0500

You can change the endpoint itself (the link I sent describes that process).
The endpoint mapper is a different ball of wax. If you did actually do that,
then I am absolutely all ears, since this is a perennially recurring topic
on several security mailing lists I am on, and the general consensus has
always been: don't allow exchange access direct from the internet because of
all the nasties out there.
 
Anyways, let me know what you find.

-----Original Message-----
From: Magnus [mailto:magnus@xxxxxxxx]
Sent: Wednesday, August 27, 2003 3:29 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: OT: Exchange thru internet


If I recall correctly we did change the RPC endpoint for it.  I will have to
double check my notes though (I could be wrong)

-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf
Of Henry Sieff
Sent: Wednesday, August 27, 2003 3:20 PM
To: 'thin@xxxxxxxxxxxxx'
Subject: [THIN] Re: OT: Exchange thru internet


Nope. You can change the ports exchange uses, but not the RPC endpoint
mapper port on 135.
 
http://support.microsoft.com/default.aspx?scid=kb;en-us;155831
<http://support.microsoft.com/default.aspx?scid=kb;en-us;155831>  details
how to change the ports exchange uses, but there is no way to change the RPC
endpoint mapper service port number. Keep in mind that the client still has
to identify which ports the exchange service is listening on, and that
requires a service which uses a port that the client knows about ahead of
time, in this case, RPC on 135.
 
 
 
 

-----Original Message-----
From: Magnus [mailto:magnus@xxxxxxxx]
Sent: Wednesday, August 27, 2003 11:02 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: OT: Exchange thru internet


Actualy you change change the port to a static port(by default it will
dynamically assign the port once it gets connected) even the TCP 135 port.
There are a couple of MS KB's on it (sorry I dont have the numbers)  I ended
up calling ms and I had it set up in about 20 minutes
 
Magnus

-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf
Of Henry Sieff
Sent: Wednesday, August 27, 2003 11:49 AM
To: 'thin@xxxxxxxxxxxxx'
Subject: [THIN] Re: OT: Exchange thru internet


To use the full exchange server client, you must open up the RPC endpoint
mapper port (135). You can set which port exchange actually ends up using,
but 135 is used to initiate the process whereby the client learns that port
number.
 

-----Original Message-----
From: Michael Boggan [mailto:MBoggan@xxxxxxxxxxx]
Sent: Wednesday, August 27, 2003 10:41 AM
To: 'thin@xxxxxxxxxxxxx'
Subject: [THIN] OT: Exchange thru internet


I want to be able to hit my exchange thru the internet but to do it it says
that the RPC port 135 has to be opened.  Well I don't want to do that for
obvious reasons.  Is there a way to change which port the RPC uses for
exchange?  

_________________________________

Michael Boggan
Network Engineer/Citrix Admin
Virtual Desktop Inc.
Dallas, Texas
Ph: (972) 960-6400
Fax: (972) 960-6445
email: mboggan@xxxxxxxxxxx
http://www.virtualdesktopinc.com <http://www.virtualdesktopinc.com/> 
_________________________________

For Technical Support during business hours please send email to
support@xxxxxxxxxxx or call the above toll free number for afterhours
support.

 

Other related posts: