RE: [SLE] Suse Newbie
Robert, I'll try to answer the questions you posed and hopefully narrow down the possible cause of this issue.
Is this on a LAN? Is the machine you telnet to also on the LAN? All machines are connected together via a LAN (crossing over different subnets).
Does the target machine have a timeout for inactivity? As far as I know, none of the Unix machines (Solaris) have any type of timeout or time limitation for telnet connections.
Does the dis-connect occur at predictable time intervals (and what is the interval)? Were you doing something specific just before it dis-connects? I've tried timing these disconnects, but I haven't gotten any hard timings. Usually the disconnects happen after I've been doing some work on another machine and then go back to using the Suse box.
Where are you running 'telnet' from (console, GNOME Terminal, Eterm, Konsole, xterm)? I'm using KDE2 with Suse 7.3 running Konsole for telnet sessions.
Over the last couple of days, I've begun to think that maybe there is not a problem with Suse 7.3 per se, but a problem with the way I've got my hardware setup. For work, I use two machines (a Win2K box and a Suse 7.3 box) with a Sun monitor and Belkin Omni Cube KVM switch. I use the <Scroll Lock> key to toggle the monitor over from Win2K to Suse and I really notice the problem when I use the Win2k box for a long period of time. If I use Win2K for let's say 30 minutes, then toggle back to the Suse box, the monitor LED just blinks until I hit something like the <spacebar>. When I hit the <spacebar>, the monitor clicks and hums, then displays my KDE desktop. Do you think that this has any bearing on the problem? TIA, Matthew -----Original Message----- From: Robert Wohlfarth [mailto:rjwohlfar@galaxyinternet.net] Sent: Wednesday, April 24, 2002 11:27 PM To: 'suse-linux-e@suse.com' Subject: Re: [SLE] Suse Newbie On Tue, 2002-04-23 at 14:25, Simoncini, Matthew wrote:
Hello,
I recently installed Suse 7.3 Personal Edition on a test machine at work (interested in trying a different flavor of Linux) and found that my telnet sessions are dropping after a certain connection time has passed. The message I see is "Connection closed by foreign host". Does anyone know if there is a default setting somewhere in the installation that sets up this "feature" ... maybe firewall rules ??
That message usually indicates that the two machines have stopped talking to each other. Is this on a LAN? Is the machine you telnet to also on the LAN? Does the target machine have a timeout for inactivity? Does the dis-connect occur at predictable time intervals (and what is the interval)? Were you doing something specific just before it dis-connects? Where are you running 'telnet' from (console, GNOME Terminal, Eterm, Konsole, xterm)? Just a few random things to check, and try to narrow down the field of possibilities. -- Robert Wohlfarth rjwohlfar@galaxyinternet.net "Is not life more important than food, and the body more important than clothes?" -- Matthew 6:25b -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com
On Thu, 2002-04-25 at 11:15, Simoncini, Matthew wrote:
All machines are connected together via a LAN (crossing over different subnets). Okay, that eliminated anything having to with a modem, ISP time out, or other external factors.
Does the target machine have a timeout for inactivity? As far as I know, none of the Unix machines (Solaris) have any type of timeout or time limitation for telnet connections. Do they time out if you log on directly, and stop using them for a long time? It's not necessarily related to telnet, but to login. Keywords (if you're asking someone else) are "idle time" or "inactivity".
I've tried timing these disconnects, but I haven't gotten any hard timings. Usually the disconnects happen after I've been doing some work on another machine and then go back to using the Suse box. Ok, that's a clue. It's probably not a timeout. Timeouts should be pretty consistent.
I'm using KDE2 with Suse 7.3 running Konsole for telnet sessions. Then it's probably not an application problem.
Over the last couple of days, I've begun to think that maybe there is not a problem with Suse 7.3 per se, but a problem with the way I've got my hardware setup. For work, I use two machines (a Win2K box and a Suse 7.3 box) with a Sun monitor and Belkin Omni Cube KVM switch. I use the <Scroll Lock> key to toggle the monitor over from Win2K to Suse and I really notice the problem when I use the Win2k box for a long period of time. If I use Win2K for let's say 30 minutes, then toggle back to the Suse box, the monitor LED just blinks until I hit something like the <spacebar>. When I hit the <spacebar>, the monitor clicks and hums, then displays my KDE desktop. Do you think that this has any bearing on the problem? Is it possible the Linux machine is powering down? Do you have energy saving features turned on? So it goes into a low power state and turns off the network card. I'm kind of guessing here. A more formal experimentwould be: 1) Telnet from Linux. 2) Use Windows for 45 minutes. 3) Jump back to Linux. 4) Check the telnet session - it should be disconnected.
If you can do that twice in a row, with the same result, then it's probably the culprit. -- Robert Wohlfarth rjwohlfar@galaxyinternet.net "Is not life more important than food, and the body more important than clothes?" -- Matthew 6:25b
participants (2)
-
Robert Wohlfarth
-
Simoncini, Matthew