Troubleshooting Procedures

Configuration Builder generates a path error.

The working directory for Configuration Builder may be incorrect. Ensure that the working directory is c:\directory name\data.

The TCP/IP option is grayed-out in Learn and Send dialog boxes.

One of the following may be true:

• You have a TCP/IP transport that is not WINSOCK-compliant, Configuration Builder cannot use TCP/IP for learning or sending a configuration to the router. Configuration Builder only recognizes TCP/IP stacks that are WINSOCK compliant. If this is the case, you can only access the router through the serial ports.
  
  
• You may have a TCP/IP stack installed, but Configuration Builder cannot locate the files. Make sure you have specified the TCP/IP stack directory location in the PATH statement in your autoexec.bat file. The app2sock.dll file and the a2s4wsoc.dll file must be in the \windows\system directory.
  
  
• The app2sock.ini file must be in the \windows directory. In the app2sock.ini file, ensure that TRANSPORT=WINSOCK.
  
  
• The winsock.dll file can be located in either the TCP/IP or \windows\system directory. Ensure that you only have one copy of the winsock.dll file.
  
  

In Configuration Builder, a device cannot be connected through TCP/IP.

Connect to the router using the Telnet option of your TCP/IP software or the Telnet supplied with Configuration Builder. If this fails, there may be a problem on your network. Refer to the documentation for your TCP/IP stack.

Long delay (in Learn and Send dialog boxes) in connecting to the router.

Check for intermediate devices that may require input, such as a modem prompting for a password.

The connection times out, or there is a long delay on a serial connection.

Verify that you have the right console cable for your router. Also check the pinouts on your adapter.

Configuration Builder cannot communicate with the router if the router is in ROM monitor mode.

Exit ROM monitor mode by connecting to the router through the console port. Then enter b to load the operating system software.

If the configuration register on your router is set to boot to ROM monitor mode, check your router documentation to change the default boot mode.

Configuration Builder menus are missing.

Verify that the LISTINIT.INI and MENUNamE.DAT files are located in your installation directory.

Configuration Builder does not generate configuration commands or generates them in the wrong order.

Verify that the SYNTAX.INI, MAJOR.SYN, PROTOCOL.SYN, and FUNCTION.SYN files are located in your installation directory.

Configuration Builder hangs if it is running on a Pentium-based machine with a peripheral component interface (PCI) bus and a 16550 Universal Asynchronous Receiver Transmitter (UART) chip.

Ensure that the first-in, first-out (FIFO) queue on the COM port UART that you are using is turned off.

If you are running Microsoft Windows 3.1, do the following:

• Add the following statement to the [386Enh] section of the SYSTEM.INI file in the \wINDOWS directory:
  
  

  COMxFIFO=OFF

  In this example, x is the value of the COM port you are using (1, 2, 3, or 4).

If you are running MS Windows NT, do the following:

• Run REGEDT32.EXE from the MS Windows Program Manager.
  
  
• Navigate to the HKEY_Local_Machine window and search your way down the tree to System>CurrentControlSet>Services>Serial.
  
  
• Locate the section labeled ForceFifoEnable : REG_DWORD : 1.
  
  
• Double-click on the section, and in the displayed window, change the value to 0.
  
  
• Click OK.
  
  
• Reboot your PC.
  
  

If you are running MS Windows for Workgroups, do the following:

• Obtain the SERIAL.386 file from Microsoft. This file should be dated February 17, 1994, and should be 10,620 megabytes long.
  
  
• Replace the existing SERIAL.386 file in the WINDOWS\SYSTEM directory with the new SERIAL.386 file.
  
  
• Reboot your PC.