setup homegroup Windows 7 fails

[kefegg]

Hi guys,

I read many things on different websites, even threads on this forum about Windows 7 homegroups.
Well, whatever I do, it doesn't work here.
I have 2 PC's running Windows 7. One is wired and the other is wireless (belkin surf&share n300) both connected to a Motorola SVG1501E (DOCSIS)modem.

All settings are set like described in most descriptions. If I click my computer, go to homegroup: nothing show up, just a message that there are no homegroupcomputers available.

What's the possible cause for this problem?

In NETWORK I do see the other PC and I do have access to a few folders but not to all I setup for sharing.

Anyone?


PS, the wireless PC, if possible, should not have access to internet, just wireless connection for my home network. (like server)

 

[JackMDS]

Maybe this can Help.

Homegroup-networking-the-easy-way - http://windows.microsoft.com/en-us/windows7/help/home-sweet-homegroup-networking-the-easy-way

HomeGroup-recommended-links - http://windows.microsoft.com/en-US/windows7/HomeGroup-recommended-links

HomeGroup-frequently-asked-questions - http://windows.microsoft.com/en-US/windows7/HomeGroup-frequently-asked-questions

Why can't I create a homegroup? - http://windows.microsoft.com/en-US/windows7/Why-cant-I-create-a-homegroup

Change-a-homegroup-password - http://windows.microsoft.com/en-us/windows7/Change-a-homegroup-password

How to leave a homegroup - http://windows.microsoft.com/en-US/windows7/Leave-a-homegroup

To enable/disable and fix IPv6 components - http://support.microsoft.com/kb/929852

-------------------------------------
Otherwise, inclusive Post about other options of File Sharing in Win 7 and other versions of Windows.
http://social.answers.microsoft.com...k/thread/68d10f8c-2800-4e10-9cc1-9bcb44597d2b

 

[paperfist]

What's the need to disable IPv6 for?

 

[imagoon]

What's the need to disable IPv6 for?

For some reason a lot of people think it makes Windows faster / more stable / whatever.

 

[paperfist]

For some reason a lot of people think it makes Windows faster / more stable / whatever.

That's interesting. I heard about it in the theory that disabling it on a netbook makes Firefox faster. Didn't do anything for me in that realm and using it on Win7 in a domain environment gave me nothing but headaches.

 

[JackMDS]

Yeah, I am sure that many of the people that get better networking because they disable IPv6 have sighted Yeti too.

In any case HomeGroup is based on IPv6 and will not work without it.

 

[imagoon]

That's interesting. I heard about it in the theory that disabling it on a netbook makes Firefox faster. Didn't do anything for me in that realm and using it on Win7 in a domain environment gave me nothing but headaches.

Not to be rude but from the tons of posts you have had about your environment I begin to wonder what is actually wrong. I mean when I got Windows 7, it installed and joined with out a problem at all in the "windows domain" portion of it. I mean I had a couple app problems but the pure "join to my Win2003 domain" was flawless. I never disabled ipv6, no issues. Windows 7 machines on the same hardware were booting and were usable faster than XP etc. You seem to be having a ton of problems. I think that is generally what the issues have been. Sometimes we all inherit a system that was never set up correctly, or the settings have been hacked on for some reason (or no reason at all) etc.

I do 'blame MS' to an extent, they have made really simple to "install AD" (insert other services here) but they don't do a great job telling people how to properly configure them and how to truly make them work. When they do they are buried in this 850 page document.

 

[paperfist]

Not to be rude but from the tons of posts you have had about your environment I begin to wonder what is actually wrong. I mean when I got Windows 7, it installed and joined with out a problem at all in the "windows domain" portion of it. I mean I had a couple app problems but the pure "join to my Win2003 domain" was flawless. I never disabled ipv6, no issues. Windows 7 machines on the same hardware were booting and were usable faster than XP etc. You seem to be having a ton of problems. I think that is generally what the issues have been. Sometimes we all inherit a system that was never set up correctly, or the settings have been hacked on for some reason (or no reason at all) etc.

I do 'blame MS' to an extent, they have made really simple to "install AD" (insert other services here) but they don't do a great job telling people how to properly configure them and how to truly make them work. When they do they are buried in this 850 page document.

It's okay I freely admit to being a networking noob, but I'm trying to learn. I wish I had the knowledge you and others here have, but it ain't going to happen overnight. I don't think 4 posts qualify as a ton though

I've only had one problem with one Win7 machine not connecting. The others connected fine without changing a thing. So as a noob I had to try different thinks like disabling ipv6 because it related to my issue from what I read on the net. It didn't work and created more problems so now I have to backtrack and resolve those issues. I don't have a test environment to run anything on, everything is live and without much networking experience I'm going to make mistakes, maybe tons. I do greatly appreciate the help I've gotten from this forum as it's been a life saver in some cases.

 

[imagoon]

It's okay I freely admit to being a networking noob, but I'm trying to learn. I wish I had the knowledge you and others here have, but it ain't going to happen overnight. I don't think 4 posts qualify as a ton though

I've only had one problem with one Win7 machine not connecting. The others connected fine without changing a thing. So as a noob I had to try different thinks like disabling ipv6 because it related to my issue from what I read on the net. It didn't work and created more problems so now I have to backtrack and resolve those issues. I don't have a test environment to run anything on, everything is live and without much networking experience I'm going to make mistakes, maybe tons. I do greatly appreciate the help I've gotten from this forum as it's been a life saver in some cases.

Don't worry I don't hold that against you. We were all there at one point. It sounded like you had inherited a mess from those posts.

--Edit--

If it gives you a reference.... I inherited years ago an NT4 network about 6 years ago... or well how about a disconnected nt4 / 2000 network. The solution to make everything work was "don't change your passwords." There were no trusts between the 2000 side that was a single DC and the NT4 side which had multiple NT4 servers. I spent the first few months upgrading nt4 to 2003, and joining the 2000 domain server as a member server. The odd ball 2000 network basically died and was merged in to the 2003 network. All of the 95 / 98 machines were retired or upgraded to 2000 / XP. The network had ISP DNS in the secondaries, invalid DHCP information etc. I had a learning curve there myself as I had done most of this work in theory (at that time most of my skill was in NT4 / 2 domain controller, single location AD setups not WAN distributed systems)

 

[paperfist]

Don't worry I don't hold that against you. We were all there at one point. It sounded like you had inherited a mess from those posts.

--Edit--

If it gives you a reference.... I inherited years ago an NT4 network about 6 years ago... or well how about a disconnected nt4 / 2000 network. The solution to make everything work was "don't change your passwords." There were no trusts between the 2000 side that was a single DC and the NT4 side which had multiple NT4 servers. I spent the first few months upgrading nt4 to 2003, and joining the 2000 domain server as a member server. The odd ball 2000 network basically died and was merged in to the 2003 network. All of the 95 / 98 machines were retired or upgraded to 2000 / XP. The network had ISP DNS in the secondaries, invalid DHCP information etc. I had a learning curve there myself as I had done most of this work in theory (at that time most of my skill was in NT4 / 2 domain controller, single location AD setups not WAN distributed systems)

Whoa that's a steep hill to climb, glad you were able to figure things out. Did the previous IT guy get fired for leaving things in such a mess?

My situation isn't quite that dramatic, but it was a mess none the less. I took over a year and a half ago when their Server2003 crashed and no one knew the password or how anything was setup. All they knew was they needed their data back. So I spent quite a few weeks trying to get the server back up, rebuilding the RAID and getting people connected again.

 

[imagoon]

Whoa that's a steep hill to climb, glad you were able to figure things out. Did the previous IT guy get fired for leaving things in such a mess?

My situation isn't quite that dramatic, but it was a mess none the less. I took over a year and a half ago when their Server2003 crashed and no one knew the password or how anything was setup. All they knew was they needed their data back. So I spent quite a few weeks trying to get the server back up, rebuilding the RAID and getting people connected again.

No he left of his own accord. It was not entirely his fault because there was no funding and there was some... "stress" between him and executive management. He also admitted to being a Novell guy.

 

[kefegg]

Well, I actually tried everything described above but still no homegroup. I guess I keep it with just 1 shared folder or sharing in Ubuntu (networkspeed is lower though).
Maybe one day I find what is wrong but for now it has been enough.
It eats time ;-)


But I appreciate all the help here.
Thanks.

Sent from my HTC Desire using Tapatalk