Solved Network Sharing Puzzle

SoFine409 · Apr 6, 2023

OK folks I'm really stuck with this one. First let me explain that I've been successfully sharing files and printers on my home network since the days of Windows 7 and I've never had a problem like this. I have an ethernet network of 4 Win 11 PCs and they all share files with no problems and have done so for many years. Today I'm setting a new gaming PC up and following a check list that I've used for several years for networking. But the issue is that while the new PC can connect to my other PCs just fine they cannot connect to the new PC. Very odd.

I've done all the usual stuff like using the same username/password on all of them. Making sure the new PC is set to Private Network with Discovery ON, Network devices connect automatically, File and Printer sharing set to ON. In addition I've checked the usual services:
Function Discovery Provider Host: Manual
Function Discovery Resource Publication: Manual, Trigger Start
Peer Networking Grouping: Manual
Peer Networking Identity Manager: Manual
UPnP Device Host: Manual
PNRP Machine Name Publication Service: Manual

I've set up share names for the new drives and set then to Authenticated Uses (as well as Everyone as a test) but still no go.

But when I try to connect to the new PC with by name or IP address the Credentials dialogue box appears and I type in the username/password that I've used for many years it fails to connect. I've redone each step many times just to be sure and have deleted the newly created credentials as well.

Something that is interesting is that when I run the Network fix bat:
net stop fdPHost /yes
net start FDResPub /yes
Then the new PC becomes visible (but not the shares) but the username/password is still rejected. However this only lasts until the next reboot and then it reverts back to not even showing.

I've also followed all the suggestions by Try3 "A consolidated network setup checklist for Windows 10, Windows 11".

So at this point I've run out of ideas. Any suggestions would be greatly appreciated.

akt196 · Apr 7, 2023

SoFine409 said:
OK folks I'm really stuck with this one. First let me explain that I've been successfully sharing files and printers on my home network since the days of Windows 7 and I've never had a problem like this. I have an ethernet network of 4 Win 11 PCs and they all share files with no problems and have done so for many years. Today I'm setting a new gaming PC up and following a check list that I've used for several years for networking. But the issue is that while the new PC can connect to my other PCs just fine they cannot connect to the new PC. Very odd.

I've done all the usual stuff like using the same username/password on all of them. Making sure the new PC is set to Private Network with Discovery ON, Network devices connect automatically, File and Printer sharing set to ON. In addition I've checked the usual services:
Function Discovery Provider Host: Manual
Function Discovery Resource Publication: Manual, Trigger Start
Peer Networking Grouping: Manual
Peer Networking Identity Manager: Manual
UPnP Device Host: Manual
PNRP Machine Name Publication Service: Manual

I've set up share names for the new drives and set then to Authenticated Uses (as well as Everyone as a test) but still no go.

But when I try to connect to the new PC with by name or IP address the Credentials dialogue box appears and I type in the username/password that I've used for many years it fails to connect. I've redone each step many times just to be sure and have deleted the newly created credentials as well.

Something that is interesting is that when I run the Network fix bat:
net stop fdPHost /yes
net start FDResPub /yes
Then the new PC becomes visible (but not the shares) but the username/password is still rejected. However this only lasts until the next reboot and then it reverts back to not even showing.

I've also followed all the suggestions by Try3 "A consolidated network setup checklist for Windows 10, Windows 11".

So at this point I've run out of ideas. Any suggestions would be greatly appreciated.

Win+R => services.msc
DNS Client - Automatic
Function Discovery Resource Publication- Automatic
Function Discovery Provider Host - Automatic
UPnP Device Host - Automatic
SSDP Discovery - Automatic
restart computer => check sharing

Start => Windows Defender Firewall => Allowed an app or feature through Windows Defender Firewall => File and Printer Sharing => check all boxes (activate)

Start => Windows Defender Firewall => Advanced settings => Indound rules =>File and Printer Sharing (all servicess -enabled,allow the connection)
Win+R => cmd (run as administrator) => sfc /scannow
Win+R => cmd (run as administrator) => DISM /ONLINE /CLEANUP-IMAGE /RESTOREHEALTH
restart computer => check sharing

hsehestedt · Apr 7, 2023

There is one item in particular that I did not see you address that has tripped me up before: NTFS permissions.

NOTE: I would suggest trying this on a test share first. For example, create a folder such as C:\Test and then share it as you always do. In this example I will make the assumption that you want to share with Everyone and give them Full Control.

Right click on C:\Test within File Explorer and select Properties. Go to the Security tab. Click Edit. Click Add... Type everyone and then click on OK. Check the Full control box and click on OK, then OK again.

Try to connect to that share and see if you have better luck.

SoFine409 · Apr 7, 2023

hsehestedt said:
There is one item in particular that I did not see you address that has tripped me up before: NTFS permissions.

NOTE: I would suggest trying this on a test share first. For example, create a folder such as C:\Test and then share it as you always do. In this example I will make the assumption that you want to share with Everyone and give them Full Control.

Right click on C:\Test within File Explorer and select Properties. Go to the Security tab. Click Edit. Click Add... Type everyone and then click on OK. Check the Full control box and click on OK, then OK again.

Try to connect to that share and see if you have better luck.

Hi @hsehesedt sadly that didn't work either. The result was the same as when I tried to share an entire drive.

SoFine409 · Apr 7, 2023

akt196 said:
Win+R => services.msc
DNS Client - Automatic
Function Discovery Resource Publication- Automatic
Function Discovery Provider Host - Automatic
UPnP Device Host - Automatic
SSDP Discovery - Automatic
restart computer => check sharing

Start => Windows Defender Firewall => Allowed an app or feature through Windows Defender Firewall => File and Printer Sharing => check all boxes (activate)

Start => Windows Defender Firewall => Advanced settings => Indound rules =>File and Printer Sharing (all servicess -enabled,allow the connection)
Win+R => cmd (run as administrator) => sfc /scannow
Win+R => cmd (run as administrator) => DISM /ONLINE /CLEANUP-IMAGE /RESTOREHEALTH
restart computer => check sharing

Hi @akt196
The services were all set for manual start except for DNS Client which was Automatic. I reset all of them to Automatic but that didn't help. FYI, all my other PCs have then set for Manual as well and in my experience they work on either Manual or Automatic.

Windows Defender Firewall was set as you suggested so no changes were necessary.

SFC found no issues and DISM ran to conclusion without issues.

Still no joy.

But, it is interesting to note that the new PC will only show up under networks if the Function Discovery Resource Publication and
Function Discovery Provider Host services are stopped and restarted after each boot. Although the PC shows the username and password are no accepted. As I said before I've never seen anything like this before. I'm still stumped.

akt196 · Apr 7, 2023

SoFine409 said:
Hi @akt196
The services were all set for manual start except for DNS Client which was Automatic. I reset all of them to Automatic but that didn't help. FYI, all my other PCs have then set for Manual as well and in my experience they work on either Manual or Automatic.

Windows Defender Firewall was set as you suggested so no changes were necessary.

SFC found no issues and DISM ran to conclusion without issues.

Still no joy.

But, it is interesting to note that the new PC will only show up under networks if the Function Discovery Resource Publication and
Function Discovery Provider Host services are stopped and restarted after each boot. Although the PC shows the username and password are no accepted. As I said before I've never seen anything like this before. I'm still stumped.

Do you remember what kind of tweakers you used? if then do a revert, and if it doesn’t work out again, then it’s better to do a reset Windows

SoFine409 · Apr 7, 2023

akt196 said:
Do you remember what kind of tweakers you used? if then do a revert, and if it doesn’t work out again, then it’s better to do a reset Windows

No tweakers and it's a brand new PC with very little installed. That's why I'm totally puzzled.

OAT · Apr 7, 2023

Since you are using PRO, try a remote desktop connection.
If the password is not accepted, look for WinKey /Search Credential Manager and see what user logins are being used for your connections.
Duplicates with different credentials should be eliminated.
For the RDT, look for TERMSVR/<machineName>

SoFine409 · Apr 7, 2023

@OAT @hsehestedt @akt196 Thank you all for your help with this. I took a deep breath this morning along with a few cups of black coffee and I've figured out what the problem was. Since I set up all my PCs with the same username of Bob and the same password, I never need to enter a Username/Password for network sharing. That has always worked flawlessly.

However, this new PC was built for me by a system integrator and when it arrived, I notice that they didn't follow my instructions to create a used directory of Bob but instead used Robert.

So, rather than going through the long and error prone process of changing this, which I have done in the past, I simply changed the login name to Bob and left the use folder named Robert to hold my profile. Big mistake because that does not change the network username from Robert to Bob. So when I use Robert everything now works properly. What a dog and pony show this was.

Again thank you all for your help and I apologize for wasting your time.
Bob but sometimes Robert!

OAT · Apr 7, 2023

Glad it's solved Robert.

Solved Network Sharing Puzzle

Well-known member

My Computers

Active member

My Computer

Well-known member

My Computers

Well-known member

My Computers

Well-known member

My Computers

Active member

My Computer

Well-known member

My Computers

Pragmatic Member

My Computers

Well-known member

My Computers

Pragmatic Member

My Computers

Similar threads