Re: Telnet session is broken.

[John Jones <chianime@xxxxxxxxx>]

Rob's 'another option' is a good idea.

Have a server - VMWare, Citrix, Terminal Server, etc. - on the network.
That server should be able to retain stable connections to the AS/400.  The
VPN users connect to that machine instead of directly to the AS/400.  That
way, if their connection drops, they just re-establish the connection to
the VMWare (or other) server and the connection to the AS/400 itself should
survive.

If there's only one or two users with the problem, you might just use VNC
or Windows' Remote Desktop to access any machine on the network (an old
desktop PC for instance) instead of dedicating a server to the role.

On Thu, Aug 9, 2012 at 6:59 AM, <rob@xxxxxxxxx> wrote:

> For super critical stuff that I can't tolerate a comm session drop I will
> often use a shared console session from my HMC.  In that I could reboot my
> remote VPN machine, connect back in and it will be right where I left off.
>  The same will hold true for taking remote control with products like
> DameWare or PC Anywhere of a local PC.  I have two PC's here I often do
> this to.
>
> Another option which is becoming very popular here is VMWare View. Instead
> of a full blown PC or laptop for everyone they may have an iPad, or this
> 'terminal' into VMWare View.  We replaced Citrix with this.
>
> Our CEO doesn't even have his own company laptop anymore.  He uses his
> iPad.  Granted, he doesn't even have a sign on to our production i so 5250
> is not a real concern of his.
>
>
> Rob Berendt
> --
> IBM Certified System Administrator - IBM i 6.1
> Group Dekko
> Dept 1600
> Mail to:  2505 Dekko Drive
>           Garrett, IN 46738
> Ship to:  Dock 108
>           6928N 400E
>           Kendallville, IN 46755
> http://www.dekko.com
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.