 Rank: Guest Joined: 9/20/2018(UTC) Posts: 1  Location: MA
|
I have a network connected Windows 10 system that I am running headless. I can connect to it using RDP, VNC, TeamViewer, but when I try to connect to it using ScreenConnect I get a blank screen. I can see the icons and windows in the preview pane in ScreenConnect but the connection window is blank. The computer responds to clicks because If I click in the area on the connection window where the icon appears in the preview I can open and run things, I was even able to sign in to the computer remotely with my credentials but the window stayed blank. Since my company uses ScreenConnect as a standard remote connection I really don't want to have to use a different client on this 1 box. Yes I have all of the latest updates in Windows 10 and the latest version of ScreenConnect. Why would remote connection work fine with all of these other clients but not ScreenConnect?
Thank You,
Stefan
|
|
|
|
|
|
 Rank: Advanced Member Medals:  Joined: 11/11/2010(UTC)
Posts: 70
Location: Detroit, MI
Thanks: 3 times
Was thanked: 5 time(s) in 4 post(s)
|
Originally Posted by: sgadecki@cleanslatecenters.com  I have a network connected Windows 10 system that I am running headless. I can connect to it using RDP, VNC, TeamViewer, but when I try to connect to it using ScreenConnect I get a blank screen. I can see the icons and windows in the preview pane in ScreenConnect but the connection window is blank. The computer responds to clicks because If I click in the area on the connection window where the icon appears in the preview I can open and run things, I was even able to sign in to the computer remotely with my credentials but the window stayed blank. Since my company uses ScreenConnect as a standard remote connection I really don't want to have to use a different client on this 1 box. Yes I have all of the latest updates in Windows 10 and the latest version of ScreenConnect. Why would remote connection work fine with all of these other clients but not ScreenConnect?
Thank You,
Stefan It's more of a display driver issue than an OS issue. We run into it a lot when we setup NVRs for camera systems. This solves it for us: https://www.ebay.com/i/163091870646?chn=psYou can get them at a lot of different places, the ebay link popped up first on google. Jason
|
|
|
|
|
|
Forum Jump
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.
