Samsung Galaxy S10+ | Samsung Galaxy Gear S3 Frontier | Samsung Galaxy Buds | Apple iPad 3 |
Vraag
Beste antwoord (via johanroelfs op 15-05-2016 18:29)
Ik had last van hetzelfde probleem, opgelost door te zoeken en uiteindelijk een map leeg te maken en de thuisgroep opnieuw aan te maken.
WIN 10 Homegroup issues
by Papa_Paul2 / August 3, 2015 2:06 PM PDT
In reply to: WIN 10 Homegroup issues
The issue for me is solved. Here are the steps I took, but I'm not sure they were necessary. I would try step 3 first and if that doesn't work, try 1 & 2 and then 3 again.
1) Deleted the idstore.sset file found in the \Windows\ServiceProfiles\LocalService\AppData\Roaming\PeerNetworking folder of your system drive (for example, drive C). It was really idstore.sst.
2) Went to services.msc and enabled (automatic):
"peer network grouping"
"peer network identity manager"
"homegroup listener"
"homegroup provider"
3) Steps 1 & 2 didn't seem to be working so I shut down all 4 PCs and went to bed. In the morning I only turned on my newest formerly WIN 8 laptop. I knew that this PC never hosted the "Ghost" HOMEGROUP. I opened HOMEGROUP and it allowed me to set up a new one and gave me a new password. I turned on the other 3 PCs and HOMEGROUP connected with the new PW. So I think the issue may be is that if the PC that created the "ghost" HOMEGROUP is powered up WIN 10 sees the "GHOST" as active and tries to connect to it.
succes.
WIN 10 Homegroup issues
by Papa_Paul2 / August 3, 2015 2:06 PM PDT
In reply to: WIN 10 Homegroup issues
The issue for me is solved. Here are the steps I took, but I'm not sure they were necessary. I would try step 3 first and if that doesn't work, try 1 & 2 and then 3 again.
1) Deleted the idstore.sset file found in the \Windows\ServiceProfiles\LocalService\AppData\Roaming\PeerNetworking folder of your system drive (for example, drive C). It was really idstore.sst.
2) Went to services.msc and enabled (automatic):
"peer network grouping"
"peer network identity manager"
"homegroup listener"
"homegroup provider"
3) Steps 1 & 2 didn't seem to be working so I shut down all 4 PCs and went to bed. In the morning I only turned on my newest formerly WIN 8 laptop. I knew that this PC never hosted the "Ghost" HOMEGROUP. I opened HOMEGROUP and it allowed me to set up a new one and gave me a new password. I turned on the other 3 PCs and HOMEGROUP connected with the new PW. So I think the issue may be is that if the PC that created the "ghost" HOMEGROUP is powered up WIN 10 sees the "GHOST" as active and tries to connect to it.
succes.
Alle reacties
Ik had last van hetzelfde probleem, opgelost door te zoeken en uiteindelijk een map leeg te maken en de thuisgroep opnieuw aan te maken.
WIN 10 Homegroup issues
by Papa_Paul2 / August 3, 2015 2:06 PM PDT
In reply to: WIN 10 Homegroup issues
The issue for me is solved. Here are the steps I took, but I'm not sure they were necessary. I would try step 3 first and if that doesn't work, try 1 & 2 and then 3 again.
1) Deleted the idstore.sset file found in the \Windows\ServiceProfiles\LocalService\AppData\Roaming\PeerNetworking folder of your system drive (for example, drive C). It was really idstore.sst.
2) Went to services.msc and enabled (automatic):
"peer network grouping"
"peer network identity manager"
"homegroup listener"
"homegroup provider"
3) Steps 1 & 2 didn't seem to be working so I shut down all 4 PCs and went to bed. In the morning I only turned on my newest formerly WIN 8 laptop. I knew that this PC never hosted the "Ghost" HOMEGROUP. I opened HOMEGROUP and it allowed me to set up a new one and gave me a new password. I turned on the other 3 PCs and HOMEGROUP connected with the new PW. So I think the issue may be is that if the PC that created the "ghost" HOMEGROUP is powered up WIN 10 sees the "GHOST" as active and tries to connect to it.
succes.
WIN 10 Homegroup issues
by Papa_Paul2 / August 3, 2015 2:06 PM PDT
In reply to: WIN 10 Homegroup issues
The issue for me is solved. Here are the steps I took, but I'm not sure they were necessary. I would try step 3 first and if that doesn't work, try 1 & 2 and then 3 again.
1) Deleted the idstore.sset file found in the \Windows\ServiceProfiles\LocalService\AppData\Roaming\PeerNetworking folder of your system drive (for example, drive C). It was really idstore.sst.
2) Went to services.msc and enabled (automatic):
"peer network grouping"
"peer network identity manager"
"homegroup listener"
"homegroup provider"
3) Steps 1 & 2 didn't seem to be working so I shut down all 4 PCs and went to bed. In the morning I only turned on my newest formerly WIN 8 laptop. I knew that this PC never hosted the "Ghost" HOMEGROUP. I opened HOMEGROUP and it allowed me to set up a new one and gave me a new password. I turned on the other 3 PCs and HOMEGROUP connected with the new PW. So I think the issue may be is that if the PC that created the "ghost" HOMEGROUP is powered up WIN 10 sees the "GHOST" as active and tries to connect to it.
succes.
Stap 1 en 2 werken voor mij. Bedankt voor de oplossing
Samsung Galaxy S10+ | Samsung Galaxy Gear S3 Frontier | Samsung Galaxy Buds | Apple iPad 3 |