The only other thing I can think of is your switch.
Is it a managed switch? Some switches will not allow a connection to be
active and idle for an extended period of time.
To test this, connect a single client to the LTSP server via crossover
cable and let it sit for a day, and see if it disconnects, too. If it
does not, then the problem is the switch, and you should figure out what
setting in the switch needs to be changed, or use a dumber switch. :)
-Gideon
On Tue, 2008-09-30 at 08:39 +0200, Wojtek Polcwiartek wrote:
> Hello,
>
> yes, we do have this line in /etc/hosts.allow
> We still work on this (wireshark etc.) :/
> Are other tcp-/udp-ports then 69 and 2000 needed?
> Any other ideas?
>
> Greetings,
>
> Wojtek
>
>
>
> Gideon Romm schrieb:
> > Do you have the following line in /etc/hosts.allow:
> >
> > nbdrootd: ALL: keepalive
> >
> > -Gadi
> >
> > On Fri, 2008-09-26 at 12:04 +0200, Wojtek Polcwiartek wrote:
> >> Hello,
> >>
> >> we try to implement LTSP in pc-pool (about 200 thin clients) for
> >> students at Tech.Univ. of Berlin (we are students too). The work is
> >> almost done. We are now in the test phase. Here we got an error, witch
> >> can stop our project :/ We use [EMAIL PROTECTED]
> >> Our problem: The connection between nbd-client and ndb-server breaks.
> >>
> >> The message at the clients says (After switching to another terminal):
> >> "nbd0: Attempted to send on closed socket"
> >>
> >> The logs at the server:
> >> - Connection
> >> ./syslog:Sep 24 16:43:14 lts02 nbdrootd[11882]: connect from
> >> 130.149.10.132 (130.149.10.132)
> >> ./syslog:Sep 24 16:43:14 lts02 nbd_server[11883]: connect from
> >> 130.149.10.132, assigned file is /opt/ltsp/images/i386.img
> >> ./syslog:Sep 24 16:43:14 lts02 nbd_server[11883]: Size of exported
> >> file/device is 228229120
> >> ./syslog:Sep 24 16:43:16 lts02 nbdrootd[11903]: connect from
> >> 130.149.10.131 (130.149.10.131)
> >> ./syslog:Sep 24 16:43:16 lts02 nbd_server[11904]: connect from
> >> 130.149.10.131, assigned file is /opt/ltsp/images/i386.img
> >> ./syslog:Sep 24 16:43:16 lts02 nbd_server[11904]: Size of exported
> >> file/device is 228229120
> >>
> >> - Connection lost
> >> Sep 24 17:56:08 lts02 nbd_server[11883]: Read failed: Connection reset
> >> by peer
> >> Sep 24 17:56:08 lts02 nbd_server[11904]: Read failed: Connection reset
> >> by peer
> >>
> >>
> >> Do You have any idea why could it happen?
> >>
> >> What tcp-ports are needed for well-working LTSP? We opened 69 (tftp) and
> >> 2000 (nbd-server). Our network infrastructure works good: we couldn't
> >> notice high-traffic time periods.
> >>
> >> Our H/W-Configuration:
> >> 2xServers (4x3GHz, 4GB Ram), H/W load balancer
> >> about 200x HP t5725, t5735 and t5525
> >>
> >>
> >> I already wrote an email about this error, but now I deliver some details.
> >>
> >>
> >> Thanks in advance!
> >>
> >>
>
>
--
--------------------------------------------------------
Gideon Romm | Proud LTSP Developer
[EMAIL PROTECTED]
Support LTSP! Buy your hardware at:
www.DisklessWorkstations.com
www.DisklessThinClients.com
(use coupon code: LTSP5P for 5% off thin clients from DisklessThinClients.com)
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_____________________________________________________________________
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
