Outlook access through a firewall
- From: "Mierdaan" <goeman@xxxxxxxxx>
- Date: 28 Jul 2005 09:04:31 -0700
Greetings,
We're currently trying to get Outlook working through a firewall, and
connected to Exchange 2000. I've read from multiple sources that this
requires locking down the high-numbered ports that the RPC Endpoint
Mapper hands out (via a registry edit), then opening up TCP port 135
and the high-numbered ports in the firewall.
We've done this, and for some reason it seems to not be working. We
set up an access rule and a translation rule in our PIX, identical to
the one that allows HTTP traffic to the Exchange server for OWA (except
for port 135 instead of 80). However, when telnetting to the outside
address specified in the translation rule on port 135, we get no
answer; the connection isn't refused, it just hangs while trying to
make the connection. Doing the same thing from inside the network
yields a familiar input prompt, indicating that the service is indeed
listening.
Since the access list and translation rule we set up are identical to
the (working) one allowing HTTP traffic through, we think that this
isn't a firewall issue. Is there any setting in Exchange that would
deny connections on port 135 to things, say, outside of the subnet? I
know you can configure access restrictions on the built-in
HTTP,IMAP,POP3 servers, but I find no similar setting that would
explain what we're seeing.
Any advice appreciated.
.
- Follow-Ups:
- Re: Outlook access through a firewall
- From: Mark Arnold [MVP]
- Re: Outlook access through a firewall
- Prev by Date: Re: display names
- Next by Date: OWA puts additional character into each message
- Previous by thread: Scheduling an E2K3 Integrity Check?
- Next by thread: Re: Outlook access through a firewall
- Index(es):
Relevant Pages
|
