Sign in
Microsoft.com
 
Windows Client TechCenter
 
 
 
Windows Client TechCenter > Windows 7 Forums > Windows 7 Networking > Problems Joining Home Group
Ask a questionAsk a question
Search Forums:
 

AnswerProblems Joining Home Group

  • Tuesday, November 03, 2009 5:59 PMmcdude Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    I have three machines running Windows 7 Ultimate X64. Two are desktops and one is a laptop. The laptop and one of the desktops uses a wireless connection to the network. I have been successful in joining the home group from each machine.

    It seems that one of the machines has become the "master" and the other "slaves". It the "master" is restarted, then all the rest must be restarted in order to join the home group. All shared folders are available, but when I try to join the home group, from a "slave", I get the message "No Home Group available". 

    Any suggestions to solve this so I don't have to restart each in a particular sequence? 
    meetoo
     

Answers

  • Friday, November 06, 2009 11:30 PMmcdude Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote
    I know there is no master/slave relationship between machines. I just used that as a method to describe the situation. Maybe it was a poor choice of words.

    I left the HomeGroup on each machine and started a new HomeGroup with a new password on my "office" computer . I then joined the HomeGroup on each of the other 2 machines. As a test, I rebooted the "office" machine and went to the other room and found that there were no other machines in the HomeGroup. I started the trouble shooter and it seemed to have found something because it rejoined the HomeGroup. I have since rebooted each machine several times without any problems.

    Thanks,
    Mike
    meetoo
     

All Replies

  • Wednesday, November 04, 2009 5:57 AMNovak WuMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

     

    Actually, there is no master or slave in HomeGroup. Each machine is the same. If one of HomeGroup machine is restarted, other machine should still be in the HomeGroup and need not restart to join the group.

     

    At this stage, it's highly recommended to leave the HomeGroup on each machine and then recreate a new HomeGroup. If certain machine cannot join HomeGroup, please perform the following steps to troubleshoot the issue.

     

    1. Click "Start", type "services.msc" (without quotation marks) in Search Bar and press Enter.

     

    Note: If you are prompted for an administrator password or confirmation, type your password, or click Continue.

     

    2. Right click the "Peer Networking Identity Manager" service and choose Properties.

     

    3. Please click Stop button to stop the service temporarily.

     

    4. Access the following folder:

     

    C:\Windows\ServiceProfiles\LocalService\AppData\Roaming\PeerNetworking

     

    5. Clear all the files and folders inside.

     

    6. Start the following service gain: Peer Networking Identity Manager

     

    7. Reboot the computer and you should be able to rejoin the HomeGroup.

     

    What's the result?

     

    Thanks,

    Novak

    • Unmarked As Answer bymcdude Saturday, November 07, 2009 3:57 PM
    • Marked As Answer bymcdude Friday, November 06, 2009 11:30 PM
    •  
     
  • Friday, November 06, 2009 11:30 PMmcdude Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote
    I know there is no master/slave relationship between machines. I just used that as a method to describe the situation. Maybe it was a poor choice of words.

    I left the HomeGroup on each machine and started a new HomeGroup with a new password on my "office" computer . I then joined the HomeGroup on each of the other 2 machines. As a test, I rebooted the "office" machine and went to the other room and found that there were no other machines in the HomeGroup. I started the trouble shooter and it seemed to have found something because it rejoined the HomeGroup. I have since rebooted each machine several times without any problems.

    Thanks,
    Mike
    meetoo