Troubleshooting: No Response from a RIS Server

  • Article

The following sequence occurs with most PXE ROM–enabled computers:

  1. When you start the client, you see the PXE boot ROM begin to load and initialize.

  2. The computer displays the message "BootP." This message indicates that the computer is broadcasting a request for service to the network.

  3. The computer displays the message "DHCP." This message indicates that the computer has received a DHCP response. This might be either the BINL response or the response from the DHCP server.

  4. The computer displays the message "BINL." This indicates that it also received a valid BINL response. Sometimes this happens quickly and you do not see it.

  5. The computer displays the message "TFTP" followed by a series of dots to indicate progress while it downloads Startrom.com.

  6. The computer displays the message "Press F12 for network service boot." This indicates a successful download of Startrom.com. Pressing F12 downloads the Client Installation Wizard, which then requests the Welcome.osc screen from the RIS server.

note-iconNote

Compaq computer systems provide the ability to press F12 during start up on PC98 or Net PC–based systems. In this case, the user is required to press F12 on the Compaq welcome screen, then press F12 again when prompted by the RIS server. RIS includes a "no F12" version of the first boot image, Startrom.n12. If all of your clients support the F12 key or some capability to request a network service boot through a welcome screen, you can replace the existing Startrom.com in the \Oschooser\i386 directory with the Startrom.n12 boot image. Rename Startrom.com to Startrom.old and then rename the Startrom.n12 boot image to Startrom.com. This allows you to use the F12 key on the client's welcome or "splash" screen to request the Client Installation Wizard and eliminate the need to press F12 a second time.

If the computer does not get past the "BootP" message, it is not receiving any information from the network. Check the following conditions:

  • Is the DHCP server available? Has the DHCP service been started on the server?

  • Have the DHCP and RIS servers been authorized in Active Directory? RIS and Windows 2000 DHCP servers must be authorized in Active Directory for their services to start.

  • Does the DHCP server have a defined IP address scope and is it activated? A DHCP server that does not have any scopes defined cannot service any clients.

  • Is there a router between the computer and the DHCP server that is not configured as a DHCP proxy? Verify DHCP packets are being forwarded through your router. Make sure that all routers between the client and the DHCP and RIS servers have been DHCP proxy–enabled. Also make sure that DHCP proxy tables contain both the DHCP and RIS servers. If the RIS server is located on the same network segment as the clients, no modifications are required to the router.

  • Are there any error messages in the event log under System Log for DHCP or BINLSVC?

  • Can other computers receive an IP address from DHCP on this network segment? Check computers already running an operating system to see if you can successfully renew their IP leases.

If the computer does not get past the "DHCP" message, the client might not be receiving a response from the RIS server. Check the following conditions:

  • Are the RIS and Windows 2000 DHCP servers authorized to run on the network? RIS and Windows 2000 DHCP servers must be authorized in Active Directory for their services to start.

  • Are other remote boot–enabled clients on the network able to download Startrom.com and see the "Press F12 for network service boot" prompt? If so, this computer might not be supported or is having problems related to PXE ROM. Most systems work with PXE ROM version .99c or later, however certain systems require version .99l. Check the version of the PXE ROM on the computer.

  • Is there a router between the computer and the RIS server that does not allow the DHCP-based requests or responses through? The RIS server communicates through the DHCP packets during the initial service request and response sequence. Blocking these packets does not allow the computer to contact the RIS server.

  • Are there any error messages in the event log under the System or Application logs specific to BINLSVC, TFTPD, DNS, or Active Directory services?

  • Make sure the Respond to client computer requesting service setting is checked in the properties of the RIS server. If this setting is not enabled, the server does not respond to any client requests.

  • If the Do not respond to unknown client computers setting in the properties of the RIS server is checked, the server only answers clients with computer account objects in Active Directory.

  • Run Verify Server . This checks to see if all of the necessary services are started and that the settings are correct. Anything it finds wrong it attempts to fix. It might prompt the user for settings that are missing or set incorrectly. It might also prompt the user for the source CD to install files that might have been accidentally erased.

  • Check the event log on the RIS server for any errors relating to DHCP, DNS, TFTPD, or BINLSVC.