Client diskless boot failed
- Failure of booting from network
- The first booting item in the BIOS is not "boot from network".
- The electricity in the BIOS battery is not enough.
- The BIOS setup is in a mess, please reset up the BIOS.
- Because of the humid climate, the connection between the RAM and main board is not good. Please wipe the gold fingers in the RAM.
- The network cable is not well plugged.
- Sometimes the client does not boot, even after checking all possibilities in the server. This means the issue is with the network switch, you need to power cycle the switch (turn off/ on) once. After that clients will boot fine. If this happens frequently. We recommend replacing the switch with a better one.
- Client will fail to boot if the IP address of client PC is conflicted with another PC or device (WiFi Extender, router, or mobile devices). If this happens please change the IP of the devices and reboot the client.
2. Stops at DHCP
The client stops at DHCP when booting and the address of the server IP can't be obtained.
- Problem of the network: testing method, use one computer to PING server and use the server to PING the computer.
- Problem of the switch. Solution: check the main switch and the sub switch to see whether the power supply is normal.
- Problem of network cable. Solution: Check whether there is a problem for the client network cable and the server network cable and make sure they have been connected to a LAN.
- Problem of the firewall. Solution: Shutdown the firewall of the server.
- The CCBoot service stops. Solution: Click the "start" button in the main interface of CCBoot, start the CCBoot service.
- The server port needed by DHCP is blocked. Solution: open port 67 on the server.
- The client is not added to the user list of CCBoot and the server of CCBoot hasn’t enabled the "auto add client" option.
3. Stops at the TFTP
In the process of booting the client, DHCP can obtain the IP address of the server, but it stops at the location of "TFTP" and the error of TFTP occurs.
- CCBoot hasn’t started the TFTP service.
- The firewall of the server system does not open TFTP port, solution: to open port 69 in the firewall.
- Reset up TFTP.
Solution: On the "DHCP Setting" uncheck the "start TFTP" checkbox and click the "Ok" button, and again check the checkbox of the "start TFTP".
- On new motherboards, sometimes "gpxe.pxe" and "gpxex.pxe " will take much time to start windows booting. In this case you can use "ipxe.pxe" (Figure 1).
4. Stops at www.ccboot.com
- PXE's loading file problem. The default PXE file doesn’t support some special network card.
Solution: Change PXE file, the default "gpxe.pxe" to "gpxex.pxe" and click the "Ok" button (Figure 2).
Note: It would be better to use "gpxe.pxe", but if you cannot diskless boot the client using "gpxe.pxe", you can try to change the PXE value to "gpxe0.pxe". If this doesn't work, please modify the value to "gpxex.pxe". If Realtek 8111E NIC has blue screen problem, you can try to change the PXE value to "ipxe.pxe".
5. No more network devices/iSCSI boot 192.168.0.1::3260:: error occurs
When booting the client, the error of "iSCSI boot 192.168.0.1: 3260: No more network devices" occurs.
The reasons of error and the solution are as follows:
- Format writeback disk if you see "No more network devices" and "Not supported".
- The trial version of CCBoot only supports 5 users, if the number exceeds 5, it will stop at "iSCSI boot 192.168.0.1: 3260". Solution: Purchase the serial number and register.
- The registered number has been exceeded. Solution: Add license number.
- In the 32-bit operating system, the single process shall not exceed 1.6 G. When the CCBoot process reaches 1.6 G, the CCBoot server can no longer allocate memory and then error occurs. Solution: Change the server into the 64-bit operating system.
- The router has opened DHCP and it has disturbed the normal operation of the client. Solution: shut down the inbuilt DHCP of the router.
- In the LAN, other software has opened DHCP functions. Solution: temporarily shut this software and reboot it after the client is in normal startling.
- The disturbing of the DHCP for CCBoot. For example: in the same LAN, there are two CCBoot servers, two servers are prepared for the load balance (please check the "Multiple server load balance" chapters for more detail). If server A deletes the client PC 101 while the client PC101 is rebooting, it stops at the "No more network devices".
Solution: open the installation folder of server B, copy the "db.xml" file to the installation folder of server A and replace the file of the same name.
- If the "Disk Group" has not been assigned, please select a disk group.
- Maybe the BIOS battery has no power.
- The image has problems.
- The client of the CCBoot property doesn’t set the "Boot Server Address".
- Haven't set the correct writeback path in the CCBoot client properties.
6. Diagnostics by read size
1K - you use UEFI images when the bios is configured legacy.
Solution: Use legacy images with legacy boot type configured on the bios.
300-500K - You used wrong pxe for the client PC
Solution: Try other pxe
60-180M - Your image does not have the correct NIC driver for your motherboard.
Solution: Add NIC drivers from local.
200-700M - Your image does not have some critical drivers for your PC.
Solution: Enable super client and turn on PC then wait until PC restarts once, after that it will boot properly.
7. Blue screen when the client boots
Cause and solution are as follows:
- The physical RAM of the client has problems.
Solution: Change the client physical RAMS.
- The network driver has problems.
Solution: change other versions of network card driver.
- Software conflict (for example, billing software).
Solution: uninstall some software which can cause conflicts.
- The problem of images package.
Solution: Remade image package.
8. Automatic restart
Before the client boots to desktop and reboot automatically, the causes and solutions are as follows:
- When the client writes, the cache setting of the client is too big and the client starts automatically.
Solution: Adjust the size of client write cache.
- Problem of network card driver.
Solution: Change the versions of network card driver.