Changing the Configuration of NetWare Remote Manager Views

To access the NetWare Remote Manager Configuration Options page, log in to the server as a user with the Supervisor right to the Server object, and then click the Configure icon in the header frame.

From the NetWare Remote Manager Configuration Options page, you can:

• Toggle settings off or on for viewing hidden SET parameters, hidden console commands, or hidden files or folders; or you can toggle settings for viewing system files or folders.

  These options let you control whether hidden SET parameters, console commands, or file and system folders and files appear in the lists on Web pages for NetWare Remote Manager or on the server console.

  Viewing hidden parameters or system files and folders can be especially helpful when you are comparing the configuration of two similar servers.

  You can change a hidden SET parameter or use console command using NetWare Remote Manager or using server console commands, whether or not the parameter is visible in the list.

  Viewing hidden console commands can help you discover undocumented commands.

• Enable or disable the Accessibility option.

  This option lets you control whether your browser's pages refresh or reload manually or automatically; the option also allows you to display the server's overall health status with text as well as color.

  Enabling the accessibility options does the following:

  • Removes the Refresh button or link from all pages.
  • Disables the refreshing of the server's overall health status.
  • Displays the server's overall health with color and with a text description of good, suspect, or bad.

    If you have lost connection with the server, a Page Not Found error is displayed.

    The status information on a specific page or the server's overall health does not change until you manually reload or refresh the overall browser view or the specific status page.

  To change the browser display after changing the accessibility options, refresh or reload the Web page in the browser.

  Whether the accessibility options are enabled or disabled, you can be notified of a change in the server's health status through e-mail notification.

  You must set all other accessibility options using the options available in your Web browser.

• Enable or disable the Emergency (Sadmin user) account and set, change, or clear the password for this account.

  If the server is in a state where Novell^® eDirectory^TM is not functioning correctly, you can log in to the server as this user and do all the necessary diagnostic and debugging tasks that do not require eDirectory.

• Control HTTP logging.

  When instructed by Novell Technical Services^SM, you can use the Turn Debug Screen On option to help debug a problem with the HTTPSTK module. You must also click the Turn Logger On button. The debug console screen journals debug information for the HTTP stack running on the server. This log shows every connection to your server and shows which pages are accessed with a time stamp. You can view information on every instance of any request from a workstation. By clicking this button, you effectively turn on the HTTP logging function.

  If you want to view detailed information about the access to your server that was made using the HTTP command, click the View button for the View Current HTTP Log File option.

  The log file contains the following information: an entry number; the date and time stamp in Greenwich Mean Time (GMT); host name; the program making the call; the level of the call (whether it's done by the server or by users); and a description of the entry itself with information including IP address of the source machine making the request, messages, status, etc.

  If logging has been turned off, clicking this button will turn it on.

  A plain text file of the log resides at SYS:\HTTPLOG.TXT; however, the information is much easier to understand when viewed using the View Current HTTP Log File option because it formats it in a table form. Also, this file is not viewable while the logging is turned on unless you view it in NetWare Remote Manager. To view the file in its raw form, logging must be turned off so the file is no longer open.

  The Reset Current HTTP Log File option clears the current log and begins a new one. Restarting the log is useful if you have made a configuration change to your server and want to begin a new logging session.

  The Log Only Errors to Log File option controls whether only errors or all requests are logged to the file. When logging only errors to the file, it will take much longer to fill the file to its maximum size; however, casual access to the server is not tracked.

  The HTTP Log File Rollover Size (in Megabytes) option sets a maximum size for the HTTP log file. If the available space on your volume SYS: is limited, you might want to limit the log file to a smaller size. If you want to gather more information over a longer period of time in the log file, you might want to increase the rollover size. When the file is full, the file is deleted and restarted. Automatic rollover guarantees that if logging is on, the log file always reflects the most recent activity on the server.

  IMPORTANT:  Nothing is written to this file unless logging is turned on.

• Adjust port parameters.

  Adjusting the port parameters lets you control which ports HTTP will try to accept requests on. To return an entry to its previous setting without having to remember that setting or closing and reopening the page, click Reset before you click Apply.

• Change Minimum Startup Threads values.

  The Change Minimum Startup Threads option lets you change from the default setting to any other number. At least one thread is required and other threads will be created as needed. These initial work threads will be built between the server and browser-based clients. Thus, initial communication begins with two listener threads and 32 work threads. If 32 work threads are used up, HTTPSTK will automatically create additional threads if needed. Each thread allocates a small piece of system memory when it is started. If memory is low on your server, you might want to set this number to 4 and let more threads be created as needed.

• Change TCP Keep Alive (in Seconds) default values.

  The Change TCP Keep Alive (in Seconds) option lets you change the access time from the default value.

• Unload and reload the PORTAL or HTTPSTK NLM programs.

  After you have made changes to the server that require the PORTAL.NLM or HTTPSTK.NLM to be restarted, or after you have loaded a newer version of these NLM programs on the server, click the applicable Restart button to unload and reload the module. A message appears asking if you are sure you want to restart the module, which temporarily disables this utility. While the reset is taking place, a page appears stating that the reset is taking place. When the reset is complete, the page refreshes to the Configuration page with the changed settings if you haven't changed the port settings.

  IMPORTANT:  If you have changed the port settings, remember to use the new numbers when accessing NetWare Remote Manager.

• Access the Mail Notification Control page.

  From this page you can specify a primary mail server, an alternate mail server, up to eight users in the notification list, and a Mail From identification. You can control which items to be notified about on the Health Monitor page.

• Access the IP Address Access Control page.

  From this page you can limit access to NetWare Remote Manger. You can specify IP addresses for workstations or specify a subnet and subnet mask for ranges of workstations that you want to give access from. Restricting access to specific IP addresses or specific subnets can assist you in securing remote access to your server from NetWare Remote Manager.

  For example, if you have static IP addresses (which you could easily assign to the administrator's workstation), use the Allow Access Only from the Following IP Addresses option to control administration access. Only those workstations with a matching IP address can access NetWare Remote Manager.

  If you want a little more flexibility in your IP address assignments, such as all IP addresses within a subnet mask range, use the Allow Access Only from the Following IP Subnets option. With this setting, the IP subnet mask and the IP address are compared with a logical AND statement. If the IP address matches the subnet specified, you can access NetWare Remote Manager; if the IP address does not match the subnet, you won't have access.

  This approach works well if you are using DHCP to dynamically allocate IP addresses. In this scenario, you might not get the same address every time you call for an IP address. But because the allocated IP address will fall within the subnet mask range, you will have access to NetWare Remote Manager. But remember, so will all other workstations that fall within the subnet mask range. To prevent people on the Internet or users of other subnets from accessing NetWare Remote Manager, set up your subnet mask so that only IS workstations can use the specified subnet mask.