These options control the ports and IP address that httpstk.nlm listens on, and the keep-alive parameters, startup threads, and workstations that can access the server through Novell Remote Manager.
This section includes instructions for the following tasks:
Section 6.4.1, Changing the HTTP IP Address and Port Setup Options
Section 6.4.2, Changing the Mail Notification Configuration Options
Section 6.4.3, Changing the Default eDirectory Login Contexts Option
Section 6.4.4, Changing the Change Minimum Startup Threads Option
Section 6.4.5, Changing the TCP Keep Alive (in Seconds) Default Option
Section 6.4.6, Changing User Access by Using the IP Address Access Control Page
The link on the Novell Remote Manager Configuration Options page under the heading takes you to the HTTP IP Address and Port Set Up page where you adjust and control the ports, IP address, and security settings that HTTP tries to accept requests on. These changes integrate with the IP Address Management functionality.
On the Novell Remote Manager Configuration Options page, click the link.
Click the applicable action you want to perform.
After clicking the button, click .
If you click the button, do these additional steps:
Select the IP address that you want the port opened for, then click .
Type the port number you want to open, then click .
(Optional) If you want users to be required to log in before accessing this port, select the check box, then click and .
Click .
Another way to make Novell Remote Manager respond on multiple IP addresses is to enter the following command at the System Console prompt:
httpbind ip address or server's DNS name /keyfile:"SSL certificate name for the specified server"
For example:
httpbind 192.168.1.2 /keyfile:"SSL CertificateIP"
Make sure there are no spaces between the parameter keyfile: and the Certificate name string.
HINT:Using the and option on the Config page can prevent syntax errors.
The link on the Novell Remote Manager Configuration Options page under the heading lets you access the Mail Notification Configuration 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 and when you receive notification on the Health Monitor page.
To access the Mail Notification Configuration page, click the link.
To change any of the options, type the applicable text this the option field, then click Save.
You can also synchronize these settings with other servers in the same group using Group Operations. For more information, see Synchronizing the E-mail Notification Settings for Novell Remote Manager.
The option on the Novell Remote Manager Configuration Options page under the heading controls whether users must specify a context when they log into Novell Remote Manager. If the context is specified here, then users do not need to enter a context.
This setting is saved to the NetWare Registry and takes affect immediately without restarting Novell Remote Manager. Any bindery contexts that are set in the autoexec.ncf file are recognized before the contexts specified here.
To change the default from root, where users must specify their contexts each time they log in, enter one or more contexts for the users that will be accessing Novell Remote Manager. Separate each context specified with a semicolon (;). For example, novell; novell.sales; novell.mkrt.
This field is limited to 1000 characters. You might want to change the context for only a limited number of users.
You can also synchronize these settings with other servers in the same group using Group Operations. For more information, see Synchronizing the eDirectory Context for Users Logging in to Novell Remote Manager.
The option on the Novell Remote Manager Configuration Options page under the heading lets you change the server from the default setting to any other number of threads.
At least one thread is required and other threads are created as needed. These initial work threads are 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.nlm automatically creates 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 can set this number to 4 and let more threads be created as needed.
To change the values, specify the new value in the field and click Apply. To use this setting, restart httpstk.nlm. See Restarting Novell Remote Manager or the HTTP Interface.
This option on the Novell Remote Manager Configuration Options page under the heading lets you change the access time from the default value of 300, which corresponds to 5 minutes and is the standard TCP timeout time. You should only need to change this value in cases where it would be useful to change.
To change the values, specify the new value in the field and click Apply.
To use the new setting, restart httpstk.nlm. See Restarting Novell Remote Manager or the HTTP Interface.
From the IP Address Access Control page, you can limit or restore access to Novell Remote Manager.
To access this page, click the link on the Novell Remote Manager Configuration Options page under the heading
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 Novell Remote Manager.
For example, if you have static IP addresses (which you could easily assign to the administrator's workstation), use the option to control administration access. Only those workstations with a matching IP address can access Novell 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 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 Novell 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 falls within the subnet mask range, you can access Novell Remote Manager. However, 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 Novell Remote Manager, set up your subnet mask so that only Information Services (IS) workstations can use the specified subnet mask.
Resetting any of the options on the IP Address Access Control page allows access to Novell Remote Manager by all users.
To use the new setting set on the IP Address Access Control page, restart httpstk.nlm. See Restarting Novell Remote Manager or the HTTP Interface.