Switch dumb terminals

Hi, we have approximately 15 dumb terminals at our office connected to an old ibm controller (3174 I believe) then to a cisco 1600 router and a dedicated 56k link which goes back to our client located in a different part of the city. We would like to replace these dumb terminals with pcs, have those pcs on our own internal network (to maximize their use) but still be able to access the clients mainframe (I guess we would have to use some terminal emulation software??). And I guess we'd have to make a connection from our internal lan to the router? What is the best way to do this with the least cost? Would we have to purchase only software and make configuration changes on both ends? What would the client have to do? Or would we have to purchase additional hardware? Thank you all.

Answer Wiki

Thanks. We'll let you know when a new response is added.

Get a linux box running and terminal emulation on the pc`s

Discuss This Question: 2  Replies

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • Howard2nd
    Networking, not a job, a WAY of life. A - Your are replacing 15 dumb terminals with PC's. Congratulations and hang on to your socks. B - Since this is a clean start, Zenith's suggestion is excellent. Linux operating system, maybe Sun's Java Desktop, or OpenOffice for productivity. It depends on where and how you acquire the PCs. Nearly all computers come with Windows and 'Works' or an equivalent office set. In either case, a terminal emulation program is easily acquired - we use Hummingbird Host Explorer. This is the software side of the puzzle. C - The hardware side is both easier and complicated at the same time. 15 teminals would imply a 16 port switch, and I would recommend a 24 port to allow room for growth or network printers etc. Then you have to have NIC's (Network Interface Cards) for each PC. And the fly in the ointment - cabling to each PC. If I remember correctly the terminals usually were connectd by thinnet (BNC on RG-58) or proprietary serial connections. In either case you want Level 5E or Level 6 Ethernet cabling installed to code specifications. There are more failed networks from cabling than any other reason. D - The Cisco 1600 will connect to the switch at the "WAN" port. Now all we have left is Addressing, subnets, gateways, and 'Do you want Internet access with that?' E - Before you start, set down with the people paying for this and get a written concensus of what they expect. Do they want e-mail, Internet browsing, file sharing, SECURITY, continuing support, and so forth. By now half the readers are LOL (laughing out loud) and the other half are wondering why I waited to this point to hit you with your Number 1 priority. I did not want to scare you off. Obviously I have probably caused more questions than I have answered. When you have developed a scope of project and 'Budget' come back to use and we can provide some specific solutions. Good luck.
    30 pointsBadges:
    Thanks for your reply. Howard2nd, you're right about the older connections, (BNC to RG). For these pcs to be on our network and still be able to connect to the clients' remote mainframe, wouldn't the wan port or csu/dscu remain the same and the new switch be connected to the ethernet port on the router? All the services you mentioned would be available from our internal network. The only thing I'm still unsure of is would we need any additional hardware to make it happen. I.e. if we install Terminal emulation software onto the pc like the hummingbird software, would that be all that is required given the proper configs are done on the mainframe, router, firewall, etc.? or would we need an intermediary device? Thanks again.
    0 pointsBadges:

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.


Share this item with your network: