Hi,
Thanks for writing . . .

Originally Posted by
Emblem Parade
(Why 3? It is a bitwise OR of both options 1 and 2, which we both want enabled.)
. . . which gives peace-of-mind that 3 is not just some arbitrarily chosen number.
But thank you even more for writing . . .

Originally Posted by
Emblem Parade
On the client, you should be seeing the menu we defined in ltsp.conf ("Press F8 for boot menu", etc.)
. . . which brought to my attention that the ltsp.conf file should not end with . . .
Code:
# Better support for old or broken DHCP clients
dhcp-no-override
. . . but rather with . . .
Code:
# Better support for old or broken DHCP clients
dhcp-no-override
# Enable this for better debugging
#log-dhcp
#
# PXE
#
# Note the file paths are relative to our "tftp-root" and that ".0" will be appended
pxe-prompt="Press F8 for boot menu", 3
pxe-service=x86PC, "Boot from network", /ltsp/i386/pxelinux
pxe-service=x86PC, "Boot from local hard disk"
. . . damn near-invisible scroll bar! Or maybe I just have tunnel vision. But I digress.
So having put all of what you suggested for ltsp.conf into it and re-running service dnsmasq restart, I returned to the thin client machine.
Turned it on. It booted Windows 7. Turn it off and on again, all the while connected to router via ethernet cable, re-entered the BIOS setup, left all as it was (still set to boot from the network), exited from the BIOS set up and got this on the screen instead of Windows 7:
Code:
Intel UNDI, PXE 2.1 (build 082)
Copyright (C) 1997-2000 Intel Corporation
For Atheros PCIE Ethernet Controller v1.0.0.5(01/22/09)
CLIENT MAC ADDR: <thin_client_computer_ethernet_nic_mac_addr> GUID: <a_guid>
CLIENT IP: <thin_client_computer_ip_address> MASK: 255.255.255.0
DHCP IP: <router_lan_ip_address> PROXY IP: <terminal_server_computer_ip_address>
GATEWAY IP: <router_lan_ip_address>
Auto-select:
Boot from network
BOOT SERVER IP: <terminal_server_computer_ip_address>
!PXE entry point found (we hope) at 9CC4:0106 via plan A
UNDI code segment at 9CC4 len 2E9E
UNDI data segment at 9475 len 84F0
Getting cached packet 01 02 03
My IP address seems to be <thin_client_computer_ip_address>
ip=<thin_client_computer_ip_address>:<terminal_server_computer_ip_address>:<router_lan_ip_address>:255.255.255.0
BOOTIF=<a_hypen_separated_number>
SYSUUID=<the_same_guid_as_above_but_with_lower_case_letters>
TFTP prefix: /ltsp/i386
Trying to load: pxelinux.cfg/default ok
Decompressing Linux... Parsing ELF... No relocation needed... done.
Booting the kernel.
Loading, please wait...
then all that disappeared and was replaced with
Code:
connect: Connection refused
read: Connection refused
read: Connection refused
read: Connection refused
read: Connection refused
ad nauseum, until
Code:
NFS over TCP not available from <router_lan_ip_address>
connect: Connection refused
Googled that and have, therefore, started to think that it is related to something that showed up when I ran
sudo apt-get install ltsp-server dnsmasq
specifically this big ** WARNING **:
Code:
Unpacking ltsp-server (5.5.0-1) ...
Processing triggers for man-db (2.6.6-1) ...
Setting up nbd-server (1:3.7-1) ...
Creating config file /etc/nbd-server/config with new version
** (process:14414): WARNING **: Could not parse config file: The config file does not specify any exports
** Message: No configured exports; quitting.
nbd-server.
Setting up nfs-kernel-server (1:1.2.8-6) ...
Creating config file /etc/exports with new version
Creating config file /etc/default/nfs-kernel-server with new version
[warn] Not starting NFS kernel daemon: no exports. ... (warning).
Setting up squashfs-tools (1:4.2+20130409-2) ...
Setting up ltsp-server (5.5.0-1) ...
I was reminded of the above when, guessing, I ran
/etc/init.d/nfs-kernel-server restart
and got in response:
Code:
[ ok ] Stopping NFS kernel daemon: mountd nfsd.
[ ok ] Unexporting directories for NFS kernel daemon....
[warn] Not starting NFS kernel daemon: no exports. ... (warning).
I mention all this on the chance that it might be immediately obvious to you what the problem is.