That explanation does not cover all cases. There is also the "dropped VPN" problem, where DHCP lease has not changed, IP address has not changed, but VPN tunnel is dropped due to outside influences (timeouts due to volume at your ISP can cause this, I have been told). In these cases there is no reconnect possible in my experience.
Unless of course there is a way to reconnect in that case that I am ignorant of, which is entirely too possible. I would love to be more educated about this, if anyone can enlighten me. Peter -----Original Message----- From: Kinney, Kevin [mailto:[EMAIL PROTECTED] Sent: Friday, June 10, 2005 9:49 AM To: [email protected] Subject: Re: Kill a TSO session to Logon (Without 2nd Username) >> Logon reconnect doesn't usually work if you're connected with TCP/IP and >> TN3270. > That's just a bug that IBM can't be bothered fixing. I don't consider myself an IBM apologist, but with respect to Mr. Woren, I don't believe it's an IBM problem. This problem is simple to recreate, provided you're on a Win system and using an IP terminal emulator. <Snipped> Regards, Kevin Kinney _ This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
