Path: utzoo!utgpu!watserv1!watmath!att!ucbvax!NUSVM.BITNET!CCECL From: CCECL@NUSVM.BITNET ("L. Chandra") Newsgroups: comp.protocols.tcp-ip.ibmpc Subject: Re: Two TCP/IP stacks on one PC Message-ID: <9006040027.ac13862@louie.udel.edu> Date: 4 Jun 90 05:33:20 GMT References: Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 38 X-Unparsable-Date: Mon, 04 Jun 90 11:55:31 SST >For God sake, would somebody please say what's wrong with 3+Open TCP. Numerous >people have made comments about it being deficient, but nobody has >elaborated as to what's wrong. > >Sometime this summer, I have to bring a 120 node 3+Open network upto ULANA >compliance. (For those non-goverment people, ULANA is a goverment network >specification mandating TCP/IP) I would hate to make the $40,000 dollar >mistake. :-) > >Delbert Matlock Internet: dmatlock@eecs.cs.pdx.edu >MicroNet Northwest UUCP: dmatlock@eecs.UUCP >Voice: (503)228-3071 Some of the our problems with 3+Open TCP 1. For a start, 3+Open TCP does not have TN3270. This is a big problem for us since our main computing resource is IBM mainframe. Further more 3Com has not annouced any plan to support TN3270. 2. No support for Bootp/Rarp for dynamic IP address allocation. This is another big problem as we have many PCs without harddisk for student cluster. 3. Telnet client does not come with a ftp server. We are kind of use to (free) NCSA/Clarkson's version which has this feature. 4. For DOS, it comes with ONLY ftp, telnet and ping. (cf: PC/TCP provides ftp, telnet, ping, tn3270, tftp, ftp server, tftp server, rcp, rexec, rlogin, lpr, smtp, NFS ..... etc etc). 5. For OS/2, there is ZERO application (no ftp, no telnet, no nothing), just a bare TCP/IP protocol stack (what is that for? I wonder) 6. There is a socket driver but NO development kit (yet). So the socket interface is useless (for now). 7. No Netbios support (yet). ps: This is cross-posted to 3com-l and pcip.