Novell Documentation: Novell Internet Access Server 4.1

Ports and Modems

This section contains troubleshooting information for ports and modems and is divided into three categories:

Troubleshooting Tools

Load NIASCFG and select View Status for NIAS > Remote Access > Display Port Status, and then select the desired port and the following troubleshooting tools:

Display Port Statistics---Displays current port configuration settings and potential problem areas. Take note of the Port Statistics section. Software overrun errors, framing errors, or parity errors could indicate phone line problems or PBX configuration problems. If the number of bytes received progressively increments and the number of bytes transmitted remains constant, then modem script incompatibilities or PPPRNS configuration errors might exist. Make sure that the modem type connected to the port matches the modem type configured for that port.

Check the PPPRNS configuration and verify that the Internetwork Packet Exchange^TM (IPX^TM) address is unique across the WAN, including network segment addresses and internal IPX addresses.

Start Trace on Port---Captures traffic sent to and received from the port.

Terminal Mode---Verifies operation of the modem or device connected to the modem by using this operation to send data to and receive data from the AIO port.

Identify Port---Identifies the physical port referenced by a port name by toggling the Data Terminal Ready (DTR) on the port.

Use NWCRPAIR to repair the remote access database after a server abends.

You can view server configurations by loading NIASCFG and selecting Configure NIAS > Remote Access > Generate Configuration Report.

Configuration Tips

This section lists configuration tips that are useful for server configuration.

Inbound Port Service

Novell Internet Access Server 4.1 provides Remote Control Services---the ability of a remote workstation to dial in to the remote access modem pool and take control of a host on the LAN---through the Inbound Port Service. Use NIASCFG to configure this service (parameter path: Select Configure NIAS > Remote Access > Configure Services > NCS). The second line, General Name for Shared Dial-In Ports, displays DIALIN. This remote access service creates a modem pool used for dial-in connections. From a workstation running Win2NCS, select Options > Map Communication Ports. When you select Unique Name or Specific Name, the service name listed is a combination of the first eight characters of the Novell Internet Access Server 4.1 server name and the word DIALIN. For example, if the server name is RemoteAccess, the service name is REMOTEACDIALIN. A local workstation would not use this service for dial-out services.

You can view sessions on dial-in connections using NIASCFG (parameter path: Select View Status for NIAS > Remote Access > Display Service Status > tab to NCS > press F10).

Outbound Port Groups

For dialing out, use only the ports listed in NIASCFG in Dial-Out mode and in Both Dial-In and Dial-Out Port Usage (parameter path: Select Configure NIAS > Remote Access > Set Up...> Define Remote Access Port Usage). You can select outbound ports by group name or individual name. If you select a port by group name, the remote access software will select an available port within the port group.

Home Server

If you have configured a Home Server for a PPPRNS user or container, ensure that the specified Home Server is running IPXRTR.NLM and is reachable by the remote access server.

Configuring IP

In NIASCFG, select Configure NIAS > Remote Access > Set Up... > Select Remote Access Services. Select PPPRNS and press Enter. Select IP. Enter a valid IP address. This address serves as the IP address for the virtual interface that is set up by remote access. This address must be on a separate network (subnet) from the LAN. TCPIP.NLM version 3.01 or later must be loaded with IP forwarding enabled. This version allows the option of variable subnetting and stub-subnetting. It also contains code that distributes IP addresses to dial-in clients. The remote access server allows for the configuration of a client address range. If addresses will be assigned from the server, enter the addresses at this point. If addressees will not be assigned, ensure that clients are entering IP addresses that belong to the unique PPPRNS subnet into their dialers.

ISDN

If you are using ISDN Synchronous Bus Adapters for remote access, make sure that you configure the ISDN interfaces using the NIASCFG Remote Access configuration menu. If you configure the ISDN interfaces using the NIASCFG Protocols and Routing menu, the interface functions only for routing.

If the server is using only ISDN, reduce the dialback parameter in NIASCFG so that the dialback takes place sooner (parameter path: Select configure NIAS > Remote Access > Configure Security > Set Global Parameters). The default dialback timer values are for analog modems. Values of 1 or 2 seconds are more appropriate for ISDN.

If the server is supporting both ISDN and analog modems, try using a value that is lower than the default. Make sure both analog and ISDN users are successfully called back. For example, try a value of 10 or 15 seconds. The limiting factors are how quickly the server's modem can hang up and reinitialize an outgoing call and how quickly the clients can hang up and reinitialize to listen for incoming calls.

ISDN Terminal Adapter

If you are using ISDN Terminal Adapters (TA) for remote access, make sure you use the configuration program provided by the manufacturer to configure the TA with the necessary information as specified by your ISDN provider. For example, the ISDN provider might require following settings, the Service Profile Identifier D-channel Protocol, (SPID) and Terminal Endpoint Identifier (TEI).

Port Modem Type

If a port name appears in the port configuration list but is not displayed in the port status listing, verify that the port modem type is not set to Unknown. Ensure that the port is configured for remote access use by selecting Configure NIAS > Remote Access > Set Up... > Select Remote Access Ports. If the port in question is not listed, press Ins, highlight the correct port modem type in the list, and press Enter. If you have ports to which no modems are connected (direct connect ports), you must select Modem Type None for each port.

Common Problems

This section discusses various symptoms of common problems related to ports and modems and the potential solutions.

The port does not initialize.

Before a port can receive a call, the port must be in the WAITING state. Use NIASCFG (parameter path: Select View Status for NIAS > Remote Access > Display Port Status) to examine the port status. If the state of your port is any of the following, it is not capable of receiving any incoming calls for the remote access server.

IDLE---Indicates that either the port is a dial-out-only port or that no remote access service (PPPRNS, ARAS, or NCS) is running that is configured to use this port for a dial-in connection. Determine whether the services you configured are running. Check the Restrict Service by Port configuration to verify that the service is allowed to use the port. If you modify the configuration so that this port is now used for a dial-in connection by a running service, the port status should change from IDLE to INITIALIZING to WAITING.

WAITING---Indicates that you have configured remote access for Dial-In only or Dial-In and Dial-Out. If, after a successful dial has been completed, the port status changes to DISCONNECTED and remains there, try resetting the port to see if the status returns to WAITING.

START UP---Indicates that the Service Selector is not running. Run NWCSTART.NCF from the server console prompt.

BROKEN---Indicates that remote access has failed to initialize the modem attached to this port. This can be caused by a defective modem, a modem type mismatch in the configuration, or a cabling problem. Use NWCTERM.NLM to send characters to the modem so you can observe the modem's responses. A port status of BROKEN can also indicate that the AIO driver is not loaded.

UNAVAILABLE---Indicates that the AIO driver that is providing this port is not loaded or is not registering this port to AIO.

ACQUIREDOTHER---Indicates that the port is already acquired by other non-remote access server modules. For example, the port might have been acquired by a routing component. Use NIASCFG to verify the remote access port usage configuration and the usage of ports by other components of the system.

CONNECTING---Indicates that an incoming call has been received. The status changes from CONNECTING to CONNECTED as soon as the Service Selector determines to which service the call is destined. The call is then sent to the appropriate remote access server module. Use NIASCFG (parameter path: View Status for NIAS > Remote Access > Display Port Status) to view the call's destination.

You have added a new communications adapter to the server, but the ports on the adapter do not appear in the Port Configuration or Port Information window on the server console.

If you have multiple communications adapters in the server, ensure that they use I/O port addresses in the proper sequence. Refer to the adapter manufacturer's documentation for the proper sequence of I/O port addresses.

Also, complete the following checks:

Use NIASCFG (parameter path: Select Configure NIAS > Remote Access > Set Up... > Select Remote Access Ports) to verify that the ports are selected for use with remote access.

Ensure that the server's communications adapters are configured correctly and do not use I/O port addresses or memory addresses that conflict with other hardware.

Verify that the AIO.NLM driver and the correct drivers for the adapters are loaded.

Ensure that the LOAD parameters for the I/O drivers specified in the NETINFO.CFG file (in SYS: ETC\NETINFO.CFG) for each communications adapter match the switch setting on the adapters.

Ensure that you have the latest drivers for the adapter.

If the ports appear in the port configuration but not in the Display Port Status portion of the menus, use Config Port (parameter path: Select Configure NIAS > Remote Access > Configure Port) to verify that a modem type has been set for the port to a value other than Unknown.

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^TM board, 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.

Modem or communications adapter takes too long to initialize.

Ensure that you are using Novell-certified communications adapters and that the drivers are up-to-date. Contact the manufacturer for information about updated drivers. Also verify that the modem type is specified correctly and that the latest modem scripts are being used.

The remote access software uses all available AIO ports, causing other NLM files on the server to generate error messages.

You might need to dedicate ports for server applications that are not part of remote access. To reserve a port for another application, use the NIASCFG utility (parameter path: Select Configure NIAS > Remote Access > Set Up... > Select Remote Access Ports). Select the desired port and press Del.

You want to determine which port a modem is using.

To determine which port a modem is using, display the port status for the desired port (parameter path: Select View Status for NIAS > Remote Access > Display Port Status) and select the desired port. Use the Identify Port menu option to toggle the port's DTR signal. This causes the modem's TR or DTR light to blink.

Modem or port initialization problems occur.

If the port status for a modem is displayed as Broken, perform the following procedures:

Ensure that the modem type defined for the port matches the modem attached to the port. For information on certified modem scripts, refer to the WWW location http://support.novell.com. Choose the search feature and enter NWCMOD.EXE for access to scripts.

Verify cable connections. Use Terminal Mode in NIASCFG (parameter path: Select View Status for NIAS > Remote Access > Display Port Status > Select a Port > Terminal Mode) to verify that modem cable connections are functional. Use the modem ATI commands and try to establish a dial-out connection using the ATDT command. You might need to issue an ATE1 command to enable echoing back to the screen.

If you are using a communications adapter, try placing the modem on the server's COM port. If you are not using a communications adapter, try switching the modem to another COM port.

Try a different modem.

No users or only some users can access communications ports.

Use NIASCFG to generate a configuration report and verify that users have access to the ports (parameter path: Select Configure NIAS > Remote Access > Generate Configuration Report). Also, if the server is on a network that is connected to the workstation by a bridge or router, ensure that the bridge or router is operating correctly and that the user has access to the server. In addition, ensure that all hardware is installed correctly, including all add-on boards and cable connections. Consider resetting ports to reactivate them.

Verify that the container TEST has access to CONNECT object by completing the following steps:

Right click on container TEST.

Check TRUSTEES OF THIS OBJECT.

The CONNECT object should be displayed.

Select the CONNECT object to display the rights.

Correct the rights if required.

The port you are trying to dial in to in order to access PPPRNS shows a status of connecting; however, the incorrect service is displayed (ARAS).

Make sure that you are using the correct modem configured for that port, that the modem is compatible with the modem on the server, and that the speeds are the same. Sometimes the modem forwards the V.42bis negotiation to the remote access software, thereby making the software process this call as an ARAS call.