Workgroup and Multi-domain clusters in Windows Server 2016

Hi,

We've 2 node Windows Failover Cluster running on Windows Server 2016 without AD.
They have iSCSI device connected and share as continuous available share.   

Basic operation works fine. 

However, we test by copying a large file to the CA share then perform failover test.
During failover, we can see for all volumes on new active server node:
- resume database can be loaded
- resume key filter can be attached

However, see error on the current active server node after failover:

======
Event: 2103
Msg Source: Microsoft-Windows-ResumeKeyFilter
Message: The resume of handle {4B26D635-64EC-11ED-984F-005056B466E2} on file \Device\HarddiskVolume15\Shares\test\cdrom.iso failed with error status 0xC0000022.

======
Event: 1016
Msg Source: Microsoft-Windows-SMBServer
Message: Reopen failed.

Client Name: \\192.168.8.247
Client Address: 192.168.8.247:60501
User Name: NODE2\smbtest2PwX9i
Session ID: 0x4300014000069
Share Name: datacenter1-dr-veeam
File Name: cdrom.iso
Resume Key: {4B26D635-64EC-11ED-984F-005056B466E2}
Status: {Access Denied}
A process has requested access to an object, but has not been granted those access rights. (0xC0000022)
RKF Status: {Access Denied}
A process has requested access to an object, but has not been granted those access rights. (0xC0000022)
Durable: false
Resilient: false
Persistent: false
Reason: RKF resume create

Guidance:

The client attempted to reopen a continuously available handle, but the attempt failed. This typically indicates a problem with the network or underlying file being re-opened.

On client:

Event: 30611
Msg Source: Microsoft-Windows-SMBClient
Message: Failed to reconnect a persistent handle.

Error: {Access Denied}
A process has requested access to an object, but has not been granted those access rights.

FileId: 0x2000013000000D8:0x0
CreateGUID: {4b26d635-64ec-11ed-984f-005056b466e2}
Path: \testrepo\test\cdrom.iso

Reason: The server denied the create request

Previous reconnect error: The transport connection is now disconnected.
Previous reconnect reason: Disconnected because there was a network disconnect indication

Guidance:
A persistent handle allows transparent failover on Windows File Server clusters. This event has many causes and does not always indicate an issue with SMB. Review online documentation for troubleshooting information.
======

The client then prompts whether to overwrite the file, as if the file on the share is another one due to persistent handle can't be resumed.

The user used to mount the share is defined in administrator group on cluster nodes while LocalAccountTokenFilterPolicy is set to 1.

Would anyone please help?

Thanks a lot.