none
Mstsc debugging capability RRS feed

  • Question

  • Hi!

    Is there any tracing/debugging capability of mstsc.exe/ActiveX component of mstscax.dll? We are currently facing several protocol errors (code 4612) returned by the activex component, and we would like to see what packets can cause this problem. The packets are unfortunately encrypted, and in this environment, encryption cannot be turned off, so we cannot use packet sniffers.

    BR,

    Talien

    Wednesday, November 28, 2012 2:44 PM

Answers

  • Talien,

    Thank you for your kind comments regarding my blogs.  Too bad they were not helpful in your situation.

    I don’t believe there is a method that would cause MSTSC to emit (via log, debug spew or ETW tracing) its on-the-wire traffic in-the-raw.  That’s a feature we would actually discourage.

    The purpose of this forum is to support the protocol specifications and third-party implementers of those protocols: http://msdn.microsoft.com/en-us/library/cc216517.aspx.  We would traditionally work with folks developing their own non-Windows RDP client, for instance, if a specific protocol question arose.

    Since your question involves MSTSC itself and you have a specific error message, I would encourage you to post your issue at the Technet Remote Desktop Services (Terminal Services) forum at http://social.technet.microsoft.com/Forums/en/winserverTS/threads.  There may be other techniques to determine the root cause of your issue.


    Bryan S. Burgin Senior Escalation Engineer Microsoft Protocol Open Specifications Team

    Thursday, November 29, 2012 6:17 PM
    Moderator

All replies