@Harv: yes, it shows me a single folder, \\tsclient\Downlo1, which when I try to access, gives the same error message.
– SensefulFeb 8 '11 at 3:07

sounds like a permissions error, not RDP. Are you on the same LAN? It looks like RDP is trying to access the target windows box using SMB, which is a whole ordeal in and of itself.
– Fake NameFeb 9 '11 at 6:57

@Dori: won't the tag [remote-desktop] be very confusing since both Apple and Microsoft have products named "Remote Desktop"?
– SensefulFeb 10 '11 at 8:14

there are good reasons on both sides; my own opinion is that, given that less than 1% of this site's questions are on any "Remote Desktop", there's no real need to split them.
– DoriFeb 11 '11 at 0:08

Thanks for sharing the new method of establishing the link. It confused me at first since the option mentioned by previous posters is not available, but I figured it out -- before reading your post... ;)
– Evan StoneNov 7 '14 at 19:41

Great! The only thing which had me stumped was that I didn't see my folder immediately under 'Computer' of the remote after I had added the 'redirection' folder on local. I figured out I had to restart the remote desktop connection first, because I had already been connected whille adding redirection. So step 5 can also be read as 'Connect to the remote PC (or reconnect if you had already been connected)'.
– BartOct 22 '15 at 11:36

It seems that Microsoft Remote Desktop can't handle paths that contain spaces. I tried hard to share a folder with such a path – no luck. Then I created and shared a folder on my desktop, and it showed up immediately when I reconnected to the remote PC.
– Rolf StaflinSep 27 '16 at 15:32

I'd recommend editing the answer and adding that if you are already connected to the remote computer that you need to re-establish your connection in order for the shared folder to appear. I spent quite a few minutes until I read @Bart comment above.
– robbpriestleySep 20 '17 at 22:45

Solution: Before you start the Remote Desktop session, make the Mac disks available to the Windows-based computer.

1.On the RDC menu, click Preferences.

2.Click Drives, and then on the pop-up menu, select the option that you want.

Your disk or folder is now available so that you can access files that are on your Mac from the Windows-based computer.

If you make this change after you connect, the disk or folder that you select becomes available the next time that you connect.

3.On the Start menu, click Computer or My Computer.

The Mac disk or folder that you have made available is listed with all other disks and folders on your Windows-based computer.

Note If you can't see the Start menu, on the View menu, click Full Screen.To return to window mode later, point to the top edge of the screen until the RDC menu bar appears. On the menu bar, click View, and then clear the Full Screen check box.

4.Open the disk or folder that you want to copy from.

5.On the Start menu, click Computer or My Computer.

6.Open the disk or folder that you want to copy to.

You should now have two windows open, one for the location that you want to copy from, and one for the location that you want to copy to.

7.Drag the document that you want to copy to the location that you want.

There are some organizations that block Dropbox, or in my case, I just really didn't want to use it on my work machine, since who knows what they're snooping... However, this is a GREAT suggestion for anyone who doesn't have those concerns (or who doesn't work in a highly/strictly-regulated corporate environment). Well done.
– Evan StoneNov 7 '14 at 19:38

I will second the Dropbox recommendation. This is the single greatest way to keep many different machines in sync with files there is. If you save a file on your Mac, within seconds it seems, the same file is updated on your PC.

A second approach is to use LogMeIn Pro which can do this but it costs money. In my experience, the speed of LogMeIn is much faster than RDP for remotely controlling another machine.

If you right-click on the folder on your Mac and then "Get Info", what permissions do you see?

Make sure your username (the user that initiated the RDC session) has read and write access to the folder. If that doesn't work, give "read & write" to "everyone" (be careful with this one - anyone with access to this folder will be able to modify the contents).