RE: [FW1] Re: SecuRemote and Outlook Client

[Lowell Heddings <Lowellh () ICN com>]

Exchange server uses a random RPC port... but you can set it to be static by
modifying the following registry keys:

SYSTEM\CurrentControlSet\Services\MSExchangeDS\Parameters
TCP/IP port=dword:1262
SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem
TCP/IP port=dword:1263
SYSTEM\CurrentControlSet\Services\MSExchangeSA\Parameters
TCP/IP port=dword:1264

This might be part of your problem.... (of course, make sure these ports are
open) You can use any ports there that you would like.

Lowell Heddings


-----Original Message-----
From: Kaptain [mailto:kaptain () kaptain com]
Sent: Thursday, April 22, 1999 1:05 PM
To: Brad Hutchins
Cc: fw-1-mailinglist () lists us checkpoint com; firewall-wizards () nfr net
Subject: [FW1] Re: SecuRemote and Outlook Client



On Wed, 21 Apr 1999, Brad Hutchins wrote:

> I am trying to get a MS Outlook client to contact an Exchange server
> behind Firewall-1 with SecuRemote and the exchange protocol.
>
> Using FW-1 v4.0 sp1, SR v4.0 build 4005, exchange server 5.5 and outlook
> 98.
>
> TCP/IP, and netbios works fine.  I can see the exchange server and any
> NT files shares that it has.  I can even connect to the exchange server
> via POP-3.  But I cannot connect via the Exchange Protocol to see all
> the public shares.
>
> It appears that the initial request from the client is being decrypted
> by the Firewall, but no return connection are occuring and Outlook times
> out.
>
> Any help is appreciated.
>
> BH
I'm not sure how your firewall is interacting with Outlook, but I've found
timeout problems with Outlook to be related to DNS issues in the past.



============================================================================
====
     To unsubscribe from this mailing list, please see the instructions at
               http://www.checkpoint.com/services/mailing.html
============================================================================
====