The reason why mine work and why yours didn't is probably due to the pesky "permissions" issue we have mentioned before.
When you are making a connection to a server's file system, the Windows syntax is (as mentioned previously)
\\<seerver ip or name>\<share name>
The connection string's share name is usually set identically to the host's local directory name by the individual who is setting up the share, but it does not have to be. The point here is that the <share name> in the connection string is not really a directory name.
When the share is set up, it will have a default directory path within the host's file system. Assuming you have the proper permission, you can then path to or specify subdirectory names. This is probably why r:\myServer did not work though, since there probably is no subdirectory called "myServer" underneath the default path that your "r:\" share is using.
Your pi obviously has a public share that you are now utilizing, and is set up with an empty user id and password. Your access to the pi's file system through that share are then restricted to whatever that public share was set to. You can also connect to the shares and specify a specific user id and password at connection time, and gain more file access permissions. I connected my share using the user id that Allonis set up for the pi, which I beleive is a root user. Therefore I skip permission errors entirely. Allonis should have provided you with that user id and password, in the packaging material you received along with the pi. I can guess what that userid is, but I am not putting it here in this public forum! I also made my share a permament share, so I don't have to re-enter that user id and password each time I reboot either system.
Full disclosure: I am proficient with Windows security and such, but still somewhat sketchy on Unix. My assumptions on how Unix is working may not always be completely accurate.
