Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Ok, I installed the LTSP Server Standalone package.
DHCP3 installed as dependecies as well.
My Client PC(laptop) is PXE booting into the Ubuntu Sign in screen, but when i enter the User ID and password, it says verifying password, then eventually the screen just clears and nothing happens.
Any suggestions on what I should do?
I tried installing the ltsp-client-core, but it tells me that is only for the Client pc. (not sure how I can install it on the client, when I'm trying to use the laptop as a diskless pc over the network (hence the whole LTSP logic).
Any help would be appreciated....
I'm having this same problem with LTSP 5.0 on Debian Lenny and now 10 thin clients are useless, as no-one can log in. It used to work perfectly with LTSP 4.2.
I have no dhcp.conf, as the company device manages DHCP, but the clients get their hostnames and boot fine to the login screen. The login manager is KDM and it's configured to allow remote access (as it does).
The users are created to the server as usual. lts.conf is in its default settings, since my old lts.conf from LTSP 4.2 doesn't work (black screen on clients).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.