Werner,
For those clients in the 192.168.2.x subnet, you'll need to set:
SERVER = <ipaddr_of_server>
in your lts.conf file. Make sure the 'ipaddr_of_server' is the address
from the 192.168.2.x subnet.
It already defaults to 192.168.0.254, but your clients in the other
subnet probably can't get to that address.
Jim McQuillan
[EMAIL PROTECTED]
Werner Winter wrote:
Hello,
I'm running a ltsp-server 3.0 and two nets: 192.168.0.0 and 192.168.2.0
The terminals from the 0.0-net are booting without any problem. When I
try to start the terminals from the 2.0-net they boot but stop on the
grey screen with the X. In /var/log/messages I get:
tserver kdm: server open failed for pc34.our.domain....
Does anyone have an idea about the problem?
--Werner
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting
language
that extends applications into web and mobile media. Attend the live
webcast
and join the prime developer group breaking into this new coding
territory!
http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
