Re: Open Ports required for RFC over HTTP
- From: "Brian Desmond [MVP]" <desmondb@xxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 31 Mar 2005 17:08:28 -0600
Harold-
The only thing you need open facing the world is port 443. All those other
ports - opening them negates the whole idea of rpc/http and leaves your
server wide open for the world.
--
--Brian Desmond
Windows Server MVP
desmondb@xxxxxxxxxxxxxxxxxxxx
www.briandesmond.com
"Harold Bruce" <Harold Bruce@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:CE0C7650-B83B-4471-B83B-F02823E5325A@xxxxxxxxxxxxxxxx
>I have an Exchange 2003 (SP1) single server that I have configured for RFC
>or
> HTTP. It works great if we are inside the firewall, but outside, it never
> connects. I know it is a firewall issue because we turned the firewall
> off
> for the IP of the server.
>
> My question is: what ports are required to be open for RFC over HTTP?
> I had the following ports open: 110, 995, 25, 143, 993, 80, 21, 443, 691,
> 389, 3268, 88, and 135.
>
> We actually run SurfControl on the server, so it is listening on port 25
> while Exchange is set to listen on port 26. Do I need to open port 26?
> Is
> there anything I am missing?
>
> Thanks
.
- Follow-Ups:
- Re: Open Ports required for RFC over HTTP
- From: Harold Bruce
- Re: Open Ports required for RFC over HTTP
- From: Phil Hunt
- Re: Open Ports required for RFC over HTTP
- References:
- Open Ports required for RFC over HTTP
- From: Harold Bruce
- Open Ports required for RFC over HTTP
- Prev by Date: Re: Owa Setup
- Next by Date: Messages stuck in "Messages awaiting directory lookup"
- Previous by thread: Open Ports required for RFC over HTTP
- Next by thread: Re: Open Ports required for RFC over HTTP
- Index(es):
Relevant Pages
|
Loading