Previous Page: Remote Access Services  Next Page: Configuring ARAS

Configuring PPPRNS

Refer to the following procedures:


Specifying Optional IPX Parameters

You can assign the following parameters for a user or a container:

To configure PPPRNS, complete the following steps:

  1. Select Configure Services from the Remote Access Options window.

    The Remote Access Services window is displayed.

  2. Select PPPRNS.

    The PPPRNS Configuration Options window is displayed.

  3. Select Set IPX Parameters.

    A list of users and containers in the default Directory context is displayed.

    Select the single period (.) to set IPX information for the current container. If users are distributed over multiple contexts, select the double period (..) to move up the Directory tree to a common branch. Select names with a plus (+) prefix to move down the tree.

    If the CONNECT object does not have Browse rights to move up the Directory tree, press Ins and enter a new Directory context. This enables you to jump to another branch of the tree where the CONNECT object does have rights.

  4. Select a user or container.

    The IPX parameters window is displayed. You can set the parameters if the CONNECT object, in addition to having Browse and Read attribute rights, has Write attribute rights to that container.

  5. Select Specify IPX Address and specify Yes.

    The User IPX Parameters window is displayed.

  6. Specify the following IPX parameters:

    • IPX Address---Enter an IPX address for the user or container. The IPX address must be a unique hexadecimal number, for example, 123ABC456780.
    • IPX Address Mask---Enter a mask for the previous IPX address to provide a range of IPX addresses for the user or container. The default, FFFFFFFFFFFF, specifies a single IPX address to be used.

    NOTE:  If the highest-order byte of the IPX address is an odd number, it indicates a multicast address. Windows 95* clients (running the Novell ClientTM for Windows 95) might not be able to connect using such an address. For example, an IPX address mask of FFFFFFFFFFF0 and address of A112233445566 will cause the connection to fail. However, the address CCBBDDEEFFAA can be used.

    NOTE:  You can assign a fixed IPX address for a user or a container by entering a unique address in the IPX address field and not providing a range (keeping the default for the IPX address mask).

  7. Create a list of home servers by doing the following:

    1. Select See List and press Enter.

      Initially, the list is empty for the selected user or container.

    2. Press Ins.

      A list of server names on the network is displayed.

    3. Select one or more home servers for the user or container.

      If you select more than one home server, the user attaches to any one of the servers in the list.

    4. Press Ins and enter the server address if the server name is not displayed in the list.

      If the server is down, the server name is displayed as an IPX address.

  8. Press Esc to exit.

    The changes take effect immediately and apply the next time the user dials in.


Specifying Optional IP Parameters

You can set up your remote access server to function as a BOOTP server for remote clients. Use this option to assign IP addresses to remote access clients from the remote access server address range through BOOTP. You can also use this option when the clients want to obtain client information such as the domain name server from the remote access server. When your remote access server is configured as a BOOTP server, specify the following parameters per user or container:

NOTE:  DHCPD must be loaded for these parameters to apply.

To install the BOOTP server, complete the following steps:

  1. Enter the following command at the console prompt on the remote access server:

    LOAD DHCPD

  2. When setting up the remote access server as a BOOTP server, make sure you set the following parameters.

    • Set the Client Address Range parameter to Yes.
    • Enter the IP addresses for the Client Address Range Start and Client Address Range End parameters. If necessary, enter IP addresses for the Secondary Local IP Address, Secondary Address Range Start, and Secondary Address Range End parameters.

  3. If your clients want to receive domain information from the BOOTP server, specify the Domain Name Server Address and Domain Name parameters when you specify IP parameters.

    NOTE:  The DHCPD NetWare Loadable ModuleTM (NLMTM) file can be used only for remote node clients. It cannot be used for LAN clients. You must set up a separate DHCP server for LAN clients.

To configure IP addresses for PPPRNS, complete the following steps:

  1. Select Configure Services from the Remote Access Options window.

    The Remote Access Services window is displayed.

  2. Select PPPRNS.

    The PPPRNS Configuration Options window is displayed.

  3. Select Set IP Parameters.

    A list of users and containers in the default Directory context is displayed.

    Select the single period (.) to set IP information for the current container. If users are distributed over multiple contexts, select the double period (..) to move up the Directory tree to a common branch. Select names with a plus (+) prefix to move down the tree.

    If the CONNECT object does not have Browse rights to move up the Directory tree, press Ins and enter the new Directory context. This enables you to jump to another branch of the tree where the CONNECT object does have rights.

  4. Select a user or container.

    The User IP Parameters window is displayed. You can set the remote access parameters if the CONNECT object, in addition to having Browse and Read attribute rights, has Write attribute rights to that container.

  5. Select Set Domain Information and specify Yes.

    The domain information can be specified when the remote access server is set up as the BOOTP server for remote clients and the clients want to receive this information.

    NOTE:  The following parameters are available to clients only if the remote access server is a BOOTP server and the clients request the information using BOOTP. If the remote access server is not set up as a BOOTP server (refer to Support for Remote Nodes) or the clients do not use BOOTP to request information, these parameters are not used.

  6. Specify the following domain parameters:

    • Domain Name Server Address---Enter the address of the domain name server to resolve hostnames for client requests.
    • Domain Name---Enter the suffix to append to local hostnames. For example, if the domain name is novell.com, the client appends this name to ca (the local hostname) to provide the complete name of ca.novell.com.

    NOTE:  You can specify the Domain Name Server Address without specifying the Domain Name if the client uses complete hostnames. Specifying the Domain Name without the server address is not useful.

  7. Select Set Boot Parameters and specify Yes.

    The Boot parameters enable a diskless client machine to transfer a boot file to the client's memory and execute the boot file to start the client.

  8. Specify the following boot parameters:

    • TFTP Server Address---Specify the IP address of the TFTP server for this user or container.
    • Boot File Name---Specify the name or pathname of the boot file that the client uses to start the remote workstation.

    You are not required to set these parameters if the client does not need this information. For example, the client usually does not require a boot filename. Few client workstations must transfer a boot file from a remote site in order to start workstation operation (boot up). Most PCs have their boot files in local memory.

    NOTE:  When the BOOTP service is used, the client dialer application must be configured to use BOOTP for address assignment. Refer to the Novell Internet Access Server 4.1 remote access online help for information about setting up the client application network parameters.

  9. Press Esc twice to save your changes.

    The changes take effect when you have saved them.


Specifying ISDN Short-Hold Parameters

Specifying short-hold parameters for a PPP ISDN connection enables a remote node client to disconnect the line temporarily when no traffic is on the line and to reconnect when required. This minimizes telephone charges by reducing the actual connection time. Note that when the line is temporarily disconnected, the line is dropped but the session remains. The line is reconnected when either side has data to send.

If you have configured the short-hold parameters, the remote node client can determine whether to activate the feature when establishing the link.

NOTE:  Although ISDN short-hold is most useful for connections for which call setup time is relatively short, it can be used for any PPP connection, including telephone dial-up lines.

To specify ISDN short-hold parameters, complete the following steps:

  1. Select Configure Services from the Remote Access Options window.

    The Remote Access Services window is displayed.

  2. Select PPPRNS.

    The PPPRNS Configuration Options window is displayed.

  3. Select Configure ISDN Short-Hold Parameters.

    The ISDN Short-Hold Configuration window is displayed.

  4. Select Idle Time Before Temporary Disconnect and enter a value.

    This specifies the amount of time, in hours, minutes, and seconds, of link inactivity before the link is temporarily disconnected. The default is 5 minutes. The range is 1 second through 23 hours, 59 minutes, and 59 seconds.

  5. Select Maximum Call Suspension Time and enter a value.

    This specifies the maximum amount of time, in hours and minutes, that the connection can be left suspended before it is permanently disconnected. The actual amount of time the call is left in a suspended state is negotiated with the remote client when the connection is established. The two sides negotiate for the smallest value proposed by each. The default is 30 minutes. The range is 1 minute through 23 hours and 59 minutes.

    NOTE:  If the remote client is configured and has negotiated short-hold with the server, both the Idle Time Before Temporary Disconnect and Maximum Call Suspension timers are used. The other timers associated with the connection, Maximum Connect Time and Idle Time Before Disconnect (each configured on a global or individual user basis), are ignored.

    If the remote client does not negotiate short-hold with the server, both the Idle Time Before Temporary Disconnect and Maximum Call Suspension timers are ignored. The other timers associated with the connection, Maximum Connect Time and Idle Time Before Disconnect, are used.

    Currently, only the Novell mobile client supports short-hold.

  6. Press Esc to save your changes.


Specifying PPP Multilink

PPP multilink enables you to group multiple physical links into one logical link. With PPP multilink, you can group two physical ISDN channels or modems into one logical link to increase bandwidth. This feature allows you to use multiple channels between a remote access server and a client to increase the bandwidth for a logical connection.

NOTE:  PPP multilink is automatically enabled for remote access. Additional links are initiated by the remote client. Check your hardware documentation to determine whether your ISDN device supports PPP multilink.

To specify PPP multilink, complete the following steps:

  1. Select Configure Services from the Remote Access Options window.

    The Remote Access Services window is displayed.

  2. Select PPPRNS.

    The PPPRNS Configuration Options window is displayed.

  3. Select Configure PPP Multilink.

  4. Press Enter to toggle between Enabled and Disabled.



  Previous Page: Remote Access Services  Next Page: Configuring ARAS