Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
Microsoft Network Client Version 2.2: User's Guide for MS-DOS Clients > Chapter 2 Using Shared Directories

Connecting to a Shared Directory

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Glossary

 » Index

Connecting to a shared directory allows you to use the directory as if it were a disk drive on your workstation. When you connect to a shared directory, you can use files or programs in that directory. You can also copy files or programs to the directory for use by others. When you connect to a shared directory, you assign a devicename to the directory. A devicename is a name by which your computer identifies a device. In this case, the device is the disk drive the directory you are connected to is on. A disk drive devicename is a letter followed by a colon.

To connect your workstation to a shared directory

  1. Set the current focus on the server with the shared directory you want to use.

  2. From the View menu, choose Available resources.

    The Resources Available at \\computername dialog box appears. The list box displays available resources on the server you specified. Shared directories are listed as Disk in the Type column.

  3. In the list box, select the directory to which you want to connect.

  4. Choose the Use Resource button.

    The Use the resource \\computername\sharename dialog box appears.

    LAN Manager Enhanced provides the next available devicename in the Local device text box, but you can type a different devicename over the one that appears.

  5. In the Password text box, type a password if needed.

  6. Choose the OK button.

  7. Choose the Done button.

Your workstation connects to the directory you selected. You can now use the directory the same way you use your workstation's disk drives. The connection exists as a logical disk drive on your workstation.

Connecting to a Shared Directory Without Setting the Focus

The LAN Manager screen allows you to connect your workstation to shared directories on servers other than the server of current focus. This includes servers that are not visible on the LAN Manager screen and servers in other domains.

LAN Manager Enhanced also lets you connect your workstation to servers on the network that are not running LAN Manager. Because non- LAN Manager servers have different interfaces, their computernames do not appear on the LAN Manager screen. Instead, you connect by specifying each server's path in a dialog box.

To connect to a directory on a server other than the server of current focus

  1. From the View menu, choose Used resources.

    The Resources in Use by username at \\computername dialog box appears.

  2. Choose the Add use button.

    The Use a Network Resource dialog box appears.

    LAN Manager Enhanced preselects Disk in the Type of Use box and provides the next available devicename in the Local device box. You can type a different devicename over the one that appears.

  3. In the Network resource box, type the network path of the shared directory — for example, \\computername\sharename

  4. In the Password box, type a password if needed.

  5. Choose the OK button.

  6. Choose the Done button.

Controlling Persistent Connections

If you often use the same connections (for example, you connect to the same printer every day), having LAN Manager save and restore your connections can save you time and trouble. LAN Manager provides the persistent connections feature, which saves the connections you have when you log off and restores them the next time you log on (if the resources are currently available).

You use the net use command to control the persistent connections feature. By default, the persistent connections feature is turned on.

To change the settings for persistent connections

  • Type net use /p[ersistent]:{yes | no | freeze | save}.

    The yes setting saves all connections as they are made, and restores them the next time you log on. This is the default setting.

    The no setting does not save or restore connections.

    The freeze setting stops saving connections.

    The save setting saves your current connections, overwriting any previously saved connections. These settings will be restored each time you log on. Con nections made after using the net use /p:save command are neither saved nor restored.

Connecting to an IBM LAN Server Resource

If the directory you are connecting to is on an IBM® LAN Server, it may be known by an alias. The alias is a short name that replaces the full path to the resource. To use the resource from LAN Manager, you must supply the full path, since LAN Manager does not support this naming convention.

Making a Onetime Connection to a Shared Directory

You can use a shared directory without assigning a devicename to the connection. For example, to use Microsoft Word to edit the LIST.DOC file in the shared directory with the network path \\SALES\FARWEST, start Word and load the file by typing

word \\sales\farwest\list.doc

Microsoft Word loads the shared file even though you haven't made a previous connection to \\SALES\FARWEST. Note that this procedure doesn't work when you need a password to gain access to \\SALES\FARWEST. In this case, you must first establish access to the directory.

If You Have Trouble Connecting

When you try to connect, you may see this error message:

SYS0071: The network request was not accepted.

This may mean that the server has reached its limit for simultaneous connections or there may be some problem with the server or with your account. Contact your network administrator for help.

In rare cases, you may get an "out of resources" message. If this happens, you probably need to increase the values for the sessions and ncbs keywords in the LANMAN.INI file. See the Installation Guide for Clients for more information on the LANMAN.INI file.

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 1996 Hewlett-Packard Development Company, L.P.