Configure file sharing on the computer named Tally-Dhaka-RJ, then connect using its exact UNC name and valid Windows credentials.
1. Configure the target computer
On Tally-Dhaka-RJ:
- Confirm it is turned on and connected to the same local network as your computer.
- Open Settings → Network & internet → Properties for the active connection.
- Set Network profile type to Private.
- In Settings, search for Manage advanced sharing settings.
- Under Private networks, turn on:
- Network discovery
- File and printer sharing
- Keep password-protected sharing enabled for a business network, and use an account that exists on the target computer. Microsoft’s simpler LAN procedure also permits turning it off, but that provides less protection.^1^
Share the required folder:
- Right-click the folder → Show more options → Give access to → Specific people.
- Select the user who needs access and assign the required permission.
- If this is centrally managed, verify that both the folder’s Sharing permissions and Security (NTFS) permissions allow that user.^2^
2. Connect using the exact path
In File Explorer’s address bar, enter:
\\Tally-Dhaka-RJ
Use two leading backslashes, no space after the hyphen, and the target computer’s exact name. If necessary, include the shared-folder name:
\\Tally-Dhaka-RJ\ShareName
When prompted, enter an account from the target PC, commonly in this format:
Tally-Dhaka-RJ\username
3. If the computer appears but still cannot be opened
On Tally-Dhaka-RJ:
- Press Windows+R, enter
services.msc, and select OK. - For each service below, set Startup type to Automatic and select Start if stopped:
- Function Discovery Provider Host
- Function Discovery Resource Publication
- SSDP Discovery
- UPnP Device Host
These are the sharing services listed in Microsoft’s Windows LAN troubleshooting procedure.^1^
Also open Windows Security → Firewall & network protection → Allow an app through firewall and allow File and Printer Sharing on Private networks; use Domain instead if this is a domain-managed network.^3^
4. Identify a newer SMB security failure
If this started after upgrading to Windows 11 24H2, or the target is a NAS/third-party file server, open PowerShell and collect:
net use
Get-SmbConnection
Get-SmbClientConfiguration
Then inspect Event Viewer → Applications and Services Logs → Microsoft → Windows → SMBClient, particularly Connectivity and Security.^2^
Apply only the branch matching the recorded message:
- Unauthenticated guest access/Event 31017: connect with valid server credentials; do not enable insecure guest access.
- SMB signing required: enable SMB signing on the target server or NAS. Do not weaken the Windows client unless the security impact has been assessed.
- Access denied for only certain users: correct both Share and NTFS permissions.
- Network path not found: verify the exact computer/share name and whether the target is online.
References