>>Hi Hugo:
>>
>>That's why the same article says that the solution is not disabling SMB2/3 on server, but on clients!
>
>But, but... my point was that we DO NOT have problems with SMB2/3 at all... that is why I showed that we are using SMB2/3 and we DO NOT have problems (I am repeating myself, hopefully I do not get a suggestion of disabling SMB2/3 anywhere client or server :P)... Anyways, back to my own issues...

One of posts that IMO clearly show that checking functionality of vfp under new versions is needed -
(not only have SOME problems surfaced with SMB > 1, but also the one you expirienced)
although IMO the typical question should not be "does it run" but "any specific problems introduced under/with WinXXX"

regds

thomas