Can't start Peer Name Resolution Protocol

WORKED.

1.unshare everything you have shared.

2.delete "idstore.sst" and "idstore.sst.new"

3.rename "a5691ef79c937250b91a4fde7c86f5db.sst.new" TO "a5691ef79c937250b91a4fde7c86f5db.sst.new.L"

4.disable you network card.

5. restart your PC.

6. try leaving homegroup NOW.

7. DONE........ :)

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, that was a mistake, you will get this error: 0x806320a1

There is not a lot of information out there for this specifically, but the solution is really simple.

1) Delete idstore.sst

2) 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.

I know this is an older forum posting but it worked out well for me. I tried all the fixes suggested here except the deleting or renaming MachineKeys file as I was unsure what that would do and no information was given.

The post preceding mine worked perfectly, I was now able to start all the services and leave the homegroup, for which I don''t have much use for right now.

Thank you all

Yes! For all which can not start Peer Name Resolution Protocol - see Eugenecist advice. Check carefully Log On tab. Make sure all 3 services (Peer ...) are set to Local Service. Enter your Log on Windows password and... voilà! You can start services.
(Btw, there is an advice here that these services should run in Local System Account, not as Local Service. I do not know the difference, in case of future problems will investigate more.)
Restart computer. Home group is here and errors in the event log gone away.
But why this happened, as Home Group worked yesterday I do not know also.

I joined this forum just to say thank you!! This helped me as well. I shared it (with a link to here) on techspot, where I had first asked for help.

I have been frustrated with this error for several days, and have researched many threads in this forum and others. I tried the delete *.sst files and that did not work. I tried resetting the login name and that did not work. Then I found a reference to the page link below -- did it (changing permissions on RSA files) and have been without the error for 8 hours now, instead of getting it every 10 or 15 minutes.

Event ID 102 ? PNRP Protocol

And just to give credit -- this was in a post by Streetwolf
https://www.sevenforums.com/network-s...-protocol.html

streetwolf said:

Event ID 102 — PNRP Protocol

I tried what they outlined (it's for Vista) but to no avail. I have no idea what the connection is between RSA and P2P.

I want to thank you directly for the reference to that article. It led me to the fix for me. What it took was the resetting of permissions on LOCAL USER as was suggested there. I'd tried all of the other things in this thread and other threads without success.

These error messages have now gone away.

streetwolf said:

researched the problem and found the solution. A file was corrupted and deleting it got the pnrp service running. The file was recreated correctly when the pnrp service started up. Here's the file for future reference:

"c:\windows\serviceprofiles\localservice\appdata\roaming\peernetworking\idstore.sst"

this worked like a charm.

Thanks thanks thanks:d:d:d:d:d:d:d

Sorry to necro this post. I have the same problems, but..
I can't find \PeerNetworking\idstore.sst
My files go to Roaming, but that is as far as I can go.