kme

Riiight! Possibly conflicting drivers may result in a "No valid session"?! Sure you didn't come across a black cat the day before? Or broke a mirror? And I thought edugeek was for educated geeks... Of course you should never include more drivers than necessary - that's the entire point of a thin client - but this type of wild claims is unserious. Driver conflicts will NEVER result in a "No valid session". It can result in all sort of other problem, but not this. The LiveCD works just fine and it includes everything and the kitchen sink.

OK, but then you have to study your tftp server's log and Thinstation's /var/log/boot.log as you thinstation.conf.network obviously does contain a valid session and it equally obviously isn't received by the Thinstation client. And frankly it isn't very smart not to have a safe fall back in thinstation.conf.buildtime as you don't have.

The .txt file extension is invalid: thinstation.conf.network is proper

It's already shown in the sample configuration file: #CRON_JOB="00 20 * * * /bin/poweroff" Just remove the # and edit the time