Homegroup

[tbernstein]

I have just upgraded a second machine to win7 on my little home network.
It immediately offered me the chance to start a homegroup. So I did.
But the machine I upgraded first can't join it. It says I have to install IPv6 first.
But IPv6 is running.
I can see shared files and folders across the network.

 

[torrentg]

Go to Network and Sharing Center. Click on local area connection, then click properties. Is there a check next to Internet Protocol Version 6 (TCP/IPv6)?

If not, put one there and click ok.

 

[tbernstein]

Yes maybe

The IPv6 is ticked. But I notice that in the "general" tab it says "no network connection" for IPv6.
And on the "advanced" section it has only IPv4 references.

 

[Hurdal]

i have the same problem with my win7x64. and also my network wont show under "My computer" - "network".

 

[djmorgan]

Turn off any antivirus software you have running before you try again, most AV programs have not been updated to allow for MS,s new network connection methods.
You may find that when you turn your AV back on you'll loose conectivity again.

 

[tbernstein]

It detected the other computer on the Homegroup. But still insists that IPv6 isn't enabled soit can't connect.
It also thinks that I have Comodo firewall running, which I don't! It's not even on my machine. I use Windows firewall!

 

[kegobeer]

Did you do an in-place upgrade, or did you do a clean install of 7? If you did an in-place upgrade, did you happen to have Comodo installed (or any other third party security suite)?

 

[tbernstein]

It was in-place upgrade - but Comodo wasn't on the system pior.It still isn't on the system.
I did have it,once. A while ago.
But not now.

I've searched the registry and can fnd no trace.
I've been through the computer, by searching and manually. There is no trace.
I use ccleaner and Glary Utilities.
It doesn't appear as a service.
It doesn't appear in any startup location.
I assume there's a binary that references it in some magical way.
And that still doesn't mean that that is what's casuing this problem.
i.e. that IPv6 is running and Windows doesn't believe that it is.

I have ad-aware and Avast installed. I treid disabling Avast, as noted already.
I'll try turning off Windows firewall, but I dont expect that to make any difference.

I'm so mystified.

 

[torrentg]

It was in-place upgrade - but Comodo wasn't on the system pior.It still isn't on the system.
I did have it,once. A while ago.
But not now.

I am a huge fan of upgrades but a system has to be in mint condition to begin with for it to be successful.

Best thing here in this case is a clean install right on top of where Windows is now. The installer will place everything currently there into a Windows.old folder at root, so you will not lose a single file.

Just do not format anything and you'll be fine.

 

[tbernstein]

Yes, I did think of that.
It's a cost benefit analysis.
Benefit:
I may be able to get the homegroup working, which won't give me a lot more than I already have through conventional networking. It'd be nice though.
Cost:
1.) I'd have to reinstall all the software, including MS Money, which would need a download of an essential patch, which I can't get cos MS don't support it anymore.
2.) My wife would kill me
3.) It still might not work
4.) It's much more satisfying to find a solution.

 

[torrentg]

Honestly, a solution may not happen easily for you. You have to have intricate knowledge of where installers place their files around the system, have to know how to scour the registry for obvious and not-so-obvious keys, go through the users folders making sure there are no signs, check the system32 folder....and after all that, Windows is still going to think you're using Comodo.

A user is your position only has 2 real choices.

Clean install or forget Homegroup and use classic networking, which is the "better way" anyhow.

 

[TheSchaft]

Honestly, a solution may not happen easily for you. You have to have intricate knowledge of where installers place their files around the system, have to know how to scour the registry for obvious and not-so-obvious keys, go through the users folders making sure there are no signs, check the system32 folder....and after all that, Windows is still going to think you're using Comodo.

A user is your position only has 2 real choices.

Clean install or forget Homegroup and use classic networking, which is the "better way" anyhow.

I'm afraid I have to agree with the clean install route, as much as it will make your life difficult. The fact that your system thinks it has Comodo installed and you cannot find out why is, I believe, indicative of deeper problems that cannot be cured by other than slicking the system and staring over (and not going with the Homegroup option.)

Try to back up all your current stuff, using something like GFI Backup - Free backup software for Windows - GFI Backup Home Edition to make the transition as painless as possible. (It does a great job, BTW.)

 

[tbernstein]

I must admit, the "quit while I'm ahead" option may be best.

 

[TheSchaft]

I must admit, the "quit while I'm ahead" option may be best.

Sometimes quitting is a viable option, I agree.

I would still encourage you to try GFI Backup - Free backup software for Windows - GFI Backup Home Edition - it can't hurt, and may save you some extra work.

 

[tbernstein]

SORTED!!!!!

I found a reference in the MS knowledge base.
You won't believe this.
You have to set the disabled items registry key to 0
But..... if it hasn't got one ( mine didn't) you have to create one first and then set it to zero!!!!!!

Or in Microsoft speak - if nothing is disabled everything is disabled unless you tell it that nothing is disabled.

In technical terms;
regedit
hkey-local machine\system\currentcontrolset\services\tcpip6\parameters
Then you have to set the DisabledComponents Dword to 0
And if there isn't a disabledcomponents dword you have to create one and then set it to zero???????

Which, since we users shouldn't be dragging our hands in the entrails of the registry, rather suggests a bug in the OS somewhere.
I'm fairly used to playing that game.
But the sort of ordinary user who actually needs the homegroups probably wouldn't want to try this.

 

[RandyD123]

As I've posted in a different thread, HOMEGROUP is ONLY for people who don't understand how sharing and how permissions work.

 

[tbernstein]

...In which case they'd have no chance of sorting out this problem.


Oh and in the nature of networks - you get a range of users, from savvy to newbie. Or parents and children. Some can sort permissions, some not. But in a home network or small office, all need to be able to do sharing as and when needed.