ccruss@deneb.ucdavis.edu (0059;0000000000;230;9999;98;) (10/27/88)
I have been requested to come up with solutions to connect some campus
IBM machines to our campus TCP/IP network. The models are a System 36,
an 4181 and a 9370. The System 36 and the 9370 are currently stand-alone
but would perfer to connect to an ethernet. The 4381 is on an IBM Token
Ring with a bunch of PCs, so the preference there is to do TCP/IP on the
token ring. I can connect the token ring to the campus network with a a
Proteon router, but can the 4381 talk TCP/IP on the token ring?
What has been done at other sites? I hear that IBM has solutions to
these problems, but I also hear the the solutions are messy and
expensive.
The location with the token ring would also like the PCs to use the
campus network. Has anyone written a IBM token ring adapter (real IBM)
driver for PD software like NCSA Telnet?
Thanks,
Russ
Russell Hobby
Data Communications Manager
U. C. Davis
Computing Services BITNET: RDHOBBY@UCDAVIS
Davis Ca 95616 UUCP: ...!ucbvax!ucdavis!rdhobby
(916) 752-0236 INTERNET: rdhobby@ucdavis.eduron@ron.rutgers.edu (Ron Natalie) (10/28/88)
The 4381 and the 9370 can both talk to the Token Ring with an 8232 which is not so hot, but it is what IBM has right now. The 8232 is a second generation of a DACU only this time rather than having something useful like a UNIBUS, it's an industrial channel attached IBM-PC. If you could deal with plugging the machines into Ethernet, BusTech makes a much cheaper and better performing channel attached Ethernet controller. The 9370 can also be attached to the network without the 8232 because there are integral lan interface cards available. The Series 3X (and the AS/400) are going to be more interesting. I don't think IBM has gotten that far in pushing TCP/IP. Mostly at the last SHARE IBM was tripping over themselves insisting that their support of TCP/IP and UNIX was not an indication that these would supplant SNA and SAA respectively. -Ron