Yes, you have to have a digital certificate issued from a third-party like verisign, or if you are on Win2K, you can install certificate services and issue your own digital certificates faster and free of charge.
hth -----Original Message----- From: Benjamin Zachary [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 18, 2002 12:17 PM To: MS-Exchange Admin Issues Subject: RE: OWA Ports Hey , real quick do I have to do anything with certificates or verisign when changing over to 443? Or just put https://mail.domain.com ?? Thx -----Original Message----- From: Mark Kelsay [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 18, 2002 2:31 PM To: MS-Exchange Admin Issues Subject: RE: OWA Ports Move your OWA server to your protected net. Implement SSL and open up port TCP/443 to the server. Block port TCP/80 and force everyone to use SSL. I believe this is the safest way. I am sure someone here will let me know if I am wrong. Mark -----Original Message----- From: McCready, Robert [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 18, 2002 1:54 PM To: MS-Exchange Admin Issues Subject: RE: OWA Ports Exchange keeps reassigning the port numbers. We were using 1062 and 1074. Yes, the DWORD value was set to Decimal. For some reason, our registry entries don't seem to matter. Maybe I shouldn't even worry about them since the OWA server is on the DMZ? -----Original Message----- From: Ben Winzenz [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 18, 2002 9:57 AM To: MS-Exchange Admin Issues Subject: RE: OWA Ports Which port numbers are you assigning? Also, did you make sure that the DWORD value is set to Decimal, NOT Hexadecimal? I don't know if there is a specified range that you are supposed to use, but we have always used the same port numbers. Ben Winzenz, MCSE Network/Systems Administrator Peregrine Systems -----Original Message----- From: McCready, Robert [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 18, 2002 8: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 ------------------------------------------------------------ This is a disclaimer.. and we disclaim anything that gets us in trouble. -Advanced PC ------------------------------------------------------------ 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
