













             PATHWORKS for DOS (TCP/IP) Release Notes




             September 1991




             Software Version:             PATHWORKS for DOS (TCP/IP)
                                           Version 1.1A









             digital equipment corporation
             maynard, massachusetts



 





             _____________________________________________
             September, 1991

             Copyright Digital Equipment Corporation  1991.

             All rights reserved.

             The following are trademarks of Digital Equipment Corporation:

             PATHWORKS, ULTRIX, and VMS.

	     3COM is a registered trademark of 3Com Corporation.

	     Microsoft is a registered trademark of Microsoft Corporation.






          PATHWORKS FOR DOS (TCP/IP) RELEASE NOTES

             These release notes provide information about:

              - New support and functionality in V1.1A

              - Files and directories

              - Installing the correct rexec daemon for ULTRIX

              - Running PATHWORKS for DOS (TCP/IP) with Microsoft
                Windows

              - Connecting to a NETBIOS application on a different
                TCP/IP network 

              - Problems and limitations
             


          I. NEW SUPPORT AND FUNCTIONALITY IN V1.1A

	     New support and functionality in Version 1.1A includes:

             - TRCV additional support for programs running in a graphic
               environment such as Windows.

             - Running PATHWORKS for DOS (TCP/IP) components under Microsoft
               Windows.

             - Ability to do wide area NETBIOS with INETNAME.EXE.

             - Unload and reload PATHWORKS for DOS (TCP/IP) components.



        II.  USING THE FILE TRANSFER PROTOCOL (FTP) 

	     File naming conventions are different for VMS,
             ULTRIX, and DOS. This means you may be unable to
	     use the MGET and MPUT commands between the DOS FTP
	     and VMS or ULTRIX. If file names are incompatible,
	     you must use the PUT or GET command, specifying both
	     input and output file names.



                                                            1







        III. REMOVING VMS DIRECTORIES

	     If you use the MKDIR command at the workstation to
	     create directories on a VMS system, the resulting directories
	     could have file protections that prevent you from
	     deleting the directories. This is normal VMS behavior.

             To remove the protected directory:

              1 Use either of the following VMS commands to add the delete
                attribute to the file owner or the system:

                 - SET FILE/PROTECTION

                 - SET PROTECTION

              2 Delete the file with the RMDIR command.
             
            
 
        III. INSTALLING THE REXEC DAEMON FOR ULTRIX

             The rexec daemon is required if you want to use mail or start
             applications from a terminal session on an ULTRIX system
             using TCP/IP. However, the rexec daemon does not work with
             Version 4.0 of ULTRIX; it works only in BSD security mode
             with Version 4.1 of ULTRIX.

             PATHWORKS for ULTRIX Version 1.0 provides a working version
             of the rexec daemon that can be installed on ULTRIX Version
             4.0. For more details, see the PATHWORKS for ULTRIX Release
             Notes, Version 1.0.



	 IV. RUNNING PATHWORKS FOR DOS (TCP/IP) WITH MICROSOFT WINDOWS

	     Programs that run with the PATHWORKS for DOS (TCP/IP) 
             protocol stack can be started and run within Microsoft 
             Windows 286, Windows 386 and Windows 3.0 (in real, standard 
             and enhanced modes).
        
	     To run a PATHWORKS program from within Microsoft Windows,
             load the PATHWORKS for DOS (TCP/IP) TSRs before running 
             Windows.

	     Customer-written programs can run in Microsoft Windows in 
             a full screen, exclusive mode window if they use only 
             synchronous socket operations. Any asynchronous calls to the 
             socket library may produce a crash or system corruption.


                                                            2 







	     This section describes:

	     - Configuring Microsoft Windows 3.0

             - Loading TSRs to use PATHWORKS for DOS
	       (TCP/IP) programs from Microsoft Windows

	     - Starting PATHWORKS programs from Microsoft Windows

                  
             CONFIGURING MICROSOFT WINDOWS 3.0 
 
             When installing or configuring Microsoft Windows 3.0,
             select the "LAN Manager 1.x (or 100% compatible)" option.

  
	     LOADING TSRs TO USE PATHWORKS PROGRAMS FROM MICROSOFT WINDOWS

	     If you intend to use any PATHWORKS for DOS(TCP/IP) programs
	     within any supported versions of Windows, you must load the
	     required TSRs before you start Windows.  

             Load the following TSRs manually each time you start
             Microsoft Windows, or include them in a batch file that you 
             can run before or when you start Microsoft Windows:

             - TCPTSR.EXE

             - NBTSR.EXE

             - DNRTSR.EXE

             - SOCKTSR.EXE

             - NMTSR.EXE

             - BAPI.EXE

             - TN.EXE

             - EMSBFR.EXE
               
                
	     STARTING PATHWORKS PROGRAMS FROM MICROSOFT WINDOWS

             After you start Windows, you can start PATHWORKS programs 
             in one of two ways:

             - From a DOS window

             - Using the Product Information Files (.PIF) files that are 
               included with PATHWORKS for DOS (TCP/IP)


                                                            3






             Starting PATHWORKS Programs from a DOS Window

             To start a PATHWORKS program from a DOS window:

             1.  Open the Main Group window in the Microsoft
                 Windows Program Manager.

             2.  Double click on the DOS Prompt icon.

             3.  When the DOS prompt appears, type the file name
                 for the PATHWORKS program you want to start, then 
                 press [Return].

                 For example, SEDT.

             NOTE: ARP.EXE, PING.EXE and NETSTAT.EXE are network 
             maintenance utilities.  If you use them from Microsoft 
             Windows, you must run them in a full screen, exclusive 
             mode window.


             Starting PATHWORKS Programs Using .PIF Files

             .PIF files are provided for all programs provided in PATHWORKS 
             for DOS (TCP/IP). See the appropriate PATHWORKS documentation 
             for information on running a program supplied in the PATHWORKS 
             for DOS kit with Microsoft Windows.

             To run a PATHWORKS program within Microsoft Windows, double 
             click on the program's .PIF file.

             The .PIF files for each PATHWORKS program are listed below.  
             A separate set of .PIF files is provided for use with
             Microsoft Windows 3.0.


                               .PIF Files			
             PROGRAM       for Microsoft Windows      .PIF Files for 
             FILENAMES        286 and 386          Microsoft Windows 3.0
             -----------------------------------------------------------
             FTP.EXE           FTP.PIF               FTP30.PIF
             TTY.EXE           TTY.PIF               TTY30.PIF
             PING.EXE          PING.PIF              PING30.PIF
             ARP.EXE           ARP.PIF               ARP.PIF
             NETSTAT.EXE       NETSTAT.PIF           NETSTAT.PIF
             -----------------------------------------------------------

             The .PIF files are located with the program files in the
	     \TCPIP subdirectory of the System Service.
                
              
                                                             
                                                            4




                

          V. CONNECTING TO A NETBIOS APPLICATION ON A DIFFERENT TCP/IP
             NETWORK

             A DOS client running TCP NETBIOS can connect to a
             NETBIOS application (such as the LAN Manager Server)
             located on a different TCP/IP network if the network is 
             accessible through an IP router.

             Before you can connect to a NETBIOS application located
             on a different TCP/IP network, you must run the
             INETNAME utility to add the name of the remote server
             or client (also called computernames) to the TCP 
             NETBIOS driver's internet name table on your workstation. 

             After you add the remote NETBIOS name, you can use the LAN 
             Manager NET USE command or NET SEND MESSAGE command to set up 
             connections to the remote server or workstation to which the 
             remote NETBIOS name refers.

	     In these release notes, the NETBIOS name of the remote 
             workstation or server that you want to connect to is called 
             the internet name.

	     If your system file service is located on a server that
	     is not on the same subnet as your workstation, you must
	     edit the STARTNET.BAT file to run the INETNAME utility
	     before the USE command for the system file service. Add the
	     following line immediately after the Redirector is loaded:

                  INETNAME /LOAD

	     The default number of names available for loading
	     INETNAME is 4. If you use the INETNAME utility's /STORE
	     option to define names of servers on two different
	     networks, the utility creates two names: the server name
	     and messenger version of a name. For example, if you
	     define two servers with the /STORE option in the NBHOSTS
	     database, four inetnames are defined when you
	     use the INETNAME /LOAD option.  

             The rest of this section describes:

             - Command syntax for the INETNAME utility

             - INETNAME utility options

             - INETNAME startup file

             - Changing your workstation's internet name capacity

             - INETNAME utility error messages

                                                            5


              



             INETNAME COMMAND SYNTAX

             To use the INETNAME utility, enter INETNAME at the 
             DOS command line.

             Following are the possible syntax variations for the
             INETNAME command. Variable and optional elements are enclosed 
             in parentheses:

		INETNAME
		INETNAME internet_name IP_address (options)
		INETNAME internet_name IP_address (options)/store (filename)
		INETNAME internet_name /delete (options)
		INETNAME (options) /load (filename)
		INETNAME ?

             Table 1 describes the INETNAME command arguments and options.

             CAUTION:  The internet names that you specify with the INETNAME 
             utility must not duplicate local NETBIOS names or user login 
             names that are added automatically by other LAN Manager 
             utilities, such as the Redirector or the Messenger Service. 
             Specifying an internet name that matches a local NETBIOS name 
             or user name will give you unpredictable results. The internet
	     names that you use with the INETNAME command must always
	     correspond to remote NETBIOS names.

             Table 1	INETNAME Command Arguments and Options

             -------------------------------------------------------------
             Argument         Description
             -------------------------------------------------------------

             internet_name    Specifies the NETBIOS name of the server 
                              or workstation you want to add to your 
                              workstation's internet name table.

                              This NETBIOS name can be, at most, 
                              16 characters in length. The name must not 
                              contain a null (hex 00) or a * in the first
                              character position.  Nonprintable characters
			      may be used anywhere in the name and can be
                              specified using the notation \xx, where xx 
                              is two hexadecimal digits.  If the \ character
                              itself is part of the name, it should be 
                              prefixed with another \, e.g., XYZ\\ABC.

                                                            6





                              If the name is shorter than 16 characters, 
                              it will be padded on the right with the 
                              Fill character up to and including the 
                              15th character position.  The 16th character 
                              position will contain the End character if 
                              the /END option is specified. See further 
                              explanations of the /FILL and /END options 
                              and LAN Manager name convention later in this 
                              section.
                                
             IP_address	      Specifies the IP address corresponding to 
                              internet_name.  It should be specified in 
                              standard internet format, XXX.XXX.XXX.XXX, 
                              where X is a decimal digit, and XXX should be
                              no greater than 255.

                              IP_address is required if adding a name; it 
                              must not be specified when deleting a name.

             /store           Specified either as /STORE or /S.  This option 
                              instructs the INETNAME utility to write 
                              internet_name and IP_address to a startup file, 
                              after adding them to the internet name table.
                              The use of a startup file allows a convenient 
                              way to respecify commonly used internet names 
                              via the /load option every time the workstation
                              is restarted.

                              You cannot specify the /store option with 
                              the /delete or /load options when you use the 
                              INETNAME command.

                              You can specify the startup filename with  
                              the /store option. See filename below.

             /load            Specified either as /LOAD or /L.  This 
                              option loads internet_name and IP_address 
                              entries from a startup file whose name can 
                              optionally be specified by filename.

             filename         Specifies the name of a startup file.  You
                              can prefix the startup filename with a 
                              directory path.  If you include no path, the 
                              current directory is assumed.  See "Internet 
                              Name Configuration Startup File" later in 
                              this section for more information on the 
                              startup file.

             /delete          Specified either as /DELETE or /D.  This 
                              option deletes internet_name from the 
                              workstation's internet name table, but not 
                              from any startup file.

                                                            7






             ?                Displays user help information.

             /case            Specified either as /CASE or /C.  All 
                              internet_names entered, whether from the 
                              command line or from a startup file, usually
                              are converted to uppercase before being added 
                              or deleted. If /case is present, names will 
                              not be converted.

             /fill arg	      Specified either as /FILL or /F, followed by 
                              a character argument.  This option specifies 
                              a character (arg)that is used to fill to the 
                              right, an internet name that is shorter than 
                              16 characters.  If arg is nonprintable, the 
                              \xx notation must be used.

                              The default Fill character when /fill is not 
                              present is the space (hex 20) character.

             /end arg         Specified either as /END or /E, followed by 
                              a character argument.  This option specifies 
                              a character (arg) that is used as the last 
                              (16th position) character in internet_name
                              (whether internet_name is from the command 
                              line or from the startup file).  If arg is 
                              nonprintable, the \xx notation must be used.

                              The default behavior when /end is absent is 
                              that each internet_name will be added to the 
                              NETBIOS name table twice, first with the End 
                              character being a space (denoting a LAN 
                              Manager Server name), and second with the End 
                              character being a hex 03 (a LAN Manager 
                              Messenger name).

                              If an internet_name is already 16 characters 
                              in length, /end will have no effect, and the 
                              name will only be added once.

             ------------------------------------------------------------

                                                            8





             SPECIFYING OPTIONS ON THE INETNAME COMMAND LINE

             You can specify options anywhere on the INETNAME command line.  
             If an option requires an argument value, the value must be 
             specified immediately after the option before beginning 
             another option or specifying an internet_name or 
             IP_address.  For example, the following two sample command 
             lines are equivalent:

             INETNAME /f \00 flamingo / 129.213.80.162 /store myhosts [Return]

             INETNAME /s myhosts flamingo /fill \00 129.213.80.162 /c [Return]

             Options are case insensitive; for example, /STORE and /stOre 
             are equivalent.  The Fill and End argument characters are
             still controlled by the /case option. Other notes:

             - If you use the INETNAME command without an option, the 
               current internet name table is displayed.

             - If you specify an internet_name that is already entered in 
               the internet name table, a duplicate name error message is 
               displayed.

             - If you use the /load option to load a file that has more 
               entries than the internet name table can hold, an error 
               message is displayed.

             - If you use the /delete option, the specified internet_name 
               will be deleted from the current internet name table, but 
               if that name has been stored in the startup file, it will 
               be reentered the next time an INETNAME /load command is given.

             - If you use the /store option, the internet_name written to 
               the startup file is exactly 16 characters in length, with the
               Fill and End character fully disclosed.  Nonprintable  
               characters will be written using the \xx notation.  The 
               INETNAME utility will write the space character as \20, its 
               hexadecimal value.  See "INETNAME STARTUP FILE" in this
	       section for guidelines on specifying names in the startup file.

             If two forms of internet_name have been added to the internet 
             name table--one form as a LAN Manager Server name and the other  
             as a LAN Manager Messenger name--both forms will be written to 
             the startup file as well.

             Examples

             - To use a LAN Manager server 'flamingo', whose IP address is
	       15.6.127.8, type:

               INETNAME flamingo 15.6.127.8 [Return]

                                                            9






             - To identify all the current entries in the table, type:

               INETNAME [Return]

             - To add an entry and to have that entry stored so it can
               be re-added later with the /load option, type:

               INETNAME flamingo 15.6.127.8 /store [Return]

             - To delete a NETBIOS name whose Fill character is A 
               (hex 41), and End character is hex 09, type:

               INETNAME nouveau /f A /end \09 /d [Return]

             - To load a new set up internet_name entries from a file 
               a:\user\myhosts and preserving cases, type:

               INETNAME /1 a:\user\myhosts /c [Return]


	     INTERNETNAME STARTUP FILE

             If you do not specify a startup file name with the 
             INETNAME /load or /store option, the default startup file, 
             NBHOSTS, is used.  NBHOSTS is located in the path specified 
             by the Netfiles parameter in the [Tcpglobal] section of 
             PROTOCOL.INI.

             Each entry in the startup file should have the following 
             format:

                  IP_address internet_name

             The arguments IP_address and internet_name are in the 
             INETNAME command syntax previously described.  The case of 
             the names is controlled by the presence or absence of the 
             /case option when /load is used.

             If a name is shorter than 16 characters in length, the Fill  
             and End characters in effect will apply.  If you do not 
             specify /end during a load operation, the name will be added 
             twice, as a LAN Manager server name and LAN a LAN Manager 
             Messenger name.  To prevent this, you should specify the name
             in full (the \xx notation is allowed) or use the /end option.

             Names written to the startup file using the /store option 
             are always in full format, with space characters written as 
             \20s, and Fill and End characters fully displayed.

                                                            10






             In the following example NBHOSTS file, the two entries for 
             the internet name CASPER_GHOST are padded to 16 characters.  
             The end characters for those entries, \20 and \03, denotes 
             LAN Manager server and LAN Manager messenger names.

                  269.17.2.134          LARRY	
                  269.17.100.77         CASPER_GHOST\20\20\20\20
                  269.17.100.77         CASPER_GHOST\20\20\20\03
                  15.2.3.87             Sue's\20appl
                     
                
             CHANGING YOUR WORKSTATION'S INTERNETNAME CAPACITY

             You can use the internetnames parameter in the [Rfcnetbios] 
             section of your workstation's PROTOCOL.INI file to specify 
             the maximum number of internet names that your workstation
	     can support.

             The internetnames parameter defines the maximum number of 
             internet names that can be added to a workstation's internet 
             name table.  The default value for this parameter is 4.  You 
             can edit this parameter in the PROTOCOL.INI file and specify 
             any value from 0 to 32.

             Sample use of internetnames in PROTOCOL.INI:

                  [Rfcnetbios]
                          drivername = tcpnb$
                          bindings = tcpip
                          internetnames = 16


             INETNAME UTILITY ERROR MESSAGES

             The following error messages may be displayed by the 
             INETNAME utility:


             INET0351:  Name already exists.
             Cause:     The name being added is already present in the 
                        TCP NETBIOS internet name table.
             Action:    Delete the name, then add it with a different
		        IP address.


             INET0352:  Internet name table is full.
             Cause:     You tried to add a name when the internet table
		        is full.
             Action:    Use the INTERNETNAMES keyword of the NETBIOS section 
                        of the PROTOCOL.INI file to increase the table size.

                                                            11






             INET0353:  Name does not exist.
             Cause:     You tried to delete a name that is not in the 
                        internet name table.
             Action:    Check the name you want to delete and try again.


             INET0354:  Name is currently in use.
             Cause:     There are some NETBIOS transactions currently 
                        pending on the name, thus it cannot be deleted.
             Action:    Wait a moment and try again.


             INET0355:  3Com TCP NETBIOS not present.
             Cause:     The program is unable to access the NETBIOS driver
		        or TSR.
             Action:    Ensure that NBDRV.EXE is loaded into memory.


             INET0356:  Cannot access 3Com TCP NETBIOS.
             Cause:     The TCP NETBIOS driver has not been properly started.
             Action:    Check to make sure the workstation has been properly 
                        installed and started with the 3Com TCP product.


             INET0357:  Option <option_name>already specified.
             Cause:     The program option <option_name> cannot be specified 
                        more than once.
             Action:    Recheck what it is you want to specify and try again.


             INET0358:  Option <option_name> conflicts with intended operation.
             Cause:     The following options conflict with one another if 
                        they are specified together in any combination: /LOAD,
                        /STORE, /DELETE.
             Action:    Reenter each option one at a time.


             INET0359:  Load file name is too long.
             Cause:     A file name specified for /LOAD or /STORE is too long.
             Action:    If possible, use CHDIR so the directory path can be 
                        shortened.


             INET0360:  /FILL or /END option incorrectly specified.
             Cause:     An argument is required for the /FILL or /END option.
             Action:    Specify an argument using a single character or 
                        the \xx notation.
 

                                                            12





             INET0361:  \in name must follow by hex digits or another \.
             Cause:     A backslash (\) character in a name must be followed 
                        by two hexadecimal digits or another backslash.
             Action:    Enter two hexadecimal digits or another backslash 
                        and try again.


             INET0362:  Name cannot begin with a null or *.
             Cause:     A NETBIOS name cannot begin with a null (hex00) or 
                        an asterisk (*) character.
             Action:    Remove the null (hex00) or the asterisk (*) and try 
                        again.


             INET0363:  IP address must be of the form ddd.ddd.ddd.ddd.
             Cause:     Standard internet address format ddd.ddd.ddd.ddd 
                        is required for IP address specification.
             Action:    Reenter the IP address in the correct form and try 
                        again.


             INET0364:  Name and/or IP address required for add/delete.
             Cause:     You did not supply sufficient information with
			the command.
             Action:    For delete, be sure to specify a name. For add, 
                        specify a name and an IP address.


             INET0365:  NETBIOS name is too long.
             Cause:     A valid NETBIOS name must consist of 16
			or fewer characters.
             Action:    Reenter the NETBIOS name desired in a 16 character 
                        or less format and try again.


             INET0366:  Argument required for /FILL or /END.
             Cause:     An argument is required for /FILL or /END.  See 
                        NET0360.
             Action:    Specify an argument using a single character or the 
                        \xx notation.


             INET0367:  3Com TCP NETBIOS version 1.2 or higher is required.
             Cause:     INETNAME  requires 3Com TCP NETBIOS version 1.2 or 
                        higher.
             Action:    Install a 3Com TCP NETBIOS version 1.2 or higher  
                        and try again.


                                                            13





             INET0368:  Cannot open/create startup file <file_name>.
             Cause:     <file_name> cannot be opened or created.
             Action:    Make sure the directory path and the file name are 
                        valid.


             INET0370:  Cannot access startup file.
             Cause:     There was a read/write failure while the program
			accessed the startup file.
             Action:    Create a new startup file, possibly in a different 
                        directory, and try again.


             INET0371:  Contents of startup file are invalid.
             Cause:     The startup file must contain only entries of the 
                        form <IP_address><internet_name>
             Action:    Comments are currently not allowed in the startup 
                        file; remove them.


             INET0372:  Unrecognized option <option_name>
             Cause:     The program encountered an illegal option on the
		        command line.
             Action:    Invoke the program again with valid options.


 
         VI. KNOWN PROBLEMS AND LIMITATIONS

             This section describes problems with the following:

              - TCP/IP session timeouts during a suspended X server
                session

	      - Failed TCP/IP connections 

              - ULTRIX Connection (UCX) timeouts on Telnet sessions

	      - Broadcast addresses

              - Files copied between the workstation and VMS with
                the file transfer protocol (FTP)

              - Copying files with the FTP MPUT command

              - Use of expanded memory
               
	      - Host names of a single alphabetic followed by numerics
		do not work.

	      - TCP/IP NBDRV NETBIOS call fails
 
                                                            14 





             TCP/IP SESSION TIMEOUTS DURING A SUSPENDED X SERVER SESSION    

	     TCP/IP sessions can time out during a suspended X 
             server session if there are too many outstanding graphics 
             requests to an X server.

             To resolve this problem, iconify the application to reduce
             the number of graphics requests and reduce the chance of
             timeout.

	     FAILED TCP/IP CONNECTIONS

	     When many TCP/IP connections and disconnections are attempted
	     in rapid succession, some connections may fail. This is
	     because a TCP/IP connection that is broken with agreement
	     of both ends goes into a state called FIN WAIT 2. FIN WAIT 2
	     is a two-minute quiet period on the TCP/IP address port pairs
	     that used for the session were just terminated. This two-minute
	     quiet period is used to disregard packets that were part of the
	     session and not delivered to timeout. This prevents any of
	     those packets from being delivered to the next instance of a
	     connection between the same TCP/IP address port pairs.
	     Because the DOS client has a limit of eight TCP/IP connections,
	     TCP/IP connections may fail quite often.

             PC DECwindows Motif exhibits this behavior when connecting to
	     VMS nodes to start X applications. Starting X applications on
	     a VMS node is accomplished with a Telnet connection; this
	     Telnet connection is terminated by the X server, but there
	     may not be an open socket available for the X client to
	     connect (although connections to additional X clients could
	     be made some time later). 	     

	     Rapid connection and disconnection of file service connections
	     can also cause TCP/IP connections to fail because of lack
	     of resources.

             ULTRIX CONNECTION TIMEOUTS ON TELNET SESSIONS

	     Version 1.3 of the ULTRIX Connection (UCX) changed the
	     functionality of timeouts on Telnet connects from prior
	     versions of the ULTRIX Connection. In future versions of the
	     ULTRIX Connection, this functionality will be configurable.

             Telnet sessions that are not correctly terminated are never
             timed out. If multiple sessions are abnormally terminated,
             you may not be able to connect through Telnet.
              

                                                            15 






	     BROADCAST ADDRESSES

	     PATHWORKS for DOS (TCP/IP) supports only a broadcast
	     address of ones. On ULTRIX and VMS servers, a ones address
	     must be selected in the ULTRIX Connection installation
	     and in the ULTRIX Netsetup utility.

	     You may receive the following message when attempting
	     to use a file or print service on a LAN Manager server
	     with the USE command:

	          "NETWORK NAME NOT FOUND'

	     This message is displayed due to the failure of the
	     NETBIOS Broadcast naming service to resolve the server
	     name. If the VMS or ULTRIX server is correctly
	     installed and operating, the most common causes of
	     the problem are:

	      - The network masks are not the same for the
	        client and server.

	      - The client and server are not on the same
	        TCP/IP network or subnetwork.

	      - There is a bridge or router that is not
	        configured to pass UDP broadcast datagrams.

	      - The TCP/IP broadcast address is zeros and
		must be ones.


             FILES COPIED TO AND FROM VMS WITH THE FILE TRANSFER PROTOCOL

	     If the following events take place, copies of a file transferred
	     between a workstation and VMS will have incompatible
	     syntax:

              1 A file is created or edited on the workstation and
                ends without a carriage return as the last text entry 
                in the file.

              2 You use FTP to copy the file to a VMS system that uses UCX
                and VMS adds a carriage return or linefeed character to the
                end of the file.
              

                                                            16





             COPYING FILES WITH THE FTP MPUT COMMAND

	     If you use the FTP MPUT command to copy files, your current
	     or default directory must be the directory where the files that
	     you are copying are located. Otherwise, the files you specify
	     for copying will be listed, but the copy will fail with a
	     message that says the files could not be found.
               
               
             USE OF EXPANDED MEMORY

             There are two known problems related to the use of expanded
             memory:

             - The PATHWORKS TCP/IP NETBIOS driver, NBDRV.EXE, loads and 
               executes in expanded memory space.  Application buffers 
               that also reside in expanded memory can create a conflict 
               known as the expanded memory context problem.  (Refer to 
               the Lotus/Intel/Microsoft (LIM) Expanded Memory Specification 
               (EMS), version 3.2 or 4.0, for a detailed explanation.)

             - Some applications, such as Microsoft Windows version 2.1 and
               Microsoft Word, perform input/output operations directly to 
               buffers in expanded memory.  If the devices used for these
               requests transfer data using the Direct Memory Access (DMA)
               method, and the correct EMS context for the buffers is not
               available, unpredictable results can occur.

             To solve these problems, a utility called EMSBFR.EXE       
             is installed automatically when you install PATHWORKS
             for DOS (TCP/IP). The installation program places an 
             invocation to the EMSBFR.EXE utility in your STARTNET.BAT file.

             The EMSBFR.EXE utility checks for the presence of any expanded 
             memory in your system.  If found, EMSBFR.EXE will terminate 
             and stay resident; otherwise it simply exits to DOS and will 
             not take up any workstation memory.

             While staying resident, EMSBFR.EXE monitors all DOS file read 
             and write operations.  If EMSBFR.EXE detects that a file write 
             is being done from a program application buffer that resides 
             in expanded memory, EMSBFR.EXE will first copy the data into 
             a temporary buffer located in conventional memory space.  The 
             write request with this new buffer address will then be passed 
             onto DOS for completion.

             Similarly, when a file read operation is destined to an 
             application buffer in expanded memory, EMSBFR.EXE will submit 
             the request to DOS with the buffer address switched to one in 
             conventional memory space.  Once DOS has completed this request,  
             EMSBFR.EXE will copy the data into the original buffer in 
             expanded memory.

                                                            17





             EMSBFR.EXE does not affect the workstation's input/output 
             performance, except where application buffers reside in 
             expanded memory, and there are very few applications that use 
             buffers in this way.


	     HOST NAMES OF SINGLE ALPHABETIC FOLLOWED BY NUMERICS

	     Internet host name of the form xnnnnn where x is any
	     alphabetic and n is numeric do not work correctly.  You will
	     not be able to connect with any host by using a name of that
	     form (A1234 for example).  Create an alias in the HOSTS file
	     that is of a different form (AA1234) or use the IP address
	     directly to connect with that host.

	     TCP/IP NBDRV: NETBIOS CALL FAILS

	     The TCP/IP RFC requires approximately 1 minute after a session
	     is closed before the database is deleted in order for all packets
	     for that session that are currently in the network to have time
	     to either time out and be dropped or delivered.  PATHWORKS for
	     DOS (TCP/IP) has only 8 session data bases that are shared
	     between NETBIOS and Socket operation.  This means that
	     applications that establish and disconnect TCP/IP sessions in
	     rapid succession may run out of available socket databases. This
	     shows up as a failure to connect.  Some time later if the
	     operation is retryed, it succeeds.

	     This problem is often seen if multiple NETTIME operations are
	     done in rapid succession or USE and USE /d to file services are
	     done quickly in succession. You should wait approximately one
	     minute before retrying the operation if you should fail.
                                                       

















                                                            18 


----- End forwarded message
