___________________________________________________________________________ news@ftp The FTP Software Quarterly Newsletter ___________________________________________________________________________ Volume II, Number 1 May 1989 Open House Table of Contents To celebrate our move and to show Item Page our customers and affiliates our new offices, we will be having an Masthead 2 open house on June 1, 1989 from 2:00 to 7:00 PM. Everyone is New Product News 2 invited to stop by and see our new location and meet the members of Technical Support 3 our staff or catch up with old acquaintances. Internetworking News 6 We've moved! FTP Software moved from our old offices in Cambridge to new corpo- rate headquarters in Wakefield on February 25. Our new address for both shipping and correspondence is: FTP Software 26 Princess Street Wakefield, MA 01880-3004 Phone: (617) 246-0900 Fax: (617) 246-0901 Telex: 981970 We are now occupying all of the third floor and half of the second floor of an office building in downtown Wakefield (shown at right). This allows us the room we need to expand both our testing facilities and our staff. We've hired many new people dur- ing the past year to try to satisfy the needs of our customers and dis- tributors, and, as a result, we grew out of our old location. The staff that we've hired over the past year includes people in tech- nical support, documentation, sales and production. __________________________________________________________________________ 1 May 1989 May 1989 news@ftp ___________________________________________________________________________ PC/TCP(R) Plus and InterDrive Start news@ftp Shipping! Volume II, Number 1 We have just released InterDrive, May 1989 our newest product! InterDrive is our implementation of NFSTM for the Published by FTP Software, Inc. IBM(R) Personal Computer(R). We Editor: Nancy Connor. are very excited about the release, Communications pertaining to this because customers have asked for newsletter should be directed to: NFS more than any other enhancement to PC/TCP. news@ftp FTP Software, Inc. With InterDrive users have access 26 Princess Street to the storage capacity of NFS Wakefield, MA 01880-3004 servers. Not only does this free Phone: (617) 246-0900 up space locally, but because files FAX: (617) 246-0901 are stored centrally, many people Telex: 981970 can access commonly referenced Answerback: FTP SFTWRE UD files. Electronic mail: news@ftp.com InterDrive is available as an FTP Software welcomes sug- add-on to PC/TCP, version 2.02 or gestions and contributions from greater, for $100. PC/TCP Plus is readers. Submissions for the a new package which contains PC/TCP next issue of the newsletter must version 2.03 and InterDrive, and be received no later than June 1, sells for $490. Upgrades for older 1988. versions of PC/TCP are also avail- able. Site license pricing is FTP Software and LANWatch are available for all of these prod- trademarks of, and PC/TCP is a ucts. Ask for the InterDrive data registered trademark of FTP Soft- sheet for more details. ware, Inc. Several OEMs Add NetWareTM Copyright 1988, 1989 by FTP Compatibility Software, Inc. Permission to use, copy, modify, and distribute The number of FTP Software OEMs this publication for any purpose supporting our Packet Driver Speci- and without fee is hereby fication has swelled in recent granted, provided that this copy- months. Each of the new OEMs has right and permission notice written a Packet Driver for PC/TCP appear on all copies, the name of that provides full compatibility FTP Software, Inc. not be used in with NetWare. The new vendors are advertising or publicity pertain- AcerTM, D-Link(R), Gateway Communi- ing to distribution of the mate- cations and IMC Networks. They rial without specific prior join the ranks of BICC Data Net- permission, and notice be given works, Proteon, Schneider & Koch that copying and distribution is and Univation, who have been pro- by permission of FTP Software, viding PC/TCP-NetWare compatibility Inc. for up to two years. PC/TCP-NetWare compatibility is a major benefit for NetWare cus- tomers, because they can alternate between NetWare and PC/TCP commands ___________________________________________________________________________ 2 May 1989 May 1989 news@ftp ___________________________________________________________________________ without rebooting. They can even series of DEC, HP and Tektronix use both protocols at the same emulators to run over PC/TCP Plus. time! For example, they can use Diversified Computer Systems' FTP to transfer a file from a series of DEC and Tektronix emula- TCP/IP host to a NetWare server. tors is also compatible with PC/TCP, and GrafpointTM offers sev- Vendors or customers who are eral compatible Tektronix emula- interested in writing a Packet tors. Driver for a particular card simply need to obtain a copy of PC-210 and Token Ring Networks the Packet Driver Specification. Included with PC-210 are a set of By Benjamin Levy public domain packet drivers, some of which include source, that can Writing drivers for the IEEE LAN be used as the basis for your new standard 802.5 Token Ring network- Packet Driver. To obtain NetWare which is also known as 4 megabit compatibility, the NetWare driver Token Ring, IBM Token Ring and also needs to be modified to con- ProNET-4(R) networks-has taught me form to the Packet Driver Specifi- a lot about how the Token Ring cation. works and what its problems are. In the following paragraphs I will Interrupt 14 Telnet Upcoming try to share some of that knowledge with you. Users of many commercially avail- able terminal emulation packages There are two ways for network will be glad to know that the next applications to communicate with release of PC/TCP (due out in sev- the Token Ring cards. Either they eral months) will contain an inter- can talk directly to the card rupt 14 Telnet. Many popular emu- (handle interrupts from the board, lators will then run unmodified transfer data to and from the over PC/TCP. board, etc.) or they can talk to an intermediate software interface, Interrupt 14-compatible emulators which handles all the details of are available for a wide variety of how the board works. Many network terminals, including DEC, HP and applications use the latter method. Tektronix(R) terminals. Among the IBM created a device independent vendors who supply interrupt 14 interface for Token Ring boards emulators are Diversified Computer called the Adapter Support Inter- Systems, KEA Systems, Persoft, face, or ASI. This enables the end Polygon, Softronics(R) and Walker user to use network applications Richer & Quinn. For users who which were designed to work on IBM don't want to wait for the next Token Ring boards with Token Ring version of PC/TCP, the pre-release boards made by other manufacturers. version of the interrupt 14 Telnet is available for $40 per copy (for IBM makes two different versions PC/TCP versions 2.02 and greater). of the ASI. The older version is called TOKREUI.COM and it can be Three vendors also offer emu- loaded into memory at any time. lation packages for the current The new version of IBM's ASI is version of PC/TCP (2.03). Walker called the Lan Support Program. Richer & Quinn offers a package The Lan Support Program is intended called Telnet Manager, which allows to be used with DOSTM 3.3 and all of their Reflection(R) Plus higher. It will also work on a _______________________________________________________________________ 3 May 1989 May 1989 news@ftp ___________________________________________________________________________ wider variety of IBM computers, their ProNET-4, which is func- including PS/2s. The Lan Support tionally equivalent to the IBM Program is made up of two program Token Ring. The p1340 is an 8 bit modules which are called board for either XTTM or AT(R) bus DXMC0MOD.SYS and DXMA0MOD.SYS. The PCs, the p1344 and p1345 are 16 bit modules are loaded into memory by boards for AT bus PCs, the p1345 is CONFIG.SYS. a new version of the p1344 which has been modified to work with PC- Many of the other Token Ring man- AT clones that are not 100 percent ufacturers have ASIs for their compatible with IBM's PC/AT, and Token Ring boards. Proteon has an the p1840 is a Micro Channel equivalent of IBM's TOKREUI.COM Adapter board for the Personal Sys- called PRO4EUI.EXE, Sytek has tem/2TM. ASI.EXE and 3ComTM has 3COMREUI.EXE. 3Com makes the TokenLinkTM (part number 3C603) and TokenLink Plus To use the new ASI with non-IBM (part number 3C605). Western Digi- Token Ring boards (i.e. Proteon, tal makes the Token-CardTM (part 3Com, and others) you will need DLC number WD8005-TR) and TokenCard ROMs on the Token Ring board. If WSTM (part number WD8005-TRWS). the board has a DLC ROM version All of these boards work in PC, XT, less than 2.08 you may have to get or AT bus PCs. a new set from the dealer or manu- facturer. The DLC ROMs can usually Other Token Ring boards I've be found in sockets on the left heard of but haven't tried, are a hand side of the board and will Token Ring board made by Gateway usually have "DLC" written on them Communications, NCR's PC Token-Ring and have a TI, IBM or Sytek copy- Connection, Sytek's 6140 Token Ring right. card (which is also resold by other OEMs), and a board made by Unger- NCR, Proteon, Sytek, Western Dig- mann-Bass. ital, and 3Com make drivers that can work with IBM's Lan Support How the Token Ring works Program by replacing IBM's DXMC0MOD.SYS with their own version The IBM and Proteon Token Rings of the driver. Note that you must pass data at a rate of 4 Megabits also purchase the Lan Support Pro- per second. Each board in the gram from IBM or a dealer even Token Ring plugs in to a wire cen- though you are using a Token Ring ter. But the board doesn't actu- board from a different manufac- ally become part of the ring until turer. the board is initialized by the software and is told to enter the IBM makes three Token Ring cards: ring. Boards in the ring take the Token Ring Network PC Adapter, turns talking, and this is regu- the Token Ring Network PC Adapter lated by a token. In each ring II, and the Token Ring Network there is one token, which gets Adapter/A for Micro ChannelTM passed from one board in the ring Adapters. The PC Adapter II can be to the next. If a board has a distinguished from the PC Adapter packet to send, it must wait until by the extra memory on the PC it gets the token to put the packet Adapter II board. on to the ring. The packet will then be passed from one board to Proteon makes four boards for the next, until it reaches the __________________________________________________________________________ 4 May 1989 May 1989 news@ftp ___________________________________________________________________________ recipient. When the recipient is the IP layer and is the same as receives the packet it will set a the IP layer over the Ethernet (or flag in the packet, marking the any other network type). packet as received. Then it puts the packet back in the ring. When The way RIFs are used is as fol- the packet gets back to the sender, lows: When you want to open a con- the sender will be able to check if nection to another machine, the PC the packet has been read by the sends out an address resolution recipient. protocol (ARP) packet asking for the hardware address of the desti- The first board to enter the ring nation machine. Each bridge on the becomes the active monitor. The Token Ring will add its two byte active monitor constantly watches address to the RIF as it passes the the traffic on the ring, checking packet across the bridge to the for a missing or duplicate token. next Token Ring. When it finally If either occurs, it will flush the gets to the destination machine, ring, then it will put a new token the RIF will contain the path on the ring. The active monitor needed for sending the reply. The also keeps track of the boards in destination machine will then send the ring, and it will inform the a reply back to the original sender other boards in the ring if it which contains the RIF with the notices that one of the boards is path in it and its hardware malfunctioning. The other boards address. in the ring are standby monitors, waiting to take over if they notice PC/TCP and LANWatch(R) that the active monitor has left the ring, or if it is having prob- FTP offers two software appli- lems. All of the monitoring is cations for the Token Ring. There done automatically by the Token is PC/TCP, which is a set of net- Ring board, and does not interfere work applications for intercommuni- with the other operations of the cation, and LANWatch, which is a PC. network analyzer program. A ver- sion of PC/TCP (part numbers PC-108 The first two protocol layers of and PC-208) talks directly to Pro- the packets on the Token Ring are teon's ProNET-4 boards, and another the Physical or MAC (Media Access version (part numbers PC-119 and Control) Layer, which is described PC-219) uses the Adapter Support by IEEE standard 802.5, and the Interface. A version of LANWatch Data Link Layer, which is described (part number LW-108) uses Proteon's by IEEE standard 802.2. The MAC ProNET-4 boards. No version of header contains a two byte field LANWatch exists for the IBM Token which indicates the packet type, Ring cards because of IBM security the source and destination hardware features built into those cards. addresses, and the Routing Informa- tion Field (RIF). The 802.2 header LANWatch on Proteon's ProNET-4 is made up of the LLC (Logical Link cards requires DLC ROMs (version Control) layer and the SNAP (Sub- 2.01 or higher). Some of Proteon's Network Access Protocol). For the earlier boards didn't come with the purposes of encapsulating IP over DLC ROMs needed for LANWatch. You 802.2, the values for the LLC and can check for their presence by SNAP headers are constant, except looking on the the left-hand side the value of the Ether Type field of the board. If there are two or in the SNAP header. The next layer three empty chip sockets on the __________________________________________________________________________ 5 May 1989 May 1989 news@ftp ___________________________________________________________________________ board, then you'll need to order the boards. Banyan is aware of the DLC chips from Proteon. Their this problem and they are in the part number is p5412-12 for the process of fixing it. Until then, p1340 board and p5412A-12 for the to get around the problem just tell p1344 and p1345 boards. The DLC the board to use an address that chips also come with a disk con- doesn't have the first bit of the taining PRO4EUI.EXE. third byte set. In both cases, the address being used by the board can All of the Token Ring boards that be changed at the software level. I have tried work with our PC/TCP The first three bytes of Proteon's software, provided that the DLC hardware address are 40-00-c9, and ROMs on the Token Ring boards are the first three bytes of 3Com's version 2.08 (or higher). address is 42-60-8c. If the address is changed, the addresses If you are using PC/TCP with an become 40-00-49 and 42-60-0c ASI, it is advisable to start respectively. PC/TCP first. This allows it to initialize the ASI and to open the Proteon: Token Ring board before you use other manufacturer's network appli- 4 0 0 0 c 9 cations. 0100 0000 0000 0000 1100 1001 ... ^ While testing the driver for PC- offending bit 119 and PC-219, it was discovered 3Com: that the ASI was causing problems 4 2 6 0 8 c by writing over memory randomly. 0100 0010 0110 0000 1000 1100 ... To fix this problem, WATSR.EXE was ^ created. WATSR.EXE is a simple again terminate and stay resident program that sets aside 256 bytes of memory The same addresses with the first for the ASI to use, then passes the bit of the third byte set to 0. address of the work area to the PC/TCP programs so they can tell Proteon: the ASI to use the work area pro- vided to it. 4 0 0 0 4 9 0100 0000 0000 0000 0100 1001 ... Since the release of the 2.03 version of PC-208 and PC-219, and 3Com: the release of the 1.16 patch level 4 2 6 0 0 c 5 version of PC-108 and PC-119, 0100 0010 0110 0000 0000 1100 ... PC/TCP has been able to work with RIFs. Note that the Token Ring board Problems will tell you if the cable is not attached to the board, but it won't There are some problems that may tell you if the cable is not occur when using Banyan's VINESTM attached to the wire center. If file server (version 3.01) as a you are having a problem with a gateway for Proteon and 3Com Token Token Ring board that is neither Ring boards. Apparently the Banyan sending nor receiving packets, try VINES file server was having prob- checking that the far end of the lems with the manufacturer address cable is attached to the wire cen- part of the hardware addresses on ter. __________________________________________________________________________ 6 May 1989 May 1989 news@ftp ___________________________________________________________________________ If you are using IBM's LAN Sup- International Business Machines port Program with IBM's NetBIOS Corporation, 1986. interface, you must tell DXMT0MOD.SYS to leave extra service access points (SAPs) for other pro- grams to use (e.g. PC-119 or PC- 219). This can be done by adding the option "ES=1" or "ES=2" to DXMT0MOD.SYS in config.sys. Read the documentation on the disk that contains the software for more information about IBM's LAN Support Program and its options. If you are using FTP's NetBIOS program with PC-219, you do not need to load DXMT0MOD.SYS in CONFIG.SYS. Acknowledgements I'd like to thank Ellie Gittelman of Proteon, Inc. and Drew Perkins of Carnegie Mellon University for their assistance. References For a more detailed description of how the Token Ring works see the following sources: IEEE Standard for Local Area Net- works: Logical Link Control. ANSI/IEEE Standard 802.2, 1985. Produced by The Technical Committee Computer Communications of the IEEE Computer Society. A Standard for the Transmission of IP Datagrams over IEEE 802 Net- works. RFC-1042. Written by J. Postel and J. Reynolds. TMS380 Adapter Chipset User's Guide. Produced by Texas Instru- ments TMS380 Adapter Chipset User's Guide Supplement. Produced by Texas Instruments. Token Ring PC Network Adapter Technical Reference. Printed by ___________________________________________________________________________ 7 May 1989 May 1989 news@ftp ___________________________________________________________________________ Recent Workstation-Oriented were not adequate for this use, in Enhancements to Telnet any case. NAWS allows window dimensions up to 65536 x 65536, and by James VanBokkelen establishes both dimensions in one operation. The older options were While many modern personal com- limited to 253 x 253, and required puters and workstations have bit- one operation per dimension mapped displays, most applications changed. Since most window changes software still expects to communi- affect both dimensions, this might cate with an asynchronous terminal. result in two successive screen Mechanisms like the BSD TERMCAP updates being sent to the client. variable and VMS Screen Management allow applications to support many Terminal Type Option Enhanced kinds of asynchronous terminals, and workstation windowing software RFC 1091, by James VanBokkelen of typically includes one or more FTP Software, defines the existing asynchronous terminal emulations. Telnet Terminal Type (TTTYPE) The transition from simple termi- option, to allow the Telnet server nal-style user interfaces to more to review the client's list of sup- sophisticated schemes is evident in ported terminal emulations, and many places, but it will take a select the one it likes best. long time to complete. Meanwhile, Later, possibly at an application's two recent RFCs describe additions request, another terminal type from to the Telnet protocol which make the supported list can be selected. things easier on the users stuck in the middle. As the option had previously been defined in RFC 930, the client Negotiate About Window Size Option indicated end-of-list by sending Defined the last supported type a second time. Thus, a server could only RFC 1075, by David Waitzmann of see the list of types once, and BBN, defines a mechanism to pass because the most desirable type was information about display window listed first, most existing sizes and size changes from client implementations simply settled for to server (and to co-operating that one. Also, multiple emulation full-screen applications). A new modes had not really been dealt Telnet option, Negotiate About Win- with, and the exact point at which dow Size (NAWS), is specified, and the mode changed was not specified. client and server are expected to negotiate it with WILL/WONT/DO/DONT The new specification builds on like other options. If NAWS is the old, while maintaining back- agreed on, then the client can send wards compatibility with RFC 930. Telnet Sub-Negotiation sequences to The option value remains the same, the server to indicate the initial and old servers will receive the display aperature dimensions (in same end-of-list indication as characters), and further Sub-Nego- before. However, if a new server tiation sequences later if the sends one more request after dimensions change. receiving the end-of-list marker, a new client is expected to return to Two previously defined Telnet the top of its list. The mode options, Negotiate Output Line change is defined as taking place Width and Negotiate Output Page when each new type is sent. Size, had never entered common use, and RFC 1073 comments that they _______________________________________________________________________ 8 May 1989 May 1989 news@ftp ___________________________________________________________________________ What the User Can Expect the technical side of the Connec- tathon. Most of the problems were When will these options show up due to lack of information, for in your environment? That depends example, what addresses each of the on the energy of your vendors (or vendors should use, what broadcast the authors and maintainers of any addresses were valid, and some public domain software in use at technical questions about specific your site). NAWS is most important NFS implementations. where windowing software is widely used, so its first implementations Sun Microsystems put together an have been in public-domain software NFS test suite which provided a packages maintained at CMU. TTTYPE fair level of functional testing. is more important in business and Unfortunately, their test suite was non-Unix environments, where appli- not available for DOS, so those cations are more likely to be coded venders who had DOS implementations for use on only a few terminals. got together a test suite from a There are already a couple of combination of software from a few forward-looking TCP/IP vendors with of the vendors. plans for supporting the extended Terminal Type option. While the test suite for DOS was being prepared, we started our own Sun Sponsors NFS Connectathon tests against the other vendors' software. The testing procedure Sun Microsystems sponsored an NFS was very simple-you walked over to Connectathon on February 18 through one of the vendors and said, "Hi, 22 in Santa Clara, CA. It con- I'd like to test against your sisted of a technical forum for server." Then they would tell you testing NFS implementations from what to mount, and what your userid the various vendors, plus a number should be, and you'd begin testing of sessions on topics relating to against them. At first, many of NFS. the implementations did not perform well, but as time went on most of The purpose of the Connectathon them were in very good shape. By was to provide a friendly forum for the time the Connectathon ended a NxN testing of the NFS products large percentage of the vendors had currently available or under tested against most of the other development. NxN testing means implementations. that every implementation of the software in question tests against In addition to the testing, there every other implementation that is were sessions on various subjects. present at the test, where N is the However, most of the true learning number of implementations. seemed to occur in the technical portion by running the test suites, There were around 70 vendors rep- watching the network, listening resented, and about 60 of them had when other people discussed their NFS implementations of one sort or problems, and talking to other peo- another. The other vendors were ple about their implementations. present in order to test their X- The people from FTP who attended window software. Of all of the NFS the event learned a lot by their implementations, only a few were PC participation. products. As may be expected, a spirit of As always in these sessions, cooperation prevailed during the there was some initial confusion on _______________________________________________________________________ 9 May 1989 May 1989 news@ftp ___________________________________________________________________________ event, allowing many vendors to work together to ensure interoper- ability. The vendors were willing to assume that their code might be as much at fault as the other side. We'd like to extend a special vote of thanks to Sun Microsystems for sponsoring the event, and Carl Beame from Beame and Whiteside for the time he spent debugging code from other vendors. PC/TCP, LANWatch and FTP Software are registered trademarks of FTP Software, Inc. Acer is a trademark of Acer Incor- porated. VINES is a trademark of Banyan Sys- tems, Inc. D-Link is a registered trademark of Datex Systems, Inc./Localnet Commu- nications, Inc. Grafpoint is a trademark of Graf- point. IBM, IBM Personal Computer and IBM Personal Computer AT are registered trademarks, and Personal Computer XT, Micro Channel, Personal Sys- tem/2 and DOS are trademarks of International Business Machines Corporation. NetWare is a trademark of Novell, Inc. ProNET-4 is a registered trademark of Proteon, Inc Softronics is a registered trade- mark of Softronics, Inc. NFS is a trademark of Sun Microsys- tems, Inc. Tektronix is a registered trademark of Tektronix, Inc. 3Com and TokenLink are trademarks of 3Com Corporation. Reflection is a registered trade- mark of Walker Richer & Quinn, Inc. WD, TokenCard and TokenCard WS are trademarks of Western Digital Cor- poration. Ethernet is a trademark of Xerox Corporation. __________________________________________________________________________ 10 May 1989