can´t connect to Samba share from fritzbox-nas

hi
was happy to see that 1.14 has samba option, so no more workaround with total-commander on my GalaxyS10 android.
But i can´t get it connected with keypass2anroid to my kdbx from my fritzbox nas samba share.
when opeing a nother database in keypassandroid i select samba, new file

• url of database
• domain: i keep it empty?
• SambaUsername: my verified samba username from fritzbox
• passwort: copy paste, so no mispelling

then it opened the normal open screen, i can see the full url, and im prompted for the kdbx database masterpassword (as usual) after enter it shows. "Ein 'Fehler ist aufgetreten:failed to login to SMB as %username%"
%usernem% is the username i had keyed in...

• unfortunately RED Error messages are shown only 1 sec... no chance to read them! wth?
• activated debug.log, but can´t be reviewed only send, but sending is not possible "Error sending log length 37339 bytes: Failure from system"

what is very anoing: you can´t edit the SMB parameters once created. you have to go thru the whole "open new file...samba...blalba" way, enter everything again and again?" why is SMB access, and open db not spearated? i had severeal times to do that, at the end i copy pasted it from an temporary email draft, where i had copy pasted it from an kepass db i can access, just to get all the complex url, password etc for copypaste in thi samba promt dialog .... but it is not working either...

by the way: with total commander i can create e samba access, what imusing today, but this is not very convenient, because its opening only a local mirroed copy and not the original... im accessing my fritz nas only from local network, or via VPN from external but just by accessing my local network...

btw: with total commander i can choose some options for samba connection, what i can´t choose with k2a?

• SMB2
• SMB3
• Verschlüsselte Übertraugung (langsamer)
  i had seen an totalcommander shortcut for url with smb2://keypass.kdbx.... but in kepass2android url is smb://
  so maybe only smb1 is used, instead of smb2, what fritzbox is serveing?

No source file, test, or entry point is named in the issue. Start by reproducing the Samba connection failure with the listed Fritzbox NAS and authentication details, then compare the error display, log handling, parameter editing, and SMB version behavior with Total Commander; done means the failing connection and the reported usability problems have clear, tested outcomes.