Link to home
Start Free TrialLog in
Avatar of hypercube
hypercubeFlag for United States of America

asked on

RDP Display is Black and Connection is Brief

We have a laptop using a desktop monitor / display (VGA).
It's been working fine for a long time.
Suddenly we couldn't RDP into it.  The problem appeared to be the trust relationship with the DC.  
So, that's been fixed and we no longer get the message "your Windows Domain Controller cannot be contacted for NLA"

However, NOW RDP connects and displays a black screen.
And, it appears, the connection terminates within a minute or so.

I've tried all manner of things with the display settings, etc. to no avail.
I've tried to update the display driver on the client.
This is happening with more that one initiating computer on the same client/target.  Other clients seem to be OK
I only see one display to manage - I don't think that's normal.
Avatar of Harjit Dhaliwal
Harjit Dhaliwal
Flag of United States of America image

Try unchecking persistent bitmap caching in your RDP client and see if that works.
User generated image
Avatar of hypercube

ASKER

I already did that....
What is the client OS? It is fully updated?
Was there any update recently on the server side?
Did you tried Remote Desktop Connection Manager?
Also try with the application like https://mremoteng.org/download which has lot many features as MS is taking away Remote Desktop Connection Manager  now.

Anything in the Event Log of the server while the client is trying to connect?

Thanks,
Sudeep

Both OSs are Windows 10 Pro.  There are many of these pairs that all work fine except this one remote computer.
Yes, this problem is with RDC.
My task is to fix RDC.
We tried manipulating the screen management in the laptop but it did no good.  We've been using it this way with the screens duplicated and the laptop closed for a long time.  Opening the laptop has no effect.



ASKER CERTIFIED SOLUTION
Avatar of hypercube
hypercube
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
We have blamed this on Windows 10 version 2004 and have reverted to version 1909.
It's rather typical of the *very* strange behavior that we're seeing with v2004 - seems there's no rule and no clear fix.
Right now I have another that will not share files.
There seems to be no correlation from one computer to another really.

Thanks for trying to help!!

Microsoft support, when told we had gone beyond the 10-day limit, suggested we do a "clean install" but didn't say of which version.  I tried to get a URL for a v1909 .iso and had no luck - wasted much time getting the runaround from Microsoft.  Seems odd that an .iso of what one had been using would not be available.  I understand the "philosophy" of supporting minimum versions but this is truly ridiculous.  v1909 .iso is gold right now one might imagine.