Consider the following scenario:

• The following policies are enabled on a domain controller that is running Windows Server 2003 in a domain:
  • Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\Microsoft network server: Digitally sign communications (always)
  • Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\Microsoft network server: Digitally sign communications (if client agrees)
• The following policies are enabled on a member computer that is running Windows Vista Service Pack 1 or Windows Server 2008 in the same domain:
  • Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\Microsoft network client: Digitally sign communications (always)
  • Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\Microsoft network client: Digitally sign communications (If server agrees)

In this scenario, Group Policy settings are not applied on the member computer. Additionally, the following event is logged in the System log on the member computer:

Date: Date
Event ID: 1058
Level: Error
Keywords:
User: UserSID
Computer: CompuerName
Description:
The processing of Group Policy failed. Windows attempted to read the file \\path\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following:
a) Name Resolution/Network Connectivity to the current domain controller.
b) File Replication Service Latency (a file created on another domain controller has not replicated to the current domain controller).
c) The Distributed File System (DFS) client has been disabled.

Note: This problem occurs only on member computers that are running Windows Server 2008 or Windows Vista Service Pack 1 (SP1). It does not occur on member computers that are running Windows Server 2003, Windows XP, or the release version of Windows Vista.

Consider the following scenario:

• On a computer that is running Windows Vista Service Pack 1 (SP1) or Windows Server 2008, you create a Server Message Block (SMB) share.
• After the share is not accessed for some time, you remove the share.

In this scenario, you cannot delete the folder that is used to back the share. Additionally, you receive an error message that resembles the following:

Folder In Use
The action can’t be completed because the folder is open in another program
Close the folder and try again.

In this case, you have to restart the computer. After that, you can delete the folder.

Consider the following scenario:

• In a network environment, you set up a Server Message Block (SMB) connection between two Windows Vista-based computers that use the SMB2 protocol.
• The SMB session requires more than one roundtrip.
• The connection is closed while Windows Vista is processing the response for the second roundtrip.

In this scenario, a handle leak may occur. Specifically, when you run the Net Session command, invalid session information is returned. This session information may indicate in the Opens column that this session has an invalid count.

After the issue occurs, you must restart the SMB service or the computer that is running this service.

Note: This issue also occurs in Windows Server 2008.

Server Message Block: An application-level network protocol mainly applied to shared access to files, printers, serial ports, and miscellaneous communications between nodes on a network.

You transfer a file between a Windows Vista-based client computer and a file server that is running a previous Windows operating system. Then, the Windows Vista-based client stops responding. This problem occurs if the following conditions are true:

• Windows Vista and the file server use the Server Message Block (SMB) 1.0 protocol to transfer the file.
• The network connection between the Windows Vista-based client computer and the file server is lost when you transfer the file. For example, the network cable is unplugged when you transfer the file.

Note: When you transfer a file between a Windows Vista-based client computer and a file server that is running a previous Windows operating system, Windows Vista uses the SMB 1.0 protocol to transfer files.

You cannot configure the maximum number of concurrent SMB requests that are sent to a Windows Vista-based file server.

When a Windows Vista-based computer is used as a file server, users access files by using long-term Server Message Block (SMB) requests. By default, only 10 SMB requests can be sent to the server at the same time. All other SMB requests are not answered. Therefore, the user of a client computer may receive an error message when the user tries to access files by using long-term SMB requests.

Note: Unlike typical SMB requests, a long-term SMB request remains open until it is answered by the server. A typical long-term SMB request is the NotifyChange SMB request (NT_TRANSACT_NOTIFY_CHANGE).

You cannot access a shared network resource that is hosted by a Windows Vista-based computer if one of the following conditions is true:

• The size of the server message block (SMB) request packet exceeds the maximum transmission unit (MTU) size of the requesting device.
• The size of the SMB request packet exceeds the MTU size of the router that connects the requesting device with the server.

When you establish a Remote Access Service (RAS) connection to a corporate network from a computer that is running Windows Vista, you cannot access Server Message Block (SMB) shares. However, if you use the ping command to test Internet connectivity, the ping test is successful.

You create, delete, copy, move, or change a file that is located on a SAMBA-based, network-attached storage device. However, the change does not appear in Windows Photo Gallery on a Windows Vista-based computer. For example, if you delete a file, that file is still displayed.

This problem occurs when the network-attached storage device is a monitored server message block (SMB) share that is in Windows Photo Gallery.