To complete this thread for anyone that might be interested ...
This was indeed a system/hardware problem. The ethernet interface in my
server had flaked out and would not transmit more than 10 or 12 packets in
rapid succession, as typically occurs when TFTP'ing a kernel to a requesting
thin
I never tested SLES. There are two real differences between 'normal SuSE
ans SLES:
- SLES is supported with updates for many years, normal SuSE update
support ends after about two years
- SLES has some more options in YaST et al
I don't think, SLES is really better than SuSE. It differs in small
Hi,
I have installed LTSP 4.2 in a suse 9.3 box everithing worked great, the problem is that now I'm trying to do the same on suse 10 and I'm not able to run the client. I have checked my DHCP configuration and tested the tftp server, I have searched for information on google since two weeks
Sent: Saturday, August 26, 2006 10:32 AM
Subject: Re: [Ltsp-discuss] LTSP Suse 10 problem
I don't know if Jorge's problem is the same as mine, but it sounds like it,
and I've got details. :-)
I've got a SuSE 10.0 system that has been successfully serving two HP
t5505
thin clients for ages
-discuss] LTSP Suse 10 problem
I don't know if Jorge's problem is the same as mine, but it sounds like it,
and I've got details. :-)
I've got a SuSE 10.0 system that has been successfully serving two HP
t5505
thin clients for ages on LTSP-4.1 and LTSP-4.2. Last night I was working
Hi!
There are many steps in setting up LTSP.
If your problem is the dhcp server (Your client
doesn't get any IP's) then you should put the next
line at the begining of your dhcp
--- Jorge Lopez [EMAIL PROTECTED] wrote:
Hi,
I have installed LTSP 4.2 in a suse 9.3 box
everithing worked
Hi!
There are many steps in setting up LTSP.
If your problem is the dhcp server (Your client
doesn't get any IP's) then you should put the next
line at the begining of your dhcp.conf:
next-server 192.168.1.1;
You should change 192.168.1.1 for the IP of your
server
Good luck.
--- Jorge Lopez
