I have removed KB2535512 and KB2536276 from the Win2k3 server and restarted it. Now I am able to open the folders on the share, but most subfolders can be opened only at second try - but never ever needs more try than two.

Windows 7 SP1 using a share on a Windows Server 2003 Enterprise SP2 stopped working. After connecting to the share I am unable to open some folders, I can open some folders once out of about ten attempts. Message is Unable to access drive:\path\file. Access Denied. I have tried to connect to the share by server name and by IP address, too. Total Commander is able to open the folders and launch the associated programs. Microsoft Word seems to be able to save back to the original file, Save as works about once out of two attempts. I have tried to reproduce the problem on three W7 clients, all fails. No events in the server security log. Windows XP SP3 clients work flawlessly. I have created a new folder on the server, shared it, results are the same. On the server I have found ambiguous NTFS access rights, one folder showed an user as inherited but no one folder up to the root had the user specified. Any ideas how to get the W7 Explorer shell to work again with our shares?

Hi, It is a networking issue between Windows 7 and Windows Server 2003. You can refer to the following method to troubleshoot the issue. 1. Update the network adapter driver from manufacture's site. 2. Disable security software or firewall on both side 3. Enable NetBIOS over TCP/IP a) Go to "Control Panel -> Network and Internet ->Network Connections". b) Right-Click on the connection and choose Properties. c) Click "Internet Protocol (TCP/IP) Version 4" in the list. d) Click Properties, and then click Advanced. e) On the Advanced TCP/IP settings windows, go to "WINS" tab. f) Under NetBIOS setting, click "Enable NetBIOS over TCP/IP", and then click OK. 4. Navigate to Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\Network security: LAN Manager authentication level change to "Send LM & NTLM - use NTLMv2 session security if negotiated". If the issue persists, I suggest checking the issue from Server side. Windows Server Forum http://social.technet.microsoft.com/Forums/en-US/category/windowsserver Best Regards, Niki Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

I have followed the suggested steps, it seems that our antivirus software caused the problem.

Hi, Glad to hear it works. Thanks for sharing. Best Regards, Niki Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.