Excel documents on a network share is opening slow and has green ribbon in the address bar

[Laalamani]

We are running a Windows 2003 server in our office on which all the documents are stored. To access these documents, we have made the drive shared. We are also having a Windows 7 client which is mapping to this drive. Now coming to the point, the drive is accessible and we are able to use almost every type of the documents except Excel. It takes a very long time to open the Excel worksheet which is unacceptable for any office. We can also see green ribbon progress bar on the Explorer window. If by chance it gets open then it appears to be Read-Only and no one is allowed to edit it. Is this problem of the setup or something else?

[Connect_Me]

1. Go to Start, Run, type Regedit, and then press Enter.
2. Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MrxSmb\Parameters
3. Select Edit, click New, and then DWORD value.
4. Type InfoCacheLevel to replace New Value #1, and then press ENTER.
5. Click the InfoCacheLevel DWORD value in the right pane, click Edit, and then click Modify.
6. Under Value data, select hexadecimal and type 10, and then click OK.
7. Close Windows Registry Editor.

[Laalamani]

Ok but there is still some problem. Whenever I open any Excel file, this time I don't see any green ribbon on the address bar and no Read-Only message, but still if I modify it and want to save it, it gives me Save as option instead of saving it directly on the network drive. What could be the reason for this?

[HiSpeed]

In Internet Explorer, go to Tools, Internet Options, Connections and then LAN settings. Under Automatic configuration, uncheck "Automatically detect setting". If it still persists then change the default authentication level to see if it helps. The one that you have to change is Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\Network security: LAN Manager authentication level.

[Amie]

This issue may occur if any one of the following conditions is true:

- There is an issue with negotiating SMB signing from a client that is running Microsoft Windows XP (SP1) to a Windows 2000-based server that requires SMB signing.
- Another process has the file open and locked.