Re: Open Ports required for RFC over HTTP

Tech-Archive recommends: Speed Up your PC by fixing your registry

Phil,

Harold is using RPC/HTTP. This works over HTTP ports NOT RPC ports. So that
wont' be the case.

Harold - are you using a valid https cert on the frontend (and it was issued
by someone lke thawte or verisin)? That makes a differenece.

--
--Brian Desmond
Windows Server MVP
desmondb@xxxxxxxxxxxxxxxxxxxx

www.briandesmond.com


"Phil Hunt" <hunt@xxxxxxxxxxxxxx> wrote in message
news:ONSsHNVOFHA.3296@xxxxxxxxxxxxxxxxxxxxxxx
> This is probaby due to your home isp/broadband provider closing all the
> RPC
> ports 'for your protection'
>
> Pretty bad that you cannot run the client at home. If you have a user on
> the road for weeks, the only way they can connect is vpn (not practical
> for
> dialup foreign connections (way too slow)), or pop/imap, or dialup using
> ras
> on the exchange server.
>
> Groupwise can use its client at home using TCP and 2 ports.
>
> Any 3rd party apps that would allow w2k systems to connect?
>
>
> "Harold Bruce" <HaroldBruce@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:DE68DC65-198C-4F68-BD5D-D90D66FE4FF9@xxxxxxxxxxxxxxxx
>> 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: SMTP and Relay.
    ... >service provider with adsl.i am using RPC over HTTP. ... >how can i send external mail through my exchange server and ... to work with RPC over HTTPS you don't need smtp ports to be ...
    (microsoft.public.exchange.admin)
  • Re: RPC over HTTP - DS wont connect
    ... I'm trying to setup RPC over HTTP and I'm hitting a brick wall. ... I have single Exchange server and separate GS server. ... ports in the internal firewall to make it worth the while. ...
    (microsoft.public.exchange.connectivity)
  • Re: More Ports to Open?
    ... Outlook uses RPC to talk to an Exchange server. ... While it is possible to statically map all the necessary ports for Outlook ... 833401 How to configure RPC over HTTP on a single server in Exchange Server ...
    (microsoft.public.exchange.connectivity)
  • Re: Question about SMB2k3 and Exchange server
    ... We are a small company that have an Exchange server up and running ... I suggest you ditch the POP connector - it's a kluge. ... but i'm not really sure what ports i need to ... For RPC over HTTP, ...
    (microsoft.public.windows.server.sbs)
  • Re: Exchange, Outlook and DNS problem
    ... > Company deceided to switch from ISP POP3 to local Exchange server. ... > Cisco routes to local ISA IP address.ISA is configured to do RPC over ... > HTTP routing for Exchange which is also located in internal network. ... > Outlook while connected internal network. ...
    (microsoft.public.win2000.dns)