Make sure tftpd and nbd are running with IPv4, /etc/default/tftpd-hpa TFTP_ADDRESS="0.0.0.0:69", sysctl net.ipv6.conf.eno1.disable_ipv6=1 and restarting nbd-server might help.
New install on Ubuntu LTS on plompy (applies to 11.04, 12.04, 14.04)
To create a basic load balancing, there is this documentation http://ubuntuforums.org/showthread.php?t=935416
...
...
@@ -28,9 +28,9 @@ Watch out for this one, you might be affected too: http://ubuntuforums.org/showt
Regular workstation installation. Install `ltsp-server`, `ldm-server` and `ltspfs`. On the DHCP server:
```
# -----------------------
# LTSP Server plompy
# -----------------------
# -----------
# LTSP Server
# -----------
group {
next-server 192.33.99.213;
filename "/ltsp/i386/pxelinux.0";
...
...
@@ -106,13 +106,8 @@ Now run dphys-config and create the NBD boot image: `ltsp-update-image -a i386`
Old install on etch/lenny
-------------------------
* [[attic/how to create LTSP boot images]]
* [[http://wiki.debian.org/LTSP/Howto]]
### Fix 'not authorized' problem after plimpy reboot
After rebooting plimpy, the ssh keys get regenerated which results in a 'this workstation is not authorized' error message on the thin clients and their inability to log into plimpy. To correct this, open `/opt/ltsp/i386/etc/ssh/ssh_known_hosts`, duplicate the two lines starting with 'plimpy' and modify the copied lines to read 'plimpy.ethz.ch'. After a reboot, the thin clients can log in again. Details: https://bugs.launchpad.net/ubuntu/+source/ldm/+bug/837924
* Double click the newly saved session **login.phys.ethz.ch** in the **Saved Session List** and enter your D-PHYS password. You should now reach a command prompt on the linux server**plimpy** or **plompy**. Minimize the SSH session window but do not close it, we only need it to stay in the background.
* Double click the newly saved session **login.phys.ethz.ch** in the **Saved Session List** and enter your D-PHYS password. You should now reach a command prompt on the linux server. Minimize the SSH session window but do not close it, we only need it to stay in the background.
* Start the **Remote Desktop Connection Client** from your Start Menu (enter _Remote Desktop_ to the search field of your Start Menu and click on the Search result **Remote Desktop Connection**). Enter **localhost:9000** to the field **Computer:**