Homegroup doesn't show up until after log-in at server
Hi, Please try to ping the main server when the issue reoccur. I suspect this issue may be cuased by the ethernet card driver is not fully compatible with Windows 7 so that this happened.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
March 25th, 2011 12:26pm

Pardon me Joke Chou but somehow I don't believe that. That sounds more like a typical Microsoft answer. There are many people experiencing similar kinds of issues with different hardware. Now when W7 installs you get a truckload of WHQL compliant drivers that installs automatically. These are provided by MS. Now you wouldn't expect that all people having all these similar kinds of problems, when it comes to networking, all have partially compatible drivers to blame? You have to try harder to convince me...I'm sorry but thats my opinion. Don't get me wrong Windows 7 is a dream come true compared to Vista and a step forward from XP...so kudos for that. :-)
Free Windows Admin Tool Kit Click here and download it now
March 25th, 2011 6:32pm

Drat, this vicious circle again. I spend a nice chunk of change on some product and get caught in this vicious circle between the software and hardware people both pointing at each other and nothing gets fixed. I can tell you that I have updated the MB bios with latest update which were specificially designed to handle the Windows 7 OS. Granted there's always the chance some programmer didn't test the programming all the configuration options to verify the new values worked. Prior to logging in, I am able to see and access all the shared drives and can log-in remotely. The only feature that does not function is the Homegroup. It is for that reason I feel the issue is "service" level related rather than driver related. And if it were a driver issue, wouldn't it just not communicate at all rather than waiting until after a log-in? After I log-off the PC, the homegroup continues to function correctly, it's only on power up.
March 26th, 2011 5:21pm

Hi, OK, check the full services startup type (HomeGroup Listener, HomeGroup Provider,Function Discovery Provider Host, function Discovery resource Publication) in the Services Manager, If they start up manully. Please change the type to Automatic for a test. In addtion, please notify the Dependencies of these services Hope this helps.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
March 30th, 2011 11:00am

I have a dedicated PC acting as a file server for my home network and is that host for the Homegroup. For some reason the Homegroup does not show up on the network until I actually log-in on that specific PC and then all is well until power up/reboot is required again. So, in the event of a power loss and my PC restarts automatically on power restore, everyone has to wait until someone logs into the main server before access is available again. How can this be corrected so that the Homegroup is launched and available on power up of the system?
March 30th, 2011 4:14pm

So is this like a trouble ticket area or just a forum for people to share what they've figured out on their own?
Free Windows Admin Tool Kit Click here and download it now
March 30th, 2011 5:16pm

That did it, thanks for the assist.
March 31st, 2011 9:41pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics