drbl clients won't boot using 192.168.0.1 only 192.168.120.1 as static ip

What did you mean? Could you please describe more so that we can try to fix it? Like the version number, they way you setup DRBL server, and run "drbl-bug-report" then post the generated file.

Steven

I got the newest drbl live ISO 2.4.6-12 686-pae.iso

1. Put on USB stick.
2. boot DRBL in RAM (remove stick mode)
3. selected defaults
4. waited for destop
5. terminal window
6. sudo su
7. mount /dev/sda1 /home/partimag
8. Start drbl
9. static IP
10. remove hard code space and put 192.168.0.1
11. wait
12. back to terminal window
13. dcs
14. select all clients
15. start clonezilla
16. Expert
17. restore disk
18. advance parameters default
19. no checking image
20. use partation from image
21. no checking
22. skip
23. power off
24. select an image w237 (for me)
25. mulitcast/unicast same problem
26. go
27. Press Enter for no good reason
28. wait
29. leave server goto client
30. F12 wait

The directory /home/partimag/w237 does not exist
/etc/drbl/drbl-ocs.conf:
mount -t nfs 192.168.120.254:/home/partimag /home/partimag
/etc/ypserv.secure.nets has a similiar error.

Note: I set it up for 192.168.0.1 and now its on the 120 subnet for no reason

client waits at a command prompt for me to type something
** I manually type
mount -t nfs 192.168.100.254**:/home/partimag /home/partimag
sudo ocs-sr -l en_US.UTF-8 -g auto -e1 auto -e2 -r --clone-hidden-data -p power-off -scr restore-disk w237 sda

the process continues normally.

drbl-bug-report was run from the client

I meant to type sudo mount in the message above

here is bug report from server.

I followed your steps here, but I can not reproduce the issue here.
"Note: I set it up for 192.168.0.1 and now its on the 120 subnet for no reason" -> Are you sure there is no any other DHCP service connected to your network switch? It looks like there are 2nd one.

Steven