On Friday 06 February 2004 12:26, Jeremy wrote: > > > > Well one approach could be to monitor all traffic with the > > remotely logged in host. For example on the server run: > > > > tcpdump -nX host <client_ip> -i <interface(eth0 for example)> > > Ok, I did that. There is -no- traffic when the disconnect happens, > or anytime before. After I logged in, the traffic stopped, after > 10 minutes, I went back, hit enter, and got kicked off. But alas, > it still did not generate any traffic in tcpdump. No traffic is what I'd expect if there was a broken socket connection. The client machine has no idea the socket is no longer valid until it tries to pump something into it and then, surprise, it discovers the broken connection and lets you know about it. > I tried the other fellow's idea of turning on the keepalive in > Putty. That helped, but not everyone connecting to my server has > PuTTY, my server is also a MUD hos, and people connecting with > other clients to their MUDs are getting kicked off every 10 minutes > of inactivity. You've definitely got something timing out and if it's your server at home then the internal clients at home should timeout as well. If they don't then you've got something between your server at home and the location you are now that's dropping out. Regards, Mike Klinke
