Previous Page: Ports and Modems  Next Page: AIOPPTP Problems

Remote Access Server Configuration Problems

This section discusses various symptoms of common problems related to the server configuration and the potential solutions.


AppleTalk zones do not appear on the network.

Ensure that the network range you specify when you bind AppleTalk to ARAS is unique for each server on the LAN. The network range is specified when you load ARAS using NIASCFG. Keep in mind that each group of ports on the server running ARAS is considered to be a network.


Data transfer errors or a PC lockup occurs.

Interrupt settings for LAN boards or other devices conflict with PC COM port settings, causing data transfer errors or a PC lockup.

By default, many LAN boards, such as the NE2000, use interrupt level 3. This conflicts with the default interrupt used by the second communications port, COM2. PC COM ports use interrupt level 3 or 4.

If you do not require more than one COM port, remove or disable the second COM port. If the second port is on an add-in board, remove the add-in board or change the jumpers on the board to disable the COM port. If you need to use the second COM port, change the LAN board to use an available interrupt level.


More than one server is running Novell Internet Access Server 4.1, and one server does not show up on the network.

Ensure that all server names and IPX network addresses are unique and have not been assigned to other servers. Use NLIST to display the names of the servers on which Novell Internet Access Server 4.1 is running. Use IPXPING to verify if the server is reachable.


A remote access server halts unexpectedly.

If you have loaded the AIOCOMX driver, ensure that the interrupt specified by the int= parameter does not conflict with interrupts used by other hardware devices in the PC. If you do not specify an interrupt when AIOCOMX is loaded, the driver assigns default interrupts to the COM ports as follows:

If you are using COM2 and COM2 is assigned IRQ3, ensure that your LAN adapter is not set to use IRQ3. Note that NE2000 uses a default IRQ3 setting.


You have restarted a server after loading the remote access software, and the server cannot find the license data, the server has corrupted the audit trail database, or the Remote Access Supervisor (NWCSU.NLM) reports problems logging in to the network.

Unload NIASCFG by exiting the utility. Enter NWCSTOP and verify that all NLM files were unloaded successfully. Unload all AIO drivers, including AIO.NLM. Enter NWCRPAIR at the system console prompt. Two unrecoverable errors, Butil-610-18 and Butil-610-9, might occur during the access of the sequential file. These errors are normal. If any other unrecoverable errors appear, corruption in the Btrieve Database has occurred.

Rename or delete the NWC*.BTR files in the system directory. If a backup copy of these files is available, restore the files.

If you do not have a backup copy from which to restore the NWC*.BTR configuration files, you must start from a blank configuration. To start from a blank configuration, complete the following steps:

  1. Delete NWC*.BTR from SYS: SYSTEM.

  2. Load SVCDEF SYS:\SYSTEM\CONNECT\SVCS.DEF at the system console prompt.

  3. Enter port configuration and access control configuration information from the configuration report.

  4. Restart the server and restart Novell Internet Access Server 4.1.


When you start the remote access software, error messages appear that indicate your server has insufficient memory.

The server might be using only the first 16 MB of memory. Use the MEMORY command at the NetWare console prompt to verify the amount of available memory. If the amount of displayed memory is less memory than you actually have, enter the REGISTER MEMORY command to make the additional memory available. Novell Internet Access Server 4.1 requires a minimum of 32 MB of RAM.



  Previous Page: Ports and Modems  Next Page: AIOPPTP Problems