Windows NT home directories scenario: Jan (Windows NT Workstation) can access her server-based home directory, but Kim (Windows for Workgroups) cannot. After logon, what action enables Kim to reach her home directory on the Windows NT Server?

Introduction:
Home directories on Windows NT Server are typically UNC paths (for example, \\\\SERVER\\Users\\Kim) that users access after logon. Clients as old as Windows for Workgroups (WfW) can still connect to SMB shares, provided name resolution and credentials are valid. The question asks what concrete step enables access for the WfW client.

Given Data / Assumptions:

• Home directories reside on Windows NT Server.
• Jan uses Windows NT Workstation and can access her share.
• Kim uses Windows for Workgroups and cannot access her share by default.
• SMB/CIFS networking is available on the LAN.

Concept / Approach:
Windows for Workgroups supports SMB file sharing but typically requires manual mapping to a server share. Mapping a network drive (for example, drive H:) to Kim’s home directory explicitly connects her client to the UNC path with appropriate credentials. Replication services and relocating directories are irrelevant to basic access. There is no requirement that only NT clients can use home directories.

Step-by-Step Solution:
1) Confirm Kim's home directory is shared on the server with proper permissions.2) On Kim's WfW computer, open the network client and connect to \\\\SERVER\\Kim (or equivalent).3) Supply valid user credentials if prompted.4) Assign a drive letter so the home directory is easily accessible after logon.

Verification / Alternative check:
Testing a manual UNC connection confirms SMB reachability. Persisted mappings on logon ensure the drive remains available.

Why Other Options Are Wrong:

• Replication service: unrelated to client access of a single share.
• Relocate directory locally: breaks the central home directory model.
• Only NT clients: incorrect—WfW can access SMB shares.
• Create a hidden local share: does not connect to the server path users need.

Common Pitfalls:
Confusing domain logon with share mapping; older clients often need explicit drive mappings.

Final Answer:
Map a network drive on Kim's Windows for Workgroups computer to her server home directory