Using Remote Desktop from MachineA to MachineB (B is the RDP host, A is the client)
On B (via RDP), you can normally browse or map a drive to \\tsclient\c in order to get to MachineA’s C: drive.
You can get to OTHER drives normally (e.g. \\tsclient\d is probably the CDROM drive)
UNKNOWN AT THIS POINT
Several variables, but I get System Error 87, which indicates that the user is not authorized. This may be due to the presence or a lack of compatible account on both machines, or due to mutual trust via a Windows AD domain infrastructure, or maybe a GPO that’s blocking this feature. I have experienced this problem using multiple RDP clients, including both the default “XP” version, and it’s updated “6.x” successor.
Although I DON’T have a good solution at this point, I DO have an excellent work-around ;-)
1. ON MachineA: Go to “My Computer” and find a free drive letter. If you have one hard drive in the client PC, E: may be free. If you have two hard drives, F: may be free. Find a drive letter that is not already in use (X: Q: etc… will work fine). This example will assume “E:”
2. At a command prompt on MachineA, type the following command:
SUBST E: C:\
“E:” will now be connected to C:\. If you type “SUBST” with no parameters, it will list the current “Substitution” list:
C:\>subst e: c:\
E:\: => C:\
3. Initiate the RDP session as normal from MachineA to MachineB.
4. On MachineB (via RDP window), instead of accessing \\tsclient\c, access MachineA’s hard drive via \\tsclient\e
I have found that this works equally well with RDP in some cases where memory sticks and certain other types of drives can not be redirected, due to GPO or local security software that prevents this behavior.