# Troubleshooting in LAN Server environments

- Use SMARTROM.EXE to ensure that your Smartrom is programmed with either MULTI.ROM or NRPL.ROM. If not then reprogram it using SMARTROM.EXE.

- Ensure that the server and remote boot services are running on the server.

- If the initial download of the boot block is failing it may be necessary to change field 5 of the RPL.MAP file from N to A. This slows down the boot process and guarantees that the server stays in touch with the workstation's progress as it downloads the boot block.

- If changes are made to the RPL setup run GETRPL to ensure that the changes are registered.

- The important files and directories (relative to the C:\IBMLAN directory) are:

  RPL\MACHINES\(machine_name):
  this directory contains the config.sys and protocol.ini file for the machine (machine_name).

  Ensure that you have referenced the Madge driver in the PROTOCOL.INI and CONFIG.SYS files. In addition be sure to make any changes to the CONFIG.SYS file which are required to support different kinds of video adapters and PC bus architectures.

  RPL\FITS\:
  for OS/2 remote booting this directory contains the fit file which defines the files to be included in the workstation's boot image.

  IBMLAN\RPLUSER\:
  contains user specific remote boot files.

- For OS/2 remote booting, if the full screen interface does not allow you to define a Madge workstation entry, ensure that you have not yet changed the bootblock file you have specified. You must define the Madge workstation first and only then edit the boot block file to make it refer to the Madge drivers.