Hi all,

We are transitioning from Novell to MS clients but still have file service provided by a NetWare server (6.0 SP3) using
CIFS. We've had problems with connectivity since relying on CIFS that basically fall into three categories:

1. Bad wiring or switch ports cause CIFS connections to be disconnected regularly and thereby cause no end of grief for
the end user. The Novell client seemed to be more tolerant of bad connections, but when we fix the bad connection, the
users seem to be able to work without trouble.

2. Redirecting MyDocuments to a network drive automatically enabled file synchronization which regularly disconnected
the user's drive mappings. This was especially evident using a database program like Access. The solution was to force
MyDocuments back to C: and to disable synchronization. I don't know enough about the synchronization process to know if
the MyDocuments needed to be moved back to C:, but we were desperate enough to go back to square one. Again, there
seems to be a sensitivity on the part of the MS client that causes regular problems for users trying to access resources
on the NetWare server through CIFS.

3. Running a program called eGovPro (written in AcuCobol and VB) which does billing is problematic and keeps erroring
out. SSI tells us that the errors we are receiving (database files are getting corrupted) are normally caused by
network errors and other factors also point to the network as the source of the problems. From previous experience (see
1 and 2 above) I suspect that the MS client is timing out and the network connection is being lost briefly, causing file
corruption and lockups.

We have tried setting the following registry settings on the workstations:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\lanmanserver\parameters]
"autodisconnect"=dword:0000fde8
"EnableOplocks"=dword:00000000

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\lanmanworkstation\parameters]
"UtilizeNTCaching"=dword:00000000

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\MRxSmb\Parameters]
"OplocksDisabled"=dword:00000001

However, we are still running into problems.

CAN YOU RECOMMEND ANY SETTINGS CHANGES ON THE NETWARE SERVER OR THE CLIENT THAT MIGHT IMPROVE PERFORMANCE / REDUCE
CONNECTION BREAKS?

Thanks,

Craig