Microsoft Network Client version 3.0 for MS-DOS

Microsoft Network Client version 3.0 for MS-DOS Release Notes ------------------------------------------------------------- This document contains information about Microsoft(R) Network Client version 3.0 for MS-DOS(R) that wasn't available when the "Windows NT (TM) Server Installation Guide" version 3.51 was printed. Contents -------- 1. Installing Network Client 2. Setup PATH Problem With Microsoft Windows 3. If You Have an 8088 Processor 4. Setup Requires 429K Available Memory 5. Setup is Slow on Some Computers 6. Network Client Cannot Be Set Up on DoubleDisk Drive 7. Windows 3.x Setup Network Choice 8. If COMMAND.COM is Not in Root Directory 9. Using INTERLNK and INTERSVR 10. Using TSRs with Network Client 11. Named Pipes and Enhanced Mode Windows 12. Using Qualitas Maximize or Quarterdeck Optimize 13. Using QEMM Lastdrive 14. Making the Pop-up Interface Visible on a Monochrome Monitor 15. Enabling Validated Logons to Windows NT and LAN Manager Domains 16. Network Settings in SYSTEM.INI 17. NWLink Supports IPX Only 18. Installing the MS-DLC Protocol 19. Installing Remote Access Service 1.1a 20. Browsing the Network Requires a Windows for Workgroups or Windows NT Computer on the Network 21. IPCONFIG.EXE and Controlling DHCP Leases 22. Specifying WINS Servers 23. Differences in MS-DOS TCP/IP 24. Logging On With TCP/IP Across a Router 25. Overview of Windows Sockets 26. Setting DNR and Sockets Settings 27. New and update NDIS Drivers ------------------------------------------ 1. Installing Network Client ---------------------------- If you are installing Microsoft Network Client version 3.0 for MS-DOS on a computer that does not have MS-DOS installed, you will get the error "No Drivers Present On This Disk" if you try to use the Windows Driver Library. You must have MS-DOS installed on the computer. If you have a Windows NT Server floppy disk set and you want to make extra copies of Microsoft Network Client for MS-DOS, note that the installation disk for this client will only fit on a 3.5" floppy disk. 2. Setup PATH Problem With Microsoft Windows -------------------------------------------- If you have Microsoft Windows installed on your computer before you install Network Client, the Network Client Setup program may incorrectly alter the PATH line in your AUTOEXEC.BAT file. The PATH line should include the Windows directory. Check this line after you install Network Client. If the Windows directory was removed from the PATH, add it back in. 3. If You Have an 8088 Processor -------------------------------- You must use the basic redirector if your computer has an 8088 processor. The full redirector is the default, so you must choose the basic redirector when you install. 4. Setup Requires 429K Available Memory --------------------------------------- In order to run Network Client Setup, you must have 429K of available conventional memory. 5. Setup is Slow on Some Computers ---------------------------------- On some computers, particularly those with 8088 processors, Network Client Setup may appear to pause for as long as five minutes. Do not restart your computer. 6. Network Client Cannot Be Set Up on DoubleDisk Drive ------------------------------------------------------ You cannot use Network Client on a Vertisoft Systems DoubleDisk drive. You must set up Network Client on another type of drive. 7. Windows 3.x Setup Network Choice ------------------------------------ If you have installed Microsoft Network Client 3.0 and then later install Windows 3.x, the Windows Setup program asks you to choose your network type from a list. "Network Client" does not appear on the list because it is newer than Windows 3.x. Instead, choose "LAN Manager 2.1." 8. If COMMAND.COM is Not in Root Directory ------------------------------------------ Network Client will not start if your COMMAND.COM file is not in the root directory of your startup drive, unless you have a SHELL command in your CONFIG.SYS file that specifies the location of COMMAND.COM. For information about the COMMAND and SHELL commands, see your MS-DOS documentation. 9. Using INTERLNK and INTERSVR ------------------------------ Do not use the MS-DOS INTERLNK or INTERSVR commands with Network Client. 10. Using TSRs with Network Client ---------------------------------- If you start any terminate-and-stay-resident programs (TSRs) and you are using the basic redirector, you might be unable to unload the basic redirector. 11. Named Pipes and Enhanced Mode Windows ----------------------------------------- Asynchronous named pipes are not supported on Microsoft Network Client when the client is running under enhanced mode Windows. All other client APIs are supported, including NetBIOS, TCP/IP, and IPX/SPX. 12. Using Qualitas Maximize or Quarterdeck Optimize --------------------------------------------------- In some rare situations, Qualitas(R) Maximize and Quarterdeck(R) Optimize may attempt to load some Network Client commands into the upper memory area. If this causes problems, use Maximize or Optimize in manual mode and do not use it to load Network Client commands into the upper memory area. Network Client automatically loads its commands into the upper memory area, if there is enough space. For information about using manual mode, see your Maximize or Optimize documentation. 13. Using QEMM Lastdrive ------------------------ If you add drive letters by using QEMM(R) Lastdrive, and then use Network Client to connect to one of them, the connection will be successful but no information about the shared resources on it will be displayed. 14. Making the Pop-up Interface Visible on a Monochrome Monitor --------------------------------------------------------------- To make the Network Client pop-up interface appear in monochrome mode, type MODE MONO at the MS-DOS command prompt before you display the pop-up interface, or include the MODE MONO command in your AUTOEXEC.BAT file. 15. Enabling Validated Logons to Windows NT Server and LAN Manager Domains ------------------------------------------------------------------- You must run the Network Client full redirector to have your user name and password validated by a Microsoft Windows NT Server or LAN Manager server. 16. Network Settings in SYSTEM.INI ---------------------------------- The [Network] section of your SYSTEM.INI file contains the following settings: filesharing= Does not apply to Network Client. printsharing= Does not apply to Network Client. autologon= Determines whether Network Client will automatically prompt you for logon when it starts. computername= The name of your computer. lanroot= The directory in which you installed Network Client. username= The username used by default at logon. workgroup= The workgroup name. Note that this may be different from the "logondomain" setting. reconnect= Determines whether Network Client restores previous connections when it starts. dospophotkey= Determines the key you press (with CTRL+ALT) to start the pop-up interface. The default is N, meaning that you press CTRL+ALT+N. lmlogon= Determines whether Network Client prompts you for a domain logon when you log on. Set this to 1 if you need to log on to a Windows NT Server or LAN Manager domain. logondomain= The name of the Windows NT Server or LAN Manager domain. preferredredir= The redirector that starts by default when you type the NET START command. autostart= If you choose a network adapter during setup, and specify the startup option Run Network Client Logon, autostart determines which