Win 7 networking

[CRGibson]

I did a clean install of Win 7 HP on a new desktop PC. I have internet access and can see folders on my other Win 7 HP PC but can not access the files. Both PC's are set to share. When I go to network page I get a box that says "To view shared resources, first join the homegroup created by CHUCK (which is me). When I click the 'join now' button it asks me for the password I created when I created the homegroup. I don't recall doing this and when I click on "Where can I find the homegroup password?", a help windows opens and says (1)to 'Click to open HomeGroup.' and (2) Click View or print the homegroup password. Only problem is there is no view OR password.
I have run the troubleshooter and found that (1) the IPv6 is not working, however when I go to the ethernet card and click on properties it shows as installed and working. (2) In Device Manager I have a yellow ! on MS Teredo Tunneling Adapter (under network adapters). Under properties for this it states "This device is not started (Code 10).
Thanks for ANY help.

[DaveA]

I am finding the use of "HomeGroups" not very friendly.
I still just use Shares on a Workgroup, and have common users and passwords on all machines.
This way I can have my XP, Vista and Windows 7 all working.

[Medico]

When you go to home group in control panel, you can view the homegroup password. Do this for the PC #1 you set your homegroup up on. write down the password or if the PC's are close together leave this password open on PC #1. Then go to second PC and choose join homegroup name from PC #1. You will have to set the password the same as the first PC. Once you do both PC's are in the same homegroup. When you have a file or folder you want to share, simply right click and choose share with and set your shares. It really is simple.

[CRGibson]

I did as you suggested but after I enter the password from PC #1 I get a box that says that I must have IPv6 enabled to join.
This is my problem. IPv6 is enabled but Teredo Tunneling Adapter is not starting. How do I fix?
Thanks

[cstierhoff]

Try changing the encryption from 128 bit to 56 bit.
You will Find this in the Network Sharing Center in the Change Advanced Sharing Options.



Good Luck
C Stierhoff

[CRGibson]

Still no go. Still get the same "IPv6" needs to be installed.
Thanks for the suggestion.

[emiliaserv]

My password is a 10-digit mixture of letters and numbers that I distinctly recall was generated by the system during homegroup setup, you say you don't remember this happening, if a network is actually showing perhaps you could try uninstalling/deleting it and starting again from scratch.

Graham

[axiomatica]

Woody Leonhard's column "Caution: Bumps in the road to IPv6" (Windows Secrets, #281, 2011-03-17) includes an illustration that references "Teredo" in connection with IPv6. I've had the Teredo Tunneling Pseudo-Interface device disabled on my Windows 7 machine since shortly after setting it up. I also was getting the error "This device is not started (Code 10)," but disabling the device caused no apparent problems.

I had no idea the Teredo device was associated with IPv6 until I read Woody's column. I was finally prompted to investigate further. I did fix the problem (apparently), but not without going down a rabbit hole for a couple of hours. Fixing the problem is probably not for the faint of heart, since getting the Teredo device working led to a sequence of follow-on problems I had to resolve.

On the other hand, my local network is more complex than your average bear's, with a Windows 2008 domain controller and Linux server, among other network-connected devices. Nonetheless, you have been warned.

The first issue to consider in fixing the Teredo device start-up problem is whether you have ZoneAlarm installed (see below if you don't). It turns out that ZoneAlarm has an advanced setting that disables IPv6. You can refer to http://www.sevenforums.com/crashes-d...code-10-a.html, but I'm including the relevant information here (applies to ZoneAlarm Pro v. 9.3.014.000):

1. Open the ZoneAlarm GUI (double-click the ZoneAlarm icon in the task bar notification area).
2. On the left-hand side, select Firewall. Under Firewall, select Main.
3. On the lower-right side, click the Advanced button. An Advanced Settings dialog box will be displayed.
4. In the Network Settings group of the dialog box, ensure the Enable IPv6 networking check box is checked. Click OK to close the dialog box.
5. If you changed the setting, restart your computer. Use Device Manager after the restart to see whether the Teredo device warning is gone.

If you don't have ZoneAlarm, or if this procedure doesn't fix your problem, updating the driver has been reported to fix the problem (see http://social.msdn.microsoft.com/For...-21d0645169bd/). I didn't have to do this, so I can't comment on it. It is safer than the next option you have, however, so I recommend trying it before going on.

As a final possibility, there is a registry setting you can investigate. This is actually where I began my troubleshooting, before I discovered that ZoneAlarm's IPv6 setting will just overwrite any change that's made. The following information comes from http://answers.microsoft.com/en-us/w...3-c1f442fdf925. Please don't mess around with your registry unless you know exactly what you are doing.

1. Run RegEdit. I'm going to assume you know how, since you are heeding my caution about knowing what you are doing.
2. Find the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\servic es\TCPIP6\Parameters key.
3. Check the value of the DWORD value DisabledComponents. If the value is 0x000000FF, change it to 0x00000000. (Note: If it is neither of these values, you are on your own, because I have no idea what else it might affect.)
4. If you changed the setting, restart your computer. Use Device Manager after the restart to see whether the Teredo device warning is gone.

And now for the follow-on problems you might encounter.

Immediately after messing about with the registry and ZoneAlarm, I was dismayed to find that I was no longer able to access a shared folder that was hosted on my Windows Server 2008 domain controller. I have no idea why, but deleting the share and recreating it resulted in the share becoming visible again to the Windows 7 machine.

Now, however, the share was visible but I was being denied access to sub-folders within it. The permissions for the sub-folders were supposed to be inherited from the folder at the root of the shared folder tree. I tried re-applying the permissions, forcing them to be propagated down to all sub-folders. This didn't work, so I finally restarted the domain controller. Voila, things seem to be back to normal.

[axiomatica]

There is a point of clarification I should probably add concerning my previous post about the Teredo Tunneling Pseudo-Interface.

When the device is not working, it is listed under the Network adapters node in Device Manager. Once you get it working, however, it may appear to disappear altogether.

This is because it becomes a hidden device once it is working. In the View menu of Device Manager, select Show hidden devices. It will reappear, listed as the Microsoft Teredo Tunneling Adapter.

Why it changes name, I do not know. But searches on the Web seem to indicate that the two are indeed the same thing.

[rictom]

I have a win 7 laptop that occasionally is on my home network. Do I need to turn on ipv6 in zonealarm (i have the free version and the box to turn on ipv6 is there) even though I haven't had any issues and my home network is not as complicated as the original poster's (sorry forgot the username listed)

I do have the Teredo tunneling protocol listed under Network adapters in Device manager.

I and probably others could use some clarification about this Teredo and if it will affect every win 7 user at some point?

Great information by the way I'm sure it'll be valuable to many users.

Thanks

[TOF]

I am finding the use of "HomeGroups" not very friendly.
I still just use Shares on a Workgroup, and have common users and passwords on all machines.
This way I can have my XP, Vista and Windows 7 all working.

I absolutely agree with DaveA! Use normal networking/workgroup setups with wired or wireless and have fewer problems.

[axiomatica]

I have a win 7 laptop that occasionally is on my home network. Do I need to turn on ipv6 in zonealarm (i have the free version and the box to turn on ipv6 is there) even though I haven't had any issues and my home network is not as complicated as the original poster's (sorry forgot the username listed)

I do have the Teredo tunneling protocol listed under Network adapters in Device manager.

I and probably others could use some clarification about this Teredo and if it will affect every win 7 user at some point?

Great information by the way I'm sure it'll be valuable to many users.

Thanks

I'm not an expert on IPv6, so take anything I say with a grain of salt. Frankly, I recommend you look at Woody Leonhard's column that I mentioned (you can get to it from this thread: http://windowssecrets.com/forums/sho...ght=Woody+IPv6). (If you aren't a paid subscriber to Windows Secrets, shame on you.)

With that caveat out of the way, the simple answer to your question is a qualified "no." IPv6 is not widely in use and there is a chicken-and-egg problem that contributes to its slow adoption. By the time you absolutely must have a machine that supports IPv6, Windows 7 will probably be history. If you aren't actually having any problems that might be related to Home Groups, IPv6, etc. then don't worry about the Teredo driver.

[Dic]

So how does one set up Workgroup Sharing? Sounds like a good deal, but I can't find my way there.

All help appreciated.

[Medico]

So how does one set up Workgroup Sharing? Sounds like a good deal, but I can't find my way there.

All help appreciated.

Check out this article from Fred Langa on Win 7 workgroup settings