Disclaimer:

All content provided in these articles is for informational purposes only.

Amitego gives no support or warranty for the accuracy or completeness of any information in these articles or found by following any link on this site.

Theme: OSGD,VLX,RDP     Audience: Administrators,System Integrators

Requirements: OSGD5.1/5.2 & VISULOX 3 & rdesktop

    

Symptom

rdesktop at times has an issue with client drive mapping to some Windows OS (including Win2012).

The mapped drives are not shown and therefore not accessible.

It is not clear at this time if the issue is with rdesktop or Windows OS, but It seems that specifications for RDP (MS-RDPEFS) have changed.

Solution

If this symptom occurs in your RDP to Windows connection, you also have to forward audio in order to get disk forwarding to work

by doing the following:

with rdesktop called directly from commandline

The synthax for rdesktop client drive mapping:
rdesktop -r disk:<mydisk>=<path> <servername>
 
if the client drive mapping is not working properly add sound forwarding to the rdesktop:
rdesktop -r disk:<mydisk>=<path> -r sound:local <servername>

with VISULOX rdesktop integration

The synthax using vlxshell:
vlxshell -client rdesktop -drive <mydisk> -- <arguments to rdesktop> <servername>
 
if the client drive mapping is not working properly add sound forwarding to the vlxshell:
vlxshell -client rdesktop -drive <mydisk> -- -r sound:local <arguments to rdesktop> <servername>

 

Copyright © VISULOX