![]() |
This section contains Mac2NCS software troubleshooting information that is divided into three categories:
If a problem that is general in nature occurs, the procedure described in Troubleshooting Checkpoints will help you isolate and resolve the problem. If a problem with a specific symptom occurs, refer to Common Problems.
Additional troubleshooting information is provided in the Mac2NCS README file.
We recommend the following guidelines for troubleshooting Mac2NCS connections:
To isolate and resolve Mac2NCS connection problems, complete the following tasks:
This section discusses various symptoms of common problems related to Mac2NCS connections and the potential solutions.
There is a conflict between the Mac2NCS drivers and the drivers in your system. To use Mac2NCS, you must identify and remove the conflicting drivers. First, identify a basic set of drivers that allow Mac2NCS to function without the Type 1 error. All system drivers are located within the Extension or Control Panel folders of the System Folder. Move all nonessential Extension folder and Control Panel objects to different folders (Unused Extension and Unused Control Panel, for example). Restart your Macintosh system.
After you have established a basic set of functioning drivers, you can identify the conflicting driver by moving the unused objects back to their original folders until the Type 1 error reoccurs.
Ensure that all modules are installed correctly and that the desired servers are accessible to your Macintosh. Open the remote access Mac Client folder (or diskette), open the Mac2NCS folder, drag the IPXNetStat application into the System Folder, and answer yes to the prompt. This adds IPXNetStat to the Apple menu. From the Apple menu, select IPXNetStat and enter 394 in the Query type field. A report of all the Novell Internet Access Server 4.1 servers accessible to your Macintosh appears. If IPXNetStat does not function properly, check the physical connection to the LAN and reinstall Mac2NCS.
If the desired server is accessible, reinstall Mac2NCS by clicking the Installer icon within the remote access Mac Client folder (diskette).
Verify port access by first clicking SetUp in the Mac2NCS Chooser. In the remote access Login window, enter your password and click Continue. The remote access Port Selection window appears. Ensure that the desired remote access port can be selected. Also, ensure that there are no other configuration errors. Exit the Chooser and try the modem application again. If the message appears, contact your system administrator.
Verify that the Redirect to LAN buttons in the Mac2NCS Chooser are set to On. Also, ensure that the serial port selected by the modem application matches the serial port selected by the Mac2NCS configuration.
From the Chooser menu, select Mac2NCS. In AppleTalk Zones, select a zone. Click Setup and enter the User ID, Context, and password of a valid Novell Directory ServicesTM (NDSTM) user. Click Options and then select Server, General Name, and Specific Name. Click OK to return to the Chooser main menu. If the only option that appears is Any Available, there is a communication problem between the server and the workstation. Use NIASCFG on the server to troubleshoot the server configuration (parameter path: Select Configure NIAS > Protocols and Routing > Protocols > AppleTalk).
If the application you are using is Mac2NCS aware, set Redirect to LAN to Off in the Chooser. Within the application you are using, change Modem Port to Mac2NCS. If the application is not Mac2NCS aware, set Redirect to LAN to On. Within the application, change Mac2NCS to Modem Port.
Most AIO drivers on the server do not use a 1.5 stop bit setting. Instead, use a stop bit setting of 1 or 2.
Set the bps rate to the next highest rate. Supported bps rates above 9,600 are 19,200, 38,400, 57,600, and 115,200. For example, if you want to use a bps rate of 12,000, instead, use the next higher supported rate of 19,200.
Remove the AT-extended commands &Q0 and &M0 from the initialization script string. These commands instruct the modem to use Direct Asynchronous mode, which eliminates buffering and requires the line speed to match the port speed. Because remote access ports do not support 14,400 bps, a mismatch of port and line speed causes the connection attempts to fail. These problems do not occur on modems with 9,600-bps or lower ratings.
Restart your system. The serial driver was not closed properly by the last application using it.
This can be caused by mismatched modem types between the application and the remote access port. Ensure that the modem type used by the application matches the modem type configured for the remote access port. Also, ensure that the remote access port is not configured as a modem-independent port.
The remote access software initializes a Bocamodem 14,400-bps V.32 modem to use hardware flow control. If you do not want to use hardware flow control, send the modem the AT&K0 command to cancel the hardware flow control mechanism for the modem.
Make sure you have the latest version of the online service installed on your Macintosh.
Your preferred server is not responding to the SAP query generated by Mac2NCS. Contact your network administrator.
Sometimes an application simply does not support these rates, even though the selection is available on the application's user interface. Contact your network administrator.
The reason might be that the application does not support these rates, even though they appear on the application's user interface. Contact your network administrator. The solution is usually specific to a particular modem type.
One possible solution is to configure your online service software to use only a 9,600-bps or lower rate and then dial in to an online service that supports 9,600-bps or lower rates.
![]() |