A screen reader app not working when using quest

Hi,

background: I'm using  a screen reader app called Jaws for Windows. As you might already be aware of,a  screen reader provides speech output for the text displayed on the screen for people with visual impairment.

This app also works over terminal services utilizing its virtual channel feature. How it happens: we need to install the same app on client and server machine and when you connect to the server, the server instance of Jaws communicates with the client instance through rdp virtual channel and sends textual information which in turn converted and conveyed as speech by the client instance.

Now the problem I'm facing is that when I remote onto the server using mstsc, Jaws behaves as described above; however, when I remote ontothe the same server using quest VWorkspace web access, it does not work. The communication between server and client instances of Jaws does not occur although my findings show that under the hood, VWorkspace client is using terminal services.

Possible solutions:

1) Please let me know how can I verify virtual channel activity and any blocking that may be happenning when using VWorkspace client, and how to fix it.

2) If there's a way to extract connection credential from .pit file and use the same to remote onto the server using MSTSC.exe directly, it might  resolve the issue.

Please help me resolving this issue asap as it has become a major opsticle for me in work.

Thanks and Regards,

Varun

pntsc version: 7.2.302.414