You use the Intel Pro/Wireless 3945ABG or Intel Wireless WiFi Link 4965AGN wireless local area network (WLAN) device on a Windows Vista-based computer (computer A) to establish a computer-to-computer (ad hoc) network that has WPA2 specified. You have a Windows Vista-based computer (computer B) that also has a wireless adapter installed. When you try to connect to the ad hoc connection from computer B, you may receive the following error message:

Windows cannot connect to Network Name

Note: Network Name represents the name of the ad hoc connection.

Consider the following scenario:

• You are using a Windows Vista-based computer that has two network adapters.
• Only one of the network adapters is connected.
• You do one of the following:
  • You set up Windows Media Player 11 by using the Welcome to Windows Media Player 11 for Vista Wizard, and you select the Express Settings (recommended) setting.
  • You install third-party software, such as a CD burning program or a DVD burning program, or you install a program that plays DVDs.

In this scenario, the network adapter that is connected appears to be disconnected when you view the connection icon in the Manage Network Connections window. The connection status is updated correctly. However, the connection icon incorrectly displays a red “X.” This behavior does not affect actual connectivity.

On a network, you deploy a Network Access Protection (NAP) architecture. When you connect to this network from a Windows Vista-based client computer, you can access the network resource correctly. However, after you run the gpupdate /force command to reapply the Group Policy settings, the client computer may lose network connectivity.

This issue occurs when the following conditions are true:

• Both IPsec policy and connection security rules are configured for NAP architecture.
• The value of the IKEFlags registry entry is set to 1C in hexadecimal.
  Note: This registry entry is located under the following registry subkey:

  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PolicyAgent\Oakley\

On a Windows Vista-based computer, you try to view the list of computers and of shared resources on the network by using one of the following methods:

• Run the NET VIEW command to show the list of the computers and the shared resources.
• View the computers and the shared resources in Windows Explorer.

However, you cannot obtain the list of computers and of shared resources.

For example, you run the NET VIEW command to view the network resources. Then, you receive following error message:

An internal Windows error occurred.
More help is available by typing NET HELPMSG 2140.

This problem occurs if the network has lots of computers in the browse list.

On a computer that is running Windows Vista, you try to use the Verizon speed optimizer tool to optimize network performance. When you do this, you may notice that the Windows Vista-based computer does not achieve the Internet connection speed improvement that is achieved in Windows XP. Therefore, you cannot use Verizon FiOS products at their full speed.

• Colasoft Capsa Now Supports Windows Vista x64 Edition
  Version 6.6 of the network analysis tool now supports both Vista 32-bit and 64-bit.
  (tags: 64-bit Network Software Compatibility )
• Vista Themes - Free Windows Vista Themes
  A site based around free Vista themes, wallpapers, icons and more.
  (tags: Wallpaper Screensaver Icon )

Keep reading →

Version 6.6 of the network analysis tool now supports both Vista 32-bit and 64-bit. Keep reading →

• Vista Hands On #19: Get one-click access to Vista network properties
  Ed Bott gives a tip that will save some time for those that need to change their network settings often.
  (tags: Network Tips )

Ed Bott gives a tip that will save some time for those that need to change their network settings often. Keep reading →

When using a Broadcom Wireless network adapter in Windows Vista, you may experience latency every 30/40 seconds. You can verify latency by using the PING -t command. Every 30/40 seconds, you will see a packet whose response time is around 1000ms.

If you use the same adapter in Windows XP, this issue does not occur.