Yup, I thought KB article 312030 was my problem. Never did find enough
hooks to see if Cryptographic services was up and running correctly.
KB article 270588 solved it for me. The "\Device\Video0" value was not
present. Once added and rebooted, I could access via RDP and the listener
was up (not 65536).
Vera, i follow many of your replys, maybe you can help me.
I'm a developer trying to do a custom terminal server client, (Seamless
windows), like New Moon do, but when i developing with the ocx, some times a
black screen appear, and is so slow, but when i use the mstsc.exe everything
is ok, so i try to refer the mstscax.dll in my vb proyect, but i don't know
hot to do this...
Ok vera thanks, i have a little question, we are a Microsoft ISV EMPOWER,
have the MSDN Universal, and we develop terminal server applications and
utilities, but i can't find any developer information anywhere ... i have al
the platform SDK... and nothing, where can i search for this information? i
think this have to exist...
I can only quote a post on this subject from another Terminal
Server MVP, Cláudio Rodrigues:
<quote>
The specs of the RDP protocol are available only to RDP licensees
that pay a lot of money to Microsoft for that. :-(
</quote>
--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---
Ask a Question
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.