How to Set Up Network Disk Sharing in Windows 3.11

Microsoft Windows for Workgroups 3.11 revolutionized small-office and home networking by introducing native peer-to-peer file sharing directly into the Windows graphical interface. Unlike standard Windows 3.1, which required third-party networking software like Novell NetWare to access remote resources, Windows for Workgroups 3.11 allowed users to share local hard drives and directories with other computers on the same local area network (LAN) using built-in protected-mode protocols and familiar management tools like File Manager.

Network Hardware and Protocol Configuration

Before a local disk could be shared, Windows 3.11 required proper hardware driver and protocol installation through the Network Setup utility located in the Network program group.

  1. Driver Installation: The system used 32-bit protected-mode network drivers (NDIS 3.0), which improved performance and freed up conventional DOS memory.
  2. Protocol Selection: The default transport protocol was NetBEUI (NetBIOS Extended User Interface), though users could also install IPX/SPX-compatible protocols or TCP/IP-32 via an add-on package.
  3. Computer and Workgroup Identification: Users designated a unique Computer Name and assigned the machine to a specific Workgroup within the Network Control Panel applet.
  4. Enabling Sharing: Under the "Sharing" configuration screen, the user had to check the box for "I want to be able to give others access to my files". This loaded the VSHARE.386 or standard SHARE.EXE background engine to handle file locking and concurrency.

Creating a Disk Share in File Manager

Once networking was active, sharing a local disk or folder was handled entirely inside File Manager (WINFILE.EXE).

  1. Select the Target: The user navigated to and highlighted the specific drive letter or folder to be shared.
  2. Open the Share Dialog: From the menu bar, the user clicked Disk, then selected Share As... (or clicked the hand-holding-a-folder icon on the toolbar).
  3. Configure Share Properties:
    • Share Name: A NetBIOS-compliant name (maximum 12 characters, often kept to an 8.3 format for DOS clients).
    • Path: The local path of the resource (e.g., C:\ or C:\DATA).
    • Comment: An optional text description visible to other network users.
    • Re-share at Startup: A checkbox enabling the share to automatically persist across reboots.

Setting Access Types and Passwords

Windows 3.11 relied on share-level security rather than user-level access control lists (ACLs). Access permissions were controlled exclusively by passwords assigned directly to the shared resource:

  • Read-Only: Remote users could view, copy, and run files, but could not delete, alter, or create new files. A read-only password could be required.
  • Full: Remote users had unrestricted read, write, modify, and delete permissions. A full-access password could be assigned.
  • Depends on Password: This option assigned two different passwords to the same share. Entering the read-only password granted read access, while entering the full-access password granted write access.

Accessing the Shared Drive from Another Computer

Other clients on the local network mapped the shared drive using their own File Manager:

  1. Click Disk and select Connect Network Drive....
  2. Select an available local drive letter (e.g., D:, E:, or Z:).
  3. Type the Universal Naming Convention (UNC) path in the format \\COMPUTERNAME\SHARENAME, or browse the visual directory tree of workgroups and computers.
  4. Check Reconnect at Startup if persistent access was required.
  5. Provide the share password when prompted.

Once mapped, the remote folder functioned identically to a local hard drive inside File Manager and DOS applications.