Remoteboot Client Won't Start

If a client won't boot remotely, or if you're having problems with the way the client is booting:

• Be sure that the server is running and that the Remoteboot service is running.
• The client must be on the same subnet as the server.
• Check Remoteboot Manager's list of adapters that have not yet been converted to workstation records. To update the list, choose Refresh from the View menu. If the client's adapter is on the list, convert the adapter record to a workstation record.
• Check the <systemroot>\Rpl\Fits directory. The server must have a .fit file for each profile that is to boot remotely.
• Each client must have an RPL ROM chip installed on or built into its network adapter. This ROM chip may need to be enabled via jumpers or a configuration program.
• Check the defaults for hardware settings in the <systemroot>\Rpl\Bblock\Netbeui\adapter\Protocol.ini file.
• If the client has a hard disk, the hard disk may need to be prepared for the Remoteboot service using the rplenabl utility.
• If the remoteboot server is a backup domain controller, wait until the account you've added has been replicated (or force synchronization to the primary domain controller using Server Manager).