Shmuel Metz (Seymour J.)([EMAIL PROTECTED])@Mon, Mar 27, 2006 at 12:02:10PM -0500: > In <[EMAIL PROTECTED]>, on 03/27/2006 > at 08:19 AM, Rich Smrcina <[EMAIL PROTECTED]> said: > > >Although technically correct that Putty can not do 3270, if the > >original poster can ssh into a Linux machine with the x3270 suite > >installed, they can use c3270 to access their 3270 based hosts. > > Sure, but they can do the same with any other protocol converter. > Putty itself doesn't buy them anything, and it's far more efficient to > simply use a TN3270 client in the first place. > > Again, Frank needs to find out what the real objective is. > Seems likely to me that one of the suits heard that ssh is secure, and that putty is a free implementation of it. I find it hard to believe that the thought process went much further.
I don't recall, was the intent to connect to TSO via ssh? One thing that I haven't heard mentioned that *may* help here, is using port forwarding. Putty (and most other ssh implementations) can do port forwarding. You could well use putty to set up a tunnel that connects an application on the host to a local port on the localhost. At that point you could fire up your 3270 client to connect to that local port. (Caveat: I haven't done this to connect to TSO before, myself.) This is a popular method for making secure connections with protocols that are usually insecure. For example, if you want to get your e-mail from a server that has IMAP or POP3 (w/o SSL), you can do something (assuming the server does have sshd running) like this: ssh -L2001:localhost:143 servername This command from the client will create an encrypted tunnelled connection. The mail-reader connects to localhost port 2001, which is then caught by the ssh client (putty). The encrypted data goes over the network to sshd on the server, where the data is unencrypted and sent to the IMAP server on port 143. So, applying the same logic to the TSO issue, I'd probably try to do something like: ssh -L2001:localhost:23 mainframe_dnsname (connects to the telnet port) OR ssh -L2001:localhost:22 mainframe_dnsname (tunnels directly to the ssh server, assuming TSO is directly accessible to ssh logins) My commands above are formulated for openssh, so translate them to putty dialog boxes before you use them. Hope that was helpful to someone. Wade Curry AT&T Services, Inc. Sr. Implementation Mgr My views and comments are my own. ---------------------------------------------------------------------- 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
