|
This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. -- [ Picked text/plain from multipart/alternative ] John, That's my understanding as well. My first question was: was I right that the problem is suppressed stay alive traffic. And it appears so from early observations. My dev box has a dozen programmers and half dozen QA people on it so I can observe and manage the ramifications in the short term. My second, and dependent question, was: if so what's the better value for the time out. I'll probably back it up to a day or two, 1200 seconds is too short for me. I'm willing to let the system clean up the abend jobs, but first I've got to get it to stop cleaning up perfectly good jobs because the home router isn't cooperating. The person who pointed to the QTVDEVICE jobs appears to have been spot on: >Device WESTDORPA1 associated with client 10.60.40.103 port 2173 has been recovered. >Device WESTDORPA1 associated with client 10.60.40.103 port 2519 has been recovered. Both of these happened after the CHGTELNA and IPL and were caused by an action on my part with my laptop (one was docking while active, the other the WAP went nuts and I lost all internet connectivity with the laptop). Meanwhile WESTDORPB1 from my home desktop ran without trouble, even after a cold restart of the WAP the desktop session responded without a hitch. Ending WESTDORPA1 sessions, docking, undocking, whatever, worked fine. At any rate, the problem here seems to only occur with home routers (all WAP's in our case); those who VPN in from a single home PC have no complaints, and there's no known problem with workplace ethernet jobs. Problem here occurred on the wireless clients and the wired clients attached to various brand WAP's. My Belkin WAP doesn't allow any control by ports, but it has MAC filtering, strong WEP, NAT, DHCP, and is pretty fast with my Orinoco Gold card. I think I can live with even a 0 TIMMRKTIMO, but not a pc in the DMZ. The range of 0-2147483647 seconds does allow for quite a bit of leeway though. :-) Tom Westdorp Station Casinos -----Original Message----- From: John Taylor [mailto:jtaylor@rpg2java.com] Sent: Wednesday, July 24, 2002 10:25 AM To: midrange-l@midrange.com Subject: Re: Telnet sessions disconnecting -- Any Solution yet? Tom, This effectively sets the telnet server to never time out, so your telnet jobs won't get cleaned up after an abnormal end. It might make more sense to try a high --though still reasonable-- value, like 1200 seconds. John Taylor ----- Original Message ----- From: "Westdorp, Tom" <Tom.Westdorp@StationCasinos.com> > I changed a telnet attribute on my development system, and saw no dropped > sessions on my laptop or home desktop, both behind my Belkin WAP. I set > TIMMRKTIMO to 0, and it seems to have solved the problem for me. I did have > ops IPL the system as I saw no effect on just the change, but the change and > the IPL had me on line for 8+ hours (with nothing going on, just the strpdm > menu screen, when I used to get dropped every 15 minutes or so. So far no > negative repercussions. >
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.