Win 7 Network Map blocked on 32 bit Pro

Does anyone know why one [COLOR=blue !important][COLOR=blue !important]laptop[/COLOR][/COLOR] cannot be placed in the Win 7 network map? The troubled machine is running Win 7 Pro, 32 bit, and has the Link Layer Topology Discovery (LLTD) enabled in the wireless adapter.

View from [COLOR=blue !important][COLOR=blue !important]Asus[/COLOR][/COLOR] P8P67 running Win 7 Ultimate 64 Bit
http://i26.photobucket.com/albums/c1...ps52e22107.jpg

Here is the view from Dell 17R wireless Laptop running Win 7 Home Premium 64 bit
http://i26.photobucket.com/albums/c1...ps16b0d367.jpg

And last here is the view from the problem PC a Dell 1501 wireless laptop running Win 7 Pro 32 bit - NOTE BIG ? IN MAP, PC name is 'KATHIEW7LAPTOP'
http://i26.photobucket.com/albums/c1...ps6970e5bc.jpg

I have home network setup and can see the shared folders from each to the other. I do not share printers because my printers are all networked through the router. The P4S8X-X shown is an old Win XP machine that I loaded the LLTD (Link Layer Topology Discovery and installed through a very complicated procedure in the CMD window. All machines are running AVAST anti-virus.

It is not a big deal that this network map will not work, but a irritant that I have something setup differently on the 32 bit laptop than I don on the 64 bit laptop. I sat the two PCs next to each other and checked all the settings in the Control Panel Network Setup and cannot find the difference. The firewall setting are all identical, although I did not go through the extensive list of outbound and inbound rules. The view on the problem PC shows a big question mark between the Dell 1501 and the router and I have no clue what it is. It is connected wirelessly just like the other laptop, which shows up just fine. COULD IT BE THE 32 BIT O/S?

Do you have IPv6 enabled on the troubled Win 7 machine? Maybe try disabling that and rebooting. See if that helps.

Yesiree - that fixed it




Will there come a time in the near future when we all will have to go to IPv6?

I don't recommend disabling IPv6 for any reason.

The Argument against Disabling IPv6
It is unfortunate that some organizations disable IPv6 on their computers running Windows Vista or Windows Server 2008, where it is installed and enabled by default. Many disable IPv6-based on the assumption that they are not running any applications or services that use it. Others might disable it because of a misperception that having both IPv4 and IPv6 enabled effectively doubles their DNS and Web traffic. This is not true.
From Microsoft's perspective, IPv6 is a mandatory part of the Windows operating system and it is enabled and included in standard Windows service and application testing during the operating system development process. Because Windows was designed specifically with IPv6 present, Microsoft does not perform any testing to determine the effects of disabling IPv6. If IPv6 is disabled on Windows Vista, Windows Server 2008, or later versions, some components will not function. Moreover, applications that you might not think are using IPv6—such as Remote Assistance, HomeGroup, DirectAccess, and Windows Mail—could be.
Therefore, Microsoft recommends that you leave IPv6 enabled, even if you do not have an IPv6-enabled network, either native or tunneled. By leaving IPv6 enabled, you do not disable IPv6-only applications and services (for example, HomeGroup in Windows 7 and DirectAccess in Windows 7 and Windows Server 2008 R2 are IPv6-only) and your hosts can take advantage of IPv6-enhanced connectivity.

Read more. http://technet.microsoft.com/en-us/m....cableguy.aspx

Most likely your Anti Virus software is causing this problem. :)