Copyright: ® FTP Software, Inc. 1997. All rights reserved.
Citation: ® Copyright FTP Software, Inc. 1997. All rights reserved.


Master Table of Contents
Reference Desk for FTP Software, Inc.
Information on Demand

Reference Desk provides access to online versions of OnNet16™ version 2.5 documentation (listed below).

FTP Titles

Roadmap	Provides a graphical representation of the documentation set.

 User′s Guide
Provides a product overview and describes how to perform everyday networking tasks using OnNet16 applications for Microsoft Windows.

 Advanced User′s Guide
Describes how to use the more sophisticated features of the product.

Part I,  "Installing and Configuring OnNet16," provides detailed information about installing and configuring the product, and about configuring the kernel (TCP/IP protocol stack) to interoperate with other network operating systems.

Part II, "Managing OnNet16 Kernel and Network Services," explains how to manage the kernel and use applications to solve potential problems.

Part III, "Using Network Security," describes how to configure support for Kerberos security or SOCKS security on your PC.

Using Networking Commands in DOS
Describes how to perform everyday networking tasks using OnNet16 commands for DOS.

Command Reference	Describes how to use OnNet16 commands for DOS in detail.

Document Conventions	Describes the typographical conventions used in the documentation.

Notices	Contains copyright and license notices.

Getting Technical Assistance	Describes how to obtain technical support.


!#$+


Notice page
Notice

The information in these documents is subject to change without notice and should not be construed as a commitment by FTP Software®, Inc.

While every effort has been made to assure the accuracy of the information contained herein, FTP Software, Inc. assumes no responsibility for errors or omissions. No liability is assumed for incidental or consequential damages resulting from the use of the information contained in these documents.

The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license.

© Copyright 1986-1997 by FTP Software, Inc. All rights reserved.

© Copyright Unipalm Limited 1994-1996. All rights reserved.

© Copyright VISUAL COMPONENTS, INC. 1995 All rights reserved.

© Copyright Andrew Corporation 1992-1994; © 1985, 1995 Relay Technology, Inc.

© Copyright 1994-1995 RSA Data Security, Inc. All rights reserved.

© Copyright 1989 Regents of the University of California. All rights reserved. For a complete copy of the SOCKS license, see the SOCKS license that appears at the front of this book.

The IBM 3270 terminal emulator that is part of tn incorporates source code copyrighted by, and distributed with permission of, the Regents of the University of California and Gregory Glenn Minshall.

Copyright © 1984-1986 by the Regents of the University of California and by Gregory Glenn Minshall.

Permission to use, copy, modify, and distribute these programs and their documentation for any purpose and without a fee is hereby granted, provided that this copyright and permission appear on all copies and supporting documentation, the name of the Regents of the University of California not be used in advertising or publicity pertaining to distribution of the programs without specific prior permission, and notice be given in supporting documentation that copying and distribution is by permission of the Regents of the University of California and by Gregory Glenn Minshall. Neither the Regents of the University of California nor Gregory Glenn Minshall make representations about the suitability of this software for any purpose. It is provided "as is" without express or implied warranty.

RESTRICTED RIGHTS LEGEND

USE, DUPLICATION, OR DISCLOSURE BY THE GOVERNMENT IS SUBJECT TO RESTRICTIONS AS SET FORTH IN SUBPARAGRAPH (C) (1) (ii) OF THE RIGHTS IN TECHNICAL DATA AND COMPUTER SOFTWARE CLAUSE AT DFARS 52.227-7013 or other similar provisions of other agencies. Copyright FTP Software Inc., 100 Brickstone Square Fift Floor, Andover, MA 01810. UnpublishedAll rights reserved under the Copyright Laws of the United States.

PC/TCP® Network Software, OnNet®16, and OnNet®32 are based on a set of programs originally designed and developed by the Massachusetts Institute of Technology. FTP Software, Inc. has made extensive modifications and enhancements to the M.I.T. programs.

Kerberos for PC/TCP® is based on code developed at the Massachusetts Institute of Technology.

©  Copyright 1989 by the Massachusetts Institute of Technology.

Export of this software from the United States of America is assumed to require a specific license from the United States Government. It is the responsibility of any person or organization contemplating export to obtain such a license before exporting.

FTP Software®, InterDrive®, OnNet®16, OnNet®32, PC/BIND®‚ and PC/TCP® are U.S. registered trademarks of FTP Software, Inc.; CyberAgent™, Esplanade™, and KEYview™ are trademarks of FTP Software, Inc. Other trade names, trademarks, or registered trademarks are property of their respective holders.

© Copyright 1992/3 Theo de Raadt <deraadt@fsa.ca>. All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

3. The name of the author may not be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE AUTHOR AS IS AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

SOCKS License

Portions of the SOCKS code are subject to the following license terms:

Copyright © 1989 Regents of the University of California. All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

3. All advertising materials mentioning features or use of this software must display the following acknowledgment:

This product includes software developed by the University of California, Berkeley and its contributors.

4. Neither the name of the University nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS AS IS AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Portions Copyright © 1993, 1994 by NEC Systems Laboratory.

Permission to use, copy, modify, and distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies, and that the name of NEC Systems Laboratory not be used in advertising or publicity pertaining to distribution of the document or software without specific, written prior permission.

THE SOFTWARE IS PROVIDED AS IS AND NEC SYSTEMS LABORATORY DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL NEC SYSTEMS LABORATORY BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.


Document Conventions

FTP Software manuals use the typographical conventions shown in the following table:

Convention	Description
ALL CAPITALS	Indicates, in text, the names of directories, files, libraries, and paths; for example, ... the PCTCP.INI file ... When the NETLIB.LIB library ... (Exception: UNIX names are shown exactly as they should appear, that is, in mixed case or lowercase.)
Monospace type	Indicates file examples and information that the system generates and displays on the screen, including messages, prompts, and configuration file sections; for example, Host Responding ... The Mailbox name? prompt appears. The sec-key= parameter ...
Bold monospace type	Indicates commands that you enter; for example, C:\> lw -h Enter mget at the system prompt.
Bold regular type	Indicates, in text and in syntax constructions, command names (including literal arguments and options); for example, ... with the idls -a command ... In addition, the boldface term kernel represents a particular TSR kernel command (such as ethdrv). Elsewhere, the term "kernel" refers to any of the PC/TCP kernels.
Italic regular type	Indicates, in text and in syntax constructions, variable options and arguments (including function parameters), for which you must substitute a value; for example, arp hostname ... where hostname is ... Italic is also used occasionally for emphasis; for example, This line must appear.
[  ]	Indicates, in syntax constructions, optional arguments. If you choose to use an optional argument, you must type it exactly as shown (without the brackets); for example,  ... remote_filename [image] Multiple optional arguments are listed individually or combined within brackets. If you choose to use any of the optional arguments, you must type them exactly as shown (without the brackets); for example, ... host [-d][-t] ...  or ... host [-dt]
|	Indicates, in syntax constructions, exclusive arguments, for which you enter only one of the alternatives; for example, comscrpt connection [dialup | hangup | keyword]
(  |  )	Indicates, in syntax constructions, required exclusive arguments or options, for which you must enter one of the alternatives (without the parentheses); for example, tftp (get | overwrite | put)
Note:	Indicates important information; for example, Note: The lpr command lets you use wildcards in filenames.
Caution:	Indicates information to prevent you from damaging software; for example, Caution: Back up your CONFIG.SYS file before you edit it.
Key+Key	Indicates that you must hold down the first key while you press (and hold down) the subsequent key(s); for example, Press Ctrl+P to move to a previous line.
Key, Key	Indicates that you press (and release) each of the keys in sequence; for example, Press Alt, F, X to exit from the DOS shell.
All examples and procedures in this documentation use the default path- and filenames, unless otherwise specified.

Many commands accept pathname arguments. In general, you can use either slashes (/), which is the UNIX convention, or backslashes (\), which is the DOS, Windows, and OS/2 convention, to specify directory names or pathnames in commands.

Note:  Pathnames interpreted on a remote host must conform with the path naming conventions on that host.


documentation roadmap; roadmap


The Command Quick Reference is a paper-only document (online documents appear in green). Online access to the information that it contains is available in the Command Reference manual.


Look for this Help button in the interface of each application.


Technical assistance

Users in the U.S. and Canada, and worldwide resellers, contact FTP Software®:

Telephone:	(800) 382-4387

(508) 685-3600

E-mail:	support@ftp.com

Fax:	(508) 794-4484

 or

Users outside of the U.S. and Canada, contact your local reseller.

Tip

For FREE online technical services, see:

World Wide Web:	http://www.ftp.com

Anonymous Ftp Server:	ftp.ftp.com

Bulletin Board System:	(508) 684-6240 ( settings  8,N,1)

CompuServe:	GO FTPSOFT (PCVENJ Section 8)