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