I would say that it looks like a username and or password problem on the surface, but since you've already said that you can access other shares on the same server from the same client machine with the same username and password, then it is more likely an explicit permission problem unique to that particular share you'll need to look closely at share and ntfs permissions specific to that share regarding users as well as groups and compare that information to another share that you can access and determine the difference. In the case of nested shares, there may be inheritance being passed down from the parent container impacting your ability to access that share.
The best bet is to look at the share and determine who can access it (share tab as well as security tab) what group has permissions, what specific user (if any) has permissions, what group does that user belong to, does that group have permissions.
With a home version of the OS, you may not be able to resolve this issue with out resorting to desperate measures and sacrificing security for access. (The old everyone group full control seldom if ever a good idea.)
If you are the server administrator and circumstances permit, you may want to add the Everyone group, with full control in both Share and NFTS permissions, just temporarily for testing purposes only. This is contrary to what is considered best practices for network file and folder security, but may help you further diagnose the issue and you can always remove or adjust them after testing. Not a recommendation, just an option.
Regards
Randy