Re: Open Ports required for RFC over HTTP

Brian,

We actually had them remove all port blocking for the IP associated with our
Exchange 2003 server. Via wireless or wired on the same subnet (inside our
firewall), we can successfully connect to the exchange server. Across
campus, on a totally different subnet (outside the firewall, although all
ports are open for the exchange server), we can via wireless or wired connect
via RPC over HTTP.

At home, using a broadband ISP, neither myself or my assistant cannot
connect successfully. What do I need to look at? Is there any way to trace
from home or setup tracing on the exchange server to see what the deal is?
We have tried using the DNS name and IP address, with the same non-results.

Thanks!
harold

"Brian Desmond [MVP]" wrote:

> 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
>
>
>
.

Relevant Pages

  • Re: How to Maintain an IIS Server?
    ... > server running on a Windows 2000 server. ... before a firewall and antivirus have been installed]. ... open ports; however, this will not identify which program is using the port. ...
    (microsoft.public.inetserver.iis.security)
  • Re: CEICW fails at firewall config
    ... ISA Server prevents connection to a remote desktop when you connect through ... Remote Web Workplace on a Windows Small Business Server 2003-based computer ... Acceleration Server as a firewall. ... connection uses TCP port 4125. ...
    (microsoft.public.windows.server.sbs)
  • Re: How to Maintain an IIS Server?
    ... >> server running on a Windows 2000 server. ... > before a firewall and antivirus have been installed]. ... > program or executable using that port. ...
    (microsoft.public.inetserver.iis.security)
  • Re: OMA?
    ... You would need to open up port 80 to the Exchange server only. ... > would I have to open up port 80 on my firewall, ...
    (microsoft.public.exchange.connectivity)
  • Re: Activesync / Airsync - Alternative Ports
    ... Setup a reverse HTTP proxy. ... Another idea is to use the PPTP capabilities of a Windows Server to allow ... Satellite - Cisco Firewall - Exchange Server ... So on the server side you would configure the port 80 to redirect to ...
    (microsoft.public.pocketpc.activesync)