The problem is that your initial post didn't specify a security mode for Samba. You've just given the share definition. The two interact, but one is not the other.
A security mode describes HOW your clients will authenticate. This also means that, if you fail to make a working model, typically most installations will default to either guest or nobody as the user you are mapped to. If it is set up correctly, your remote credentials are mapped to a local user, a mapped user account stored in the samba back-end, or some other mapping (typically used with Active Directory), depending on how you have this set up. That mapping dictates who you present yourself as when accessing the share.
The share definition dictates what is shared to whom in the context of the security mode. Now that you have (or haven't) authenticated yourself, the resulting identity is compared to what is specified for the share definition; access to the share is granted in varying degrees based on what the definition says.
In order to fully diagnose what is happening, we would need to see the entire smb.conf file. I would suggest typing out
testparm > results.smb
and copying the contents of
results.smb to your posting, so everyone can see what is happening.