Consider the following scenario:

• On a computer that is running Windows Vista or Windows Server 2008, you add a shared printer.
• This shared printer is located on a print server that is running an earlier version of Windows, such as Windows Server 2003.
• The shared printer’s status is “Driver Update Needed.”
  Note: This status is displayed in the Status field in the Printers item in Control Panel.

In this scenario, the print server’s performance gradually decreases. Eventually, the print server constantly runs at 100-percent CPU utilization.

Consider the following scenario:

• You have a shared folder that is available offline.
• On a Windows Vista-based computer, in an Office application or in WordPad, you use the Open File dialog box to open an offline file that is in the shared folder.

In this scenario, the shared folder goes offline. After the shared folder goes offline, you cannot make the shared folder go online from Windows Explorer.

Consider the following scenario. You are running a Windows Vista-based computer. On this computer, you use Windows Explorer to rename a folder on a network share or in a redirected folder. In this scenario, the renamed folder disappears in Windows Explorer.

Additionally, the renamed folder reappears after you perform one of the following operations:

• You press F5 to update Windows Explorer.
• You close Windows Explorer, and then you reopen it.

On a Windows Vista-based computer, you open a remote shared folder in Windows Explorer that uses the Details view and for which the Preview Pane layout is enabled. When you try to open a Microsoft Office Excel 2007 Workbook from the remote shared folder, you may receive the following message:
File in Use file_name is locked for editing by user_name
However, in this case, no other user is using this document.

Note: This problem also occurs when you try to open other shared 2007 Office documents. Different users cannot exclusively edit such shared documents.

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.

Consider the following scenario:

• On a Windows Vista-based computer, you log on to a domain.
• You use a smart card certificate to establish a remote access connection.
• You try to connect the Windows Vista-based computer to a shared resource in a foreign domain by using the remote access connection.

In this scenario, Kerberos authentication that uses the Public Key Initialization (PKINIT) protocol in the foreign domain fails. For example, when you use the net use \\ComputerName\ShareName command to connect the computer to a shared resource in the foreign domain, you cannot make the connection.

Note: PKINIT is an Internet Engineering Task Force (IETF) Internet Draft for “Public Key Cryptography for Initial Authentication in Kerberos.” Windows Vista uses the PKINIT protocol when you use a smart card to perform an interactive logon.

Consider the following scenario. A shared printer is hosted on a Microsoft Windows Server 2003-based computer. On a Windows Vista-based client computer, you use the “Point and Print” feature to connect to this printer. In this scenario, the printer does not work correctly.

In Windows Vista, when you right-click a shared color printer and then click Properties, an access violation occurs in the Explorer.exe process.

When you try to install a shared printer when you have User Account Control (UAC) turned off in Windows Vista, you may receive an error message that resembles the following:

Connect to a Printer

Windows cannot connect to the printer.
The specified Print Monitor is unknown

This problem occurs after you click Install driver in the Printers dialog box. This problem may occur if the printer driver has a language monitor as part of the driver package.

You perform one of the following operations on a Windows Vista-based computer:

• Connect to a shared printer on the network, and then run the “Common Scenario Stress with IO” test in Driver Test Manager (DTM).
• Print to a shared printer on the network.
• Perform a power management operation. For example, you put the computer to sleep or into hibernation. Or, you wake the computer from sleep or from hibernation.

In this scenario, you receive a Stop error message that resembles the following:

*** STOP: 0×0000009F (parameter1, parameter2, parameter3, parameter4)
DRIVER_POWER_STATE_FAILURE