We do it differently. Instead of a VPN, we use a Windows Terminal Services Gateway. We connect to that and it automatically connects us to our in-house desktop. We used to use a VPN, but it was replaced with the TSG server. I guess because the F5 VPN "wasn't Microsoft!". A common reason why we convert off of something.
On Mon, Aug 5, 2013 at 9:55 AM, Skip Robinson <[email protected]>wrote: > I think the answer is the same for OSA-ICC as for all other 'outside' > accesses to the mainframe: VPN. Let RSA do the heavy lifting. By the time > you reach the console, you have already been validated. You can also > access HMC in the same way. > > . > . > JO.Skip Robinson > Southern California Edison Company > Electric Dragon Team Paddler > SHARE MVS Program Co-Manager > 626-302-7535 Office > 323-715-0595 Mobile > [email protected] > > > > From: Joe Messineo <[email protected]> > To: [email protected], > Date: 08/05/2013 05:52 AM > Subject: Securing OSA-ICC Consoles > Sent by: IBM Mainframe Discussion List <[email protected]> > > > > We have been using OSA-ICC to emulate consoles for several years. This > has been done on a private network within the data center. We now have > the requirement to monitor the mainframe from a remote site. OSA-ICC > does not have an option to secure the Console traffic from the client to > the OSA card. > > Has anyone else out there faced this issue and how did you resolve? > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > -- As of next week, passwords will be entered in Morse code. Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
