Thank you for making the effort and posting the screenshot. There are the two areas you need to fix in order to enable local access to your My Cloud Home (MCH) and log in from your version of Windows. The MCH software is designed for users running the Home or Pro version of Windows which still allow guest authentication log on by default.
It would appear that you are using a version of Windows such as Windows Enterprise or Windows Education which do not allow the default behavior typical of the Windows Home version and that is because:
Guest account access to a remote server.
Fall back to the Guest account after invalid credentials are provided.
SMB2 and SMB3 have the following behavior in these versions of Windows:
Windows 10 Enterprise and Windows 10 Education no longer allow a user to connect to a remote share by using guest credentials by default, even if the remote server requests guest credentials.
Windows Server 2019 Datacenter and Standard editions no longer allow a user to connect to a remote share by using guest credentials by default, even if the remote server requests guest credentials.
Configure your third-party SMB server device to require a username and password for SMB connections. If your device allows guest access, any device or person on your network can read or copy all of your shared data without any audit trail or credentials.
If you can't configure your third-party device to be secure, you can enable insecure guest access with the following Group Policy settings:
Open the Local Group Policy Editor (gpedit.msc) on your Windows device.
In the console tree, select Computer Configuration > Administrative Templates > Network > Lanman Workstation.
For the setting, right-click Enable insecure guest logons and select Edit.
Select Enabled > OK.
