How to Fix: One-Way or Broken Network Sharing Between Two Windows PCs (Windows 10 & 11)
Quick Fix (For Experienced Users)
If PC-A can access PC-B, but PC-B cannot access PC-A:
- Set both PCs to “Private Network”
- Disable password-protected sharing on both
- Enable these Windows services:
- Function Discovery Provider Host
- Function Discovery Resource Publication
- Access shared folders using \PC-NAME instead of \192.168.x.x
- Share a folder with “Everyone” Read/Write
- Optional: Enable SMB 1.0 for legacy testing
- Optional: Allow insecure guest logon via Group Policy
Are You Facing This?
You’re probably here because:
- You can access one PC, but the other one fails to connect
- Ping works but file sharing fails
- You get “Network path not found” or “0x80070035” errors
- You’re stuck at the “Enter Network Credentials” prompt
- Your PCs don’t appear in the network anymore
Step-by-Step Fix (For Beginners)
Step 1 – Set Network to Private
- Settings > Network & Internet > Wi-Fi/Ethernet > Your Network
- Select: Private Network (on both PCs)
Step 2 – Adjust Sharing Settings
- Control Panel > Network and Sharing Center > Advanced sharing settings
- Turn ON:
- Network discovery
- File and printer sharing
- Turn OFF:
- Password protected sharing
- Save changes
Step 3 – Start Required Services
- Win + R > type
services.msc
- Set these to Automatic and Running:
- Function Discovery Provider Host
- Function Discovery Resource Publication
Step 4 – Share a Folder
- Right-click folder > Properties > Sharing tab > Advanced Sharing
- Check “Share this folder”
- Permissions > Add “Everyone” > Allow Read/Write
- Confirm via Security tab: add “Everyone” with same access
Step 5 – Access from Other PC
- In File Explorer:
\\PC-NAME\SharedFolder
- If it fails, try:
\\[IP Address]\SharedFolder
- Use matching username/password when prompted
Step 6 – Optional: Enable SMB 1.0 (Testing Only)
- Control Panel > Programs > Turn Windows Features On/Off
- Enable “SMB 1.0/CIFS File Sharing Support”
- Reboot
- Only use temporarily for compatibility tests
Step 7 – Optional: Guest Logon Fix (Pro Only)
- Win + R >
gpedit.msc
- Go to:
- Computer Config > Admin Templates > Network > Lanman Workstation
- Enable “Insecure guest logons”
Common Errors Explained
- 0x80070035 – Network path not found
- 0x80004005 – General access denied (permissions)
- “Extended error occurred” – Wrong credentials or services not running
- Login prompt keeps showing – Try matching local accounts/passwords
Extra Troubleshooting Tips
- Restart both PCs after changes
- Try different account with a password
- Temporarily disable firewall/security software
- Restart router
- Ensure same subnet (e.g. 192.168.1.xxx)
- Avoid using IP, prefer \PC-NAME
Security Advice
- Don’t leave shared folders open forever
- Always create a dedicated user with a password
- Avoid SMB 1.0 for daily use – it’s insecure
Frequently Asked Questions & Expert Additions
Why does one PC see the other, but not vice versa?
This is usually caused by Windows disabling certain discovery services by default. Make sure both “Function Discovery Provider Host” and “Function Discovery Resource Publication” services are running on both machines. Also verify you’re on a Private Network.
Why am I stuck at the login prompt even with correct credentials?
-
You might be using the wrong format. Try entering the PC name before the username like:
PCNAME\username
-
Make sure the password is not blank — Windows blocks blank passwords over networks by default.
-
Try using a local account with matching credentials on both machines.
What’s the difference between using IP vs. PC name?
Using \PC-NAME\SharedFolder
is more reliable across reboots and router restarts, because IP addresses can change unless you set up DHCP reservation in your router.
Is SMB 1.0 safe to use?
No. SMB 1.0 is outdated and vulnerable. Only enable it temporarily for compatibility testing with older devices, and turn it off again afterward.
Should I use guest access?
Only if you understand the risks. Guest access can bypass authentication and is often blocked by default in Windows 10/11 Pro. It can be enabled via Group Policy but is not recommended unless necessary for legacy devices.
What causes the 0x80070035 error?
This typically means the path was not found. Causes:
-
Typo in share name or PC name
-
Firewall blocking file sharing
-
Network profile set to Public
-
Required services are not running
Why do shared drives disappear after reboot?
-
Windows sometimes “forgets” mapped drives unless you enable “Reconnect at sign-in”
-
Mapped drives based on dynamic IPs can break when IP changes — use PC name instead
What does “Account restrictions” mean in error messages?
-
You may have tried to connect using an account without a password
-
The account may have login hour restrictions
-
A policy might block network logins (check Local Security Policy)
Pro Tips from Real Users (Based on Forum Insights)
-
Use the full share name instead of IP address — many reported sudden success just by switching to
\ComputerName\SharedFolder
-
Rebooting both PCs after a change is often necessary — especially after changing services or credentials
-
Use identical user accounts on both PCs for easiest access (same name + same password)
-
Prevent automatic updates temporarily if you have an older device with working shares — new builds may reset settings
-
Use
gpedit.msc
to disable digital sign requirements under:-
Local Policies > Security Options > Microsoft Network Client: Digitally sign communications (always)
-
Set to Disabled
-
Bonus Fixes (When Everything Else Fails)
-
Delete mapped drives and recreate them using correct share name
-
Check firewall settings — allow File and Printer Sharing on Private networks
-
Add these registry keys if still stuck (be careful):
-
HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters
-
Set
AllowInsecureGuestAuth
to1
-
-
Set static IPs for both PCs (only if confident)
-
Create a batch script to remap drives at startup
Summary
Fixing Windows file sharing issues requires careful setup of:
-
Network type
-
Services
-
Credentials
-
Permissions
Using PC names, disabling password protection (carefully), and verifying services go a long way. Adding FAQ content helps boost your troubleshooting and your blog SEO.
Let us know in the comments if a specific trick worked for you!