Move to Win Server 2012 R2

[Digikiss]

Hello
Just got a new Win 2012R2 Server and having some issues. Currently Openfiler for file server = XP, Vista and W7 clients no problem

A test read/lock/write on W7 & XP seems to work fine, the problem is when the test program is executed on the server itself (in view of rdp use). Very quickly produces CDX error on either client or server.
All the usual done: SMB2 & oplocks disabled server side. XP client oplocks disabled. W7 oplocks & SMB2 disabled. Server client SMB2 & oplocks disabled.
Server disk caching is disabled.
Seems like some other caching/locking is still going on when when the server is accessing files 'locally'?
Need to access files via map drives and RDP into server.
Would like to avoid recoding as its working fine with files stored on Openfiler and worked fine before that on files stored on an XP 'server'. Code is very 1980's but is working fine in current setup.
Obvious solution would be to keep Openfiler or other NAS for file server but just forked out for pricey new kit so hmmmm would like to find solution!
Any ideas?

Mods made below:

Clients XP:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MRXSmb\Parameters OplocksDisabled = 1
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters]
"FileInfoCacheLifetime"=dword:00000000
"FileNotFoundCacheLifetime"=dword:00000000
"DirectoryCacheLifetime"=dword:00000000

Client Win 7 - 1:
SMB2 desactivé
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MRXSmb\Parameters OplocksDisabled = 1
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters]
"FileInfoCacheLifetime"=dword:00000000
"FileNotFoundCacheLifetime"=dword:00000000
"DirectoryCacheLifetime"=dword:00000000

Client Win 7 - 2:
Aucun modification

Serveur:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters SMB2 = 0
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters SMB1 = 1
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters EnableOplocks = 0
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters EnableOpLockForceClose = 1
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters CachedOpenLimit = 0



HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MRXSmb\Parameters OplocksDisabled = 1
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters]
"FileInfoCacheLifetime"=dword:00000000
"FileNotFoundCacheLifetime"=dword:00000000
"DirectoryCacheLifetime"=dword:00000000

 

[clipper01]

I had a similar problem, after switch to server 2012, apps crawled , had set on seperate virtual server, smb2 disabled etc etc. Tried all the kind of things above, finally fixed when the network hub was replaced with managed switch for that section. It does seem there must be some change in the 'caching' mechanisms that greatly increases the number of round-trips on the network, for shared files, and in the pre server 2012 case the 'slow' switch was just not an issue. So worth having a look at the netwrok switches

 

[Olaf Doschke]

That's a good hint, oplocks are blamed too fast, there are simpler reasons for slowness, non optimal indexing being the first, temp files configured to be on a slow drive or even a network share, is another one. It's simplest to stay with the OS default.

Bye, Olaf.

 

[GTGeek88]

I saw elsewhere that someone was having issues with VFP on WinServer 2012 and - kind of strangely - he noted that some clients accessed the files using UNC naming and some via mapped drives. He switched everyone to mapped drives and the issue resolved. It's worth a try, I suppose.

 

[Digikiss]

Hi
Thanks for all the suggestions and help.
I ended up just putting the files for the VFP app on a Synology NAS - enabled SMB1, disabled Oplocks. Works great!