As exvor points out, have you looked at the user credetials that are used to connect to the Windows share?
All Windows shares have permissions on them, so you'll need to give the proper username and password to access them. smbmount passes your credetials (username/password on the Linux box) by default, probably. So if those aren't the ones you need to give to Windows to get access on the share, then you'll need to supply some smbmount options for specifying the right username/passwd.
You should give the shares real names, not use "D$" (the default sharename). Linux shells may misread the $ as a special character, so enclosing it in single quotes (ie '//192.168.1.110/D$') is a good idea too.
Mounting a specific folder like
smbmount //192.168.1.110/mp3s /mnt/homegrown/
will only work if the folder itself is shared on the Windows box.
On Windows, you can share both entire partitions (like D:, E:, etc) and folders, or a combination of both.
This is useful in case, for instance, you want to give different access permissions to the contents of
D: and D:\secrets\, but you still want to share both. If you want to share both the partition (like D
and a folder on that partition, with the same access permissions, then you'll only need to put a Win share on the partition.
Remember also that, on Windows, share permissions are not the same as folder permissions.
In short, please verify:
1. the Windows share (name, permissions)
2. the username/passwd you're supplying to Windows in order to gain access.
My guess is that 1. is the problem, since you get an error that says that there is no share that has the name you gave.
2. would result in a "access denied" error only, not in the "called name not present" stuff. But with Windows, you can never be sure.