Nice... Can I demonstrate how unsecure that is? Your DMZ is virtually useless in this scenario. Might I suggest and SSL key?
-------------------------------------------- Don Ely Network Engineer Tripath Imaging, Inc. (336) 290-8293 - Direct (336) 516-4519 - Mobile [EMAIL PROTECTED] - email http://www.tripathimaging.com -----Original Message----- From: McCready, Robert [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 18, 2002 11:13 AM To: MS-Exchange Admin Issues Subject: RE: OWA Ports Affirmative. -----Original Message----- From: Martin Blackstone [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 18, 2002 10:16 AM To: MS-Exchange Admin Issues Subject: RE: OWA Ports So you have OWA in the DMZ then? -----Original Message----- From: McCready, Robert [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 18, 2002 6:41 AM To: MS-Exchange Admin Issues Subject: OWA Ports Exchange 5.5, NT 4.0. OK. We are using OWA. Apparently, each time the Exchange Server is rebooted, it randomly assigns ports for the directory and information store by default, therefore, the ports that the client will use must be statically mapped. Following the OWA instructions, I made the following registry entry to TRY and accomplish the static mapping..... HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MS Exchange ServerDS\Parameters: >From here, I selected EDIT - NEW - DWORD VALUE. I then typed in TCP/IP port for the ENTRY and typed the port number in under VALUE. I also did the same for HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MS Exchange ServerIS\ParametersSystem: However, each time I reboot, a new port number is assigned. Has anybody else had this problem? Thanks. Robert List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
