Does it relate to this? https://www.samba.org/samba/security/CVE-2016-2111.html

The following constraints are applied to SMB1 connections:
"client lanman auth = yes" is now consistently required for authenticated connections using the SMB1 LANMAN2 dialect.
"client ntlmv2 auth = yes" and "client use spnego = yes" (both the default values), require extended security (SPNEGO) support from the server. That means NTLMv2 is only used within NTLMSSP.

What happens if you where todo:
smbclient -L 11.22.33.44 -U Administrator%Password --option=clientntlmv2auth=no

i just try it and result still same,
didnt show the samba version of the target

I'm using a completely up-to-date version of Kali (which currently uses smbclient 4.7.1) and I can confirm this is still an issue.

I encountered the issue when I was trying to solve the Kioptrix Level 1 VM since it relies on smbclient being able to fingerprint the service version.

The only workable solution I've found to get around this issue is to use Metasploit's smb_version script. If anybody knows of a better work-around, please let me know.

Due to the age of the OS (Kali Moto [v1], Kali Safi [v2], Kali Rolling 2016.x/2017.1), these legacy versions are no longer supported.
We will be closing this ticket due to inactivity.

Please could you see if you are able to replicate this issue with the latest version of Kali Linux - https://www.kali.org/downloads/)?

If you are still facing the same problem, feel free to re-open the ticket. If you choose to do this, could you provide more information to the issue you are facing,and also give information about your setup?
For more information, please read: https://kali.training/topic/filing-a-good-bug-report/