Hi All thanks for taking my call....
We have some old Milling machines which use a Windows XP controller touch screen to load the programs.
Until recently these have been connected via network drive to a Windows Server 2012 R2 SMB1.0 based file share and all has been well.
We need to decommission the Windows 2012R2 server so I've copied the files to a Windows Server 2019 hyper-v virtual machine with the SMB1.0/CIFS feature installed.
I've then remapped the network drives to point to the \server\fileshare of the programs they need to load.
They can see all the files listed in the directory but when they try and load one they get a "File system error" and are unable to load them.
If I go on to the file server itself and try and rename or delete the offending file I'm told that it is open by "System" and I'm unable to do anything with it.
If I look in Open files on the server I can see the file in question is open for read by the machine that tried and failed to open it. If I close the file from here I can then rename or delete the file.
The problem is that "The file" can be any file or files in the file share, we have 9 HURCO milling machines that need access to this file share and they're all having the same problem with different files.
I have re-copied all the files from the old 2012 server and it solves the problem for a while but the issue comes back eventually. It doesn't seem to be the same file or files any time.
Is there something peculiar to Windows 2019 running SMB1.0 file shares? Or some issue with Windows XP machines opening files on it?
If I run a windiff on the files on each server I'm told they are byte for byte identical. Sorry but I'm at a complete loss.
Any help would be gratefully received.