PAul
Thu Sep 18 12:37:12 CDT 2003
Since you've just upgraded the server and not the networking hardware, it
probably is not a hardware problem. But bear in mind that it could be a
Windows driver issue, at the client side.
The solution to a very similar problem for us was registry hacks.
We went from NT to Windoes 2000 and overnight had hundreds of 1104 errors.
On the old NT 3.51 servers we had MS recommended patches to fixc the
problem,
But there were no Win2000 equivalents and we were really stuck.
Win2000 (we use Terminal Server) isn't too bright about multiple users
accessing the same files.
It gets awfully upset when one user logs out, it loses the connection (to
the files that user was using) for all other users. Which causes the 1104
problems. You will also see eror 2005 occasionally.
There is a fortunate side effect of a few registry changes that made the
1104 errors go away.
Knowledgebase article 299603
>Microsoft cannot guarantee that you can solve problems
>that result from using Registry Editor incorrectly. Use
>Registry Editor at your own risk.
>1. Start Registry Editor (Regedt32.exe).
>2. Locate the OpLocksDisabled value under the
>following key in the registry:
>HKEY_LOCAL_MACHINE\System\CCS\Services\Mrxsmb\Parameters
>3. On the Edit menu, click DWORD, type 0x1, and then
>click OK.
>4. Locate the CachedOpenLimit value under the
>following key in the registry:
>HKEY_LOCAL_MACHINE\System\CCS\Services\LanmanServer\Parame t
>ers
>5. On the Edit menu, click DWORD, type 0x0, and then
>click OK.
>6. Locate the UtilizeNTCaching value under the
>following key in the registry:
>HKEY_LOCAL_MACHINE\System\CCS\Services\LanmanWorkstation\P a
>rameters
>7. On the Edit menu, click DWORD, type 0x0, and then
>click OK.
>8. Quit Registry Editor.
I'm surprised to find that it's not just terminal server, we needed to edit
the data servers and the standalone PC clients too. So it's worth looking at
that, but bear in mind there is a "proper" fix too.
There is a new HotFix that makes things work much better.
Kowledgebase artielc 818528
CAUSE
The Windows 2000 network redirector maintains the data structures per
computer, and therefore if two users on the same terminal server access the
same file over the network, they share the same data structures internally.
When the first user closes the file, the redirector also closes the file for
other users.
RESOLUTION
A supported fix is now available from Microsoft, but it is only intended to
correct the problem that is described in this article. Only apply it to
systems that are experiencing this specific problem. This fix may receive
additional testing. Therefore, if you are not severely affected by this
problem, Microsoft recommends that you wait for the next Windows 2000
service pack that contains this fix.
To resolve this problem immediately, contact Microsoft Product Support
Services to obtain the fix. For a complete list of Microsoft Product Support
Services phone numbers and information about support costs, visit the
following Microsoft Web site:
http://support.microsoft.com/default.aspx?scid=fh;[LN];CNTACTMS
Note In special cases, charges that are ordinarily incurred for support
calls may be canceled if a Microsoft Support Professional determines that a
specific update will resolve your problem. The usual support costs will
apply to additional support questions and issues that do not qualify for the
specific update in question.
-----
We have been testing that in Belgium since its release and so far have no
problems.
But your mileage may vary and contents settle during shipment.