uvarov
asked on
Microsoft, remote desktop, xp sp2
Some time ago remote desktop connection stopped working for me.
It is enabled on the machine to where I want to connect.
I double checked the port (I changed it from the default one).
It was working just fine and then at some point it stopped. I do not know/remember about any changes I made what perhaps could impact it.
The only thing I suspect is related to this message in the event viewer:
Application popup: : \SystemRoot\System32\TSDDD
I looked up what this dll does and it seems to be directly related to the problem.
Literaly the folowing is happening.
I try to connect, the pasword is asked. The window of th remote desktop appears (empty, just blue background) and then it closes with no messages or any other indication of what happened.
Ther is nothing suspecious in the event viewer of the computer from which I am trying to connect.
Please help. Thank you.
It is enabled on the machine to where I want to connect.
I double checked the port (I changed it from the default one).
It was working just fine and then at some point it stopped. I do not know/remember about any changes I made what perhaps could impact it.
The only thing I suspect is related to this message in the event viewer:
Application popup: : \SystemRoot\System32\TSDDD
I looked up what this dll does and it seems to be directly related to the problem.
Literaly the folowing is happening.
I try to connect, the pasword is asked. The window of th remote desktop appears (empty, just blue background) and then it closes with no messages or any other indication of what happened.
Ther is nothing suspecious in the event viewer of the computer from which I am trying to connect.
Please help. Thank you.
TSDDD.dll is directly related to your problem. It is the headless VGA driver Terminal Services/RDP sessions use for console connect and disconnect. That is why the desktop will not load. Are there any other messages or more info in the event log around the error you posted?
ASKER
No there is nothing else. I downloaded svereal files (TSDDD.dll) from different places. I replcaed the file I had there (System32). But it didn't help.
ASKER
The message I listed:
Application popup: : \SystemRoot\System32\TSDDD
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
was from System section of event viewer.
There is sectio there called ACEEventLog. In this section about same time as the time of the above record it has the following which may be related as well:
0000000011: 2007-08-15 11:35:31:590 iDEMDriverSettings.GetDFPD
Error Called by: ATI.ACE.CLI.Aspect.DeviceD
--------------------------
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
May be it tells something? Since it is about ATI (video cards I have) ....
Application popup: : \SystemRoot\System32\TSDDD
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
was from System section of event viewer.
There is sectio there called ACEEventLog. In this section about same time as the time of the above record it has the following which may be related as well:
0000000011: 2007-08-15 11:35:31:590 iDEMDriverSettings.GetDFPD
Error Called by: ATI.ACE.CLI.Aspect.DeviceD
--------------------------
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
May be it tells something? Since it is about ATI (video cards I have) ....
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Also, search for the file ACEEventLog on your hardrive. It is an ATI generated log and may contain more detailed information on the problem you are experiencing with the driver.
ASKER
yep - that only took to reinstall the software package from ati's site
i think this was the exact scenario - windows update somehow replaced working version of sotware (not sure what - perhaps driver only) which did not work with ati's control software as it was expecting the driver and whatever else if anything which came with it instead of the one microsoft delivered with their update.
thank you!
i think this was the exact scenario - windows update somehow replaced working version of sotware (not sure what - perhaps driver only) which did not work with ati's control software as it was expecting the driver and whatever else if anything which came with it instead of the one microsoft delivered with their update.
thank you!
Your welcome. Glad to hear it's fixed.