Reply to thread

Message

<blockquote data-quote="FantaRulez" data-source="post: 506037" data-attributes="member: 51267">I don't know if you're still interested in a solution, but I think I have one. I was having the same problems with my central database, delay write failures and a corrupted database after a time. I've made two changes to my setup, I don't know which one was the actual solution or maybe the combination of the two was the trick.First thing I did was to check if the server used the same MTU size as the client. Well, it didn't so I changed the MTU on the client:System Key: [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\[Adapter ID]]Value Name: MTUData Type: REG_DWORD (DWORD Value)Value Data: Default = 0xffffffffCreate a new DWORD value, or modify the existing value, called &quot;MTU&quot; and set it to equal the required MTU size in decimal. The second thing I did, and then the problem finally went away, was to disable opportunistic locking on the client:<a href="http://support.microsoft.com/kb/296264:" target="_blank">http://support.microsoft.com/kb/296264:</a>The location of the client registry entry for opportunistic locking has changed from the location in Microsoft Windows NT. In later versions of Windows, you can disable opportunistic locking by setting the following registry entry to 1:HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MRXSmb\Parameters\OplocksDisabled REG_DWORD 0 or 1Default: 0 (not disabled)</blockquote>

[QUOTE="FantaRulez, post: 506037, member: 51267"] I don't know if you're still interested in a solution, but I think I have one. I was having the same problems with my central database, delay write failures and a corrupted database after a time. I've made two changes to my setup, I don't know which one was the actual solution or maybe the combination of the two was the trick. First thing I did was to check if the server used the same MTU size as the client. Well, it didn't so I changed the MTU on the client: System Key: [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\[Adapter ID]] Value Name: MTU Data Type: REG_DWORD (DWORD Value) Value Data: Default = 0xffffffff Create a new DWORD value, or modify the existing value, called "MTU" and set it to equal the required MTU size in decimal. The second thing I did, and then the problem finally went away, was to disable opportunistic locking on the client: [url]http://support.microsoft.com/kb/296264:[/url] The location of the client registry entry for opportunistic locking has changed from the location in Microsoft Windows NT. In later versions of Windows, you can disable opportunistic locking by setting the following registry entry to 1: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MRXSmb\Parameters\ OplocksDisabled REG_DWORD 0 or 1 Default: 0 (not disabled) [/QUOTE]

Verification