No, the problem (of the "hanging") is inherent to the CIFS linux kernel driver. Every linux installation has this problem. It's been a long standing issue that hasn't been addressed for years.
There are several versions of the SMB protocol, v1, v2.0, v2.1 and v3. (see https://blogs.techne...-are-you-using/ for more in-depth information).
Recently, due to severe security issues, SMBv1 has been disabled, not only in Windows 10, but also in the Synology NAS for example. Windows has the option to cycle through all available and allowed protocols, so you as a user don't notice anything, and don't know which protocol is used. But the Linux kernel driver doesn't. It connects using the version it has been programmed with, and if you as a user needs a different version, you need to specify this in the mount options.
Up to kernel v4.13, the default was SMBv1, after that, the default has been upgraded to SMBv3. So if you box has a kernel older than 4.13, and your "server" doesn't support SMBv1, you need to specify the version on the mount. Likewise, if your box runs 4.13 or higher, and your "server" doesn't support SMBv3, you also need to specify the version on the mount.
This is a good overview on this subject: https://www.happyass...ol-version-fun/
The same is true for the authentication mechanism. This used to be NTLM, but in Kernel 3.8 the default has changed to NTLMv2, as Windows no longer supports NTLM (also because of security issues). But depending on the version and configuration of Windows (especially Windows Server), you might need to specify an alternative mechanism on the commandline too.
Edited by WanWizard, 18 February 2018 - 14:07.
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.