=======================================================================
                   Netscape Enterprise Server 2.0 (Windows NT)
=======================================================================

Thank you for purchasing the Netscape Enterprise 2.0 server. The 
Enterprise server is subject to the terms detailed in the license 
agreement file called license.txt.

To see answers to frequently asked questions (FAQs), technical notes,
and links to other information (such as the Netscape User Group),
go to the following link:

http://home.netscape.com/assist/support/server/

For LiveWire release notes, see:

http://home.netscape.com/eng/LiveWire/relnotes

and look for the file corresponding to your platform (for example,
win-1.0.html for Windows NT).

=======================================================================
                   Installation Requirements
=======================================================================

* A minimum of 32MB RAM is required to run the Enterprise server. 
  System memory is checked during installation; if your system 
  has less than 32MB of RAM, a dialog box appears asking if you
  want to exit the installation program.

  You can install and run another instance of the web server with 
  32MB of RAM. To install and run additional web servers, each 
  will require an additional 16MB of RAM. For example, if you plan
  to run 3 web servers, your system needs 48MB of RAM. 
  
* Your system must be running Windows NT 3.51 or 4.0. If you are
  running Windows NT 3.51, you must install Windows NT Service 
  Pack 4 or later. Service Pack 4 is a collection of bug fixes from 
  Microsoft. You can get the latest NT Service Pack from Microsoft 
  at:
         
      http://www.microsoft.com

* Before you can install the server, you must have installed
  Netscape Navigator 2.0 or higher or Netscape Navigator Gold 
  (included on the CD). JavaScript must also be enabled in 
  Netscape Navigator before you can administer your server using
  the Server Manager forms.

* If you intend to use host names during the Enterprise server
  installation, make sure that DNS is properly configured and that
  your server has an entry in a DNS server. If you are having
  problems using host names during installation, edit the HOSTS 
  file in /System32/drivers/etc to include the IP address and
  complete host name, and then reinstall the server.


=======================================================================
                    Installation Instructions
=======================================================================

To install the server,

1.  Put the CD-ROM in the drive, and then choose File|Run from the
    Program Manager. 
2.  In the dialog box that appears, type
    D:\INTEL\ENTPRISE\E32D20.EXE for the domestic version, or
    D:\INTEL\ENTPRISE\E32E20.EXE for the export version, where
    D: is the drive letter for your CD-ROM drive. 
    Press Enter. The Netscape Enterprise Server Installation dialog
    box appears. 
4.  Click Yes to continue. The files are extracted, and the Welcome
    screen appears. 
5.  After reading the Welcome screen, click Next. 
6.  The Software License Agreement appears. Click Yes to accept
    the license. 
7.  The Choose Destination Location screen appears. The default
    location for the server files is C:\Netscape\Server. You can
    choose a different directory, but the directory name should not
    contain any spaces in it. Click Next. The installation program
    copies the server files to the directory you specified. 
8.  The Configure Netscape Enterprise Server 2.0 screen appears.
    Click Next. 
9.  Type the full name of your server, and then click Next. If you
    have an entry in a DNS server, your server name appears as the
    default choice.
10. Type the username for administration server access; the default is
    "admin". Type the administration server access password; type it
    again for verification. Click Next. 
11. Type the port the administration server runs on. This can be any
    number from 1 to 65535. The default port is a randomly generated
    number in this range. Click Next.
12. Type the user account name that the server will start as and
    run under. This user has write permission to the configuration
    files that control the server. The default is LocalSystem. You
    can also change the user account name using the Server Manager
    after you’ve completed the installation. Click Next.
13. Type the path for your primary document directory, which is
    where your server's content files will be stored. The default
    document directory is C:\Netscape\Server\docs. Click Browse to
    navigate your filesystem. 
    Note: If you enter an existing document root, the sample HTML
    files won't be copied to the existing document root. 
14. The Finish screen appears. Click Finish. Your new server's home
    page appears after installation is complete. 

	
=======================================================================
                   Upgrading from a 1.1x Server
=======================================================================

If you had NSAPI enabled for your 1.1x server and you upgrade it to a
Enterprise server, it might not start up after the upgrade. Open the
obj.conf file in [ServerRoot]/https-[server_identifier]/config and
comment all the lines that call NSAPI (add the # character at the
beginning of the line you want to comment). Restart the server. 
In order for your 1.1x server's NSAPI programs to work with Enterprise,
you need to recompile them using the new 2.0 header files. 

Wildcard restrictions on host names and IP addresses for access control
work differently in Enterprise than they did in the 1.1x servers. If
you used wildcard restrictions in your 1.1x servers, see the 
information available from the Tech Notes link at:

  http://home.netscape.com/assist/support/server/


=======================================================================
                   Troubleshooting
=======================================================================

* If you are using a DNS server that does not provide reverse
  name-lookup service or has not been configured properly for
  reverse DNS lookups, the Enterprise administration server
  response time might be affected. More information is available 
  from the Tech Notes link at:

  http://home.netscape.com/assist/support/server/

* The Enterprise server CGI does not export all system environment 
  variables to the CGI process (as was the case for 1.1x servers).
  Only a select set of variables are exported for Enterprise, as 
  specified in the CGI specification. If you have CGI scripts 
  that might use variables that are not exported, you can enable
  loading of all environment variables by adding the following line
  to the top of your obj.conf file (which is located in the
  [ServerRoot]/https-[server_identifier]/config directory):

  Init fn=cgi-init load-server-vars=true

* When working with Server-Side Includes (SSI), the DOCUMENT_URI 
  variable does not get set in some cases.

* The Enterprise 2.0 server supports the WinCGI 1.3a informal
  specification, with the following differences:

    - The keyword Document Root in the [CGI] section might not
      refer to the expected document root because the Enterprise
      server does not have a single document root. The directory
      returned in this variable is the root directory for the
      WinCGI program.
    - The keyword Server Admin in the [CGI] section is not 
      supported.
    - The keyword Authentication Realm in the [CGI] section
      is not supported.
    - Forms sent with multipart/form-data encoding are not
      supported.

* All access-control passwords, including the administration 
  server password, are limited to a length of 8 characters. 
  This limit doesn't apply to SSL key passwords.

* If you are using Navigator 2.0 or Navigator Gold 2.01, after
  making a selection from the Resource Picker drop-down list,
  click the form for the change to take effect. You do not
  need to do this if you are using Navigator 3.0 or later.

* When using the AutoCatalog feature, you can only stop or
  kill the catalog agent and stop enumeration by using the
  command line. Do not use the Server Manager (AutoCatalog|
  Manually Control form) to stop or kill the catalog agent 
  or stop enumeration.

  * To stop the catalog agent, use the File Manager to go to
    [ServerRoot]\plugins\autocatalog\bin, and double-click on
    stop.exe.

    [ServerRoot] is your server root directory. 
  
  * To kill the catalog agent, use the File Manager to go to
    [ServerRoot]\plugins\autocatalog\bin, and double-click on
    kill.exe.

  * To stop enumeration, use the File Manager to go to
    [ServerRoot]\plugins\autocatalog\bin, and double-click on
    finish.exe.

* To get help for a Server Manager form, click the Help button. 
  A help window appears showing context-sensitive information 
  about the form. You can print any of the help windows by 
  pressing Control-P, which brings up a Print dialog box.

* If your server is running in unsecure mode, make sure you
  don't select the 128 bit key size in the Encryption|Stronger
  Ciphers form (in Server Manager).

* SSL 3.0 is currently only supported in Netscape Navigator
  version 3.0 or later. Keep this in mind if you choose
  to turn on only SSL 3.0 (and not SSL 2.0).

* If you manually edit any configuration files, make sure you
  don't have any spaces around the equal signs for the function
  names. For example, the lines should appear like the following:
      fn="flex-log" name="global"

  
=======================================================================
