How To Repair Peer Name Resolution Protocol
Recently decided to restart my HomeGroup on my Windows 7 machine/network after moving and discovered something had mysteriously broken during travel to the new place. What occured was a total lockout of HomeGroup settings with no viable means of fixing or even leaving the old HomeGroup and its settings.
Symptoms:
HomeGroup was not working correctly.
Unable to leave the HomeGroup or run diagnostics with a happy ending (can not fix).
Unable to make permanent changes to HomeGroup, such as password changes.
Background Info:
This particular case was related to the Repair Peer Name Resolution Protocol in Windows 7, however there maybe many other reasons why HomeGroup doesn't work. Which is why this is a Peer Name Resolution Protocol How-To, not a HomeGroup fix it all.
Now, this is a middle child service.
HomeGroup is dependent on 3 services to run correctly:
1.) Peer Networking Identity Manager
2.) Peer Name Resolution Protocol
3.) Peer Networking Grouping
Pretty much what happens is there is a handshake error and you become locked out of either the Peer Name Resolution Protocol Service, or the ability to edit anything with your HomeGroup. It seems to be either a corrupted configuration or another Windows method of tamper prevention/security.
Solution:
Restarting the services manually may work. This usually does not.
This corrupted configuration file needs to be deleted:
C:\Windows\ServiceProfiles\LocalService\AppData\Roaming\PeerNetworking\idstore.sst
Infact, I have deleted every file in here with no remorse. After this, you should require a simple reboot, AND, run HomeGroup diagnostics, go through to the end and "Refresh HomeGroup."
Solution Addition:
IF you are like me and tried manually starting the services as a different account etc, i.e. you probably changed the default settings for the account user info, you will get this error: 0x806320a1
There is not a lot of information out there for this specifically, but the solution is really simple.
You want to go back to each service and change the Log On As options and log on user to "LOCAL SERVICE" (no quotes) and then edit the password so its blank. You will want to do this on ALL 3 services (don't forget to apply before closing). Then you should start them in the order 1,2,3 above. At his point you should be good to go, to run the HomeGroup self-diagnostics and then choose Refresh HomeGroup.
Symptoms:
HomeGroup was not working correctly.
Unable to leave the HomeGroup or run diagnostics with a happy ending (can not fix).
Unable to make permanent changes to HomeGroup, such as password changes.
Background Info:
This particular case was related to the Repair Peer Name Resolution Protocol in Windows 7, however there maybe many other reasons why HomeGroup doesn't work. Which is why this is a Peer Name Resolution Protocol How-To, not a HomeGroup fix it all.
Now, this is a middle child service.
HomeGroup is dependent on 3 services to run correctly:
1.) Peer Networking Identity Manager
2.) Peer Name Resolution Protocol
3.) Peer Networking Grouping
Pretty much what happens is there is a handshake error and you become locked out of either the Peer Name Resolution Protocol Service, or the ability to edit anything with your HomeGroup. It seems to be either a corrupted configuration or another Windows method of tamper prevention/security.
Solution:
Restarting the services manually may work. This usually does not.
This corrupted configuration file needs to be deleted:
C:\Windows\ServiceProfiles\LocalService\AppData\Roaming\PeerNetworking\idstore.sst
Infact, I have deleted every file in here with no remorse. After this, you should require a simple reboot, AND, run HomeGroup diagnostics, go through to the end and "Refresh HomeGroup."
Solution Addition:
IF you are like me and tried manually starting the services as a different account etc, i.e. you probably changed the default settings for the account user info, you will get this error: 0x806320a1
There is not a lot of information out there for this specifically, but the solution is really simple.
You want to go back to each service and change the Log On As options and log on user to "LOCAL SERVICE" (no quotes) and then edit the password so its blank. You will want to do this on ALL 3 services (don't forget to apply before closing). Then you should start them in the order 1,2,3 above. At his point you should be good to go, to run the HomeGroup self-diagnostics and then choose Refresh HomeGroup.
Comments (0)