Here is the exact solution to your problem:
This is caused by an issue with Windows XP Professional x64. This issue does not occur with 32-bit versions of Windows XP, or with newer releases of Windows.
Access the affected share in a persistent way using the name of the Windows Storage Server 2008 system. For example, you could access the share by using one of the following two methods:
Type net use * \\server-name\share /persistent:yes in a Command Prompt window.
Navigate to \\server-name\share in Explorer and keep the Explorer window open.
While still persistently accessing the share (from step 1), access the share again using the IP address of the Windows Storage Server 2008 system. You can determine the IP address of the Windows Storage Server 2008 system by using the command ping server-name from a Command Prompt window. When you access the share the second time, it can be in a persistent or non-persistent way. For example, assuming the Windows Storage Server 2008 system has an IP address of 192.168.1.1, you could access the share by using one of the following three methods:
Type dir \\192.168.1.1\share in a Command Prompt window (non-persistent).
Navigate to \\192.168.1.1\share in Explorer and keep the Explorer window open (persistent).
Type net use * \\192.168.1.1\share in a Command Prompt window (persistent).
All folders and subfolders in the share will be visible until the share is no longer being accessed (the system is rebooted, all Explorer windows are closed, the share is unmapped, etc.). Once the share is no longer being accessed, the issue reappears.
You can also reverse steps 1 and 2 above, such that you first access the share using its IP address, and then access the share using the server name. You just need to ensure that you access the share once using one method (i.e. IP address or server name), and once using the other.
The above steps can also be adapted for the second scenario in the Symptoms section involving 14-36 files within a folder.
the link-> http://support.microsoft.com/kb/2004445
