Connected – Display Off

[yusuf]

after I installed it and I can’t open the display settings, every time I open the display settings it always forces close, and on the secondary device screen I only see “Connected – Display Off”
Please help me!!

Attachments:

You must be logged in to view attached files.

[spacedesk Lea]

Hi @yusuf,
Could you please run devmgmt.msc then check on device manager if spacedesk Graphics Adapter (underneath Display adapters) has error or disabled?
Maybe send a screenshot of the spacedesk Graphics Adapter in device manager.

Then to further analyze this issue, please download the spacedesk diagnostic script here, then extract it.
https://www.dropbox.com/s/z8h5llgi8c2ig3g/2021_spacedeskDiagnosticTool.zip?dl=0

Inside you will find spacedeskDiagnosticTool.cmd, just right-click it then run as administrator.
This script will start a debug view app to capture spacedesk debug traces.
On step 5 it will prompt you to reproduce the issue (by connecting the viewer app and wait for the issue to happen), make sure to do this before pressing any key to continue.
After the script is done, a folder will be created on the same folder as the script file which contains various log files that we need for analysis.
Please right-click it -> Send to -> Compressed (zipped) folder, then attach the *.zip file on your next reply.

• Diese Antwort wurde geändert vor 3 Jahren, 4 Monaten von spacedesk Lea.

[angels11_6]

Hi,

I’m also having the same issue. I’ve downloaded the diagnostic tool and attached the debug view file here.
Any help is greatly appreaciated. I’ve spent weeks trying to figure this out!! Thank you.

Attachments:

You must be logged in to view attached files.

[spacedesk Lea]

Hi @angels11_6,
Thanks for sending the debug view log.
Based on the log file, you have incompatible display driver detected by spacedesk server.
Do you have splashtop WiredX display on your primary machine?
If yes, please uninstall the virtual display on it’s advanced settings.

[angels11_6]

Hi,
Thanks for your response. We’ve investogated this further and Android devices running Spacedesk can’t connect to the main PC. They’re on the same network and both devices can ping each other. We ran a pcap on the main PC and can see the Android Spacedesk trying to connect on UDP/28252 but the server isn’t responding. Please see attached pcap file for your reference. We also checked the main PC and can see it listening on 0.0.0.0:28252 but not on it’s IP address 192.168.1.133;
UDP 0.0.0.0:28252 *:*
UDP 0.0.0.0:49668 *:*
UDP 0.0.0.0:49914 *:*
UDP 0.0.0.0:52061 *:*
UDP 0.0.0.0:53097 *:*
UDP 0.0.0.0:54478 *:*
UDP 0.0.0.0:58413 *:*
UDP 0.0.0.0:59339 *:*
UDP 0.0.0.0:60187 *:*
UDP 0.0.0.0:61075 *:*
UDP 0.0.0.0:61076 *:*
UDP 0.0.0.0:61676 *:*
UDP 0.0.0.0:62728 *:*
UDP 127.0.0.1:1900 *:*
UDP 127.0.0.1:10010 *:*
UDP 127.0.0.1:49670 *:*
UDP 127.0.0.1:59338 *:*
UDP 127.0.0.1:61675 *:*
UDP 192.168.1.133:137 *:*
UDP 192.168.1.133:138 *:*
UDP 192.168.1.133:1900 *:*
UDP 192.168.1.133:5353 *:*
UDP 192.168.1.133:5353 *:*
UDP 192.168.1.133:61674 *:*

[angels11_6]

Your system didn’t like the pcap file dues security issues?? Weird…
No. Time Source Destination Protocol Length Info
137 2.456935 192.168.1.123 192.168.1.255 UDP 63 54365 → 28252 Len=21
212 2.615869 192.168.1.123 192.168.1.133 UDP 63 54365 → 28252 Len=21
213 2.615869 192.168.1.123 192.168.1.133 UDP 63 54365 → 28252 Len=21
214 2.615869 192.168.1.123 192.168.1.133 UDP 63 54365 → 28252 Len=21
215 2.615869 192.168.1.123 192.168.1.133 UDP 63 54365 → 28252 Len=21
216 2.615869 192.168.1.123 192.168.1.133 UDP 63 54365 → 28252 Len=21
242 2.648084 192.168.1.133 192.168.1.123 ICMP 74 Echo (ping) request id=0x0001, seq=22/5632, ttl=128 (reply in 245)
245 2.652214 192.168.1.123 192.168.1.133 ICMP 74 Echo (ping) reply id=0x0001, seq=22/5632, ttl=64 (request in 242)
258 2.662746 192.168.1.123 192.168.1.255 UDP 63 54365 → 28252 Len=21
259 2.663022 192.168.1.123 192.168.1.255 UDP 63 54365 → 28252 Len=21
260 2.663174 192.168.1.123 192.168.1.255 UDP 63 54365 → 28252 Len=21
261 2.663881 192.168.1.123 192.168.1.255 UDP 63 54365 → 28252 Len=21
262 2.663881 192.168.1.123 192.168.1.255 UDP 63 54365 → 28252 Len=21

[spacedesk Lea]

Hi @angels11_6,

Thanks for the info.
Is there any issue on spacedesk discovery on your side?
Based on the debugview log file you sent, the viewer were able to connect to the server’s IP address properly, it’s just that the server detects an incompatible display hook driver on your priamry machine which is the cause of display off status on your side.

Were you able to remove/uninstall the incompatible display driver detected by the spacedesk server?
Please confirm if you have splashtop WiredX display or Duet Display software on your primary machine.

[angels11_6]

HI,

Thanks for getting back to me. Please see my responses below:

“Is there any issue on spacedesk discovery on your side?” Yes, there is an issue as the remote Spacedesk clients can’t connect to the main PC. Please see my previous post with the network diagnostics clearly showing the clients trying to connect and the server not responding

“Were you able to remove/uninstall the incompatible display driver detected by the spacedesk server?” Yes, only the standard Intel/NAVIDA drivers are installed, which according to your website are supported

“Please confirm if you have splashtop WiredX display or Duet Display software on your primary machine.” – Neither of these are installed on the main PC

Any help is appreciated.

Thanks!

[spacedesk Lea]

Hi @angels11_6,
OK, thanks for answering the questions.
Could you please send us again the updated diagnostic logs?

[angels11_6]

Hi,

Thanks for your reply – I’ve re-run the diagnostic tool and attached the zip file here.
Thanks in advance!

Attachments:

You must be logged in to view attached files.

[spacedesk Lea]

Hi @angels11_6,
The zipped file you sent does not contain the diagnostic logs (debugview.log, *.etl logs, etc..) that we need for analysis.

[angels11_6]

Hi,
Please find attached the updated diag file. Note, the screens still don’t connect, nor is the server responding. We can see the screens trying to connect when doing a pcap, but no response from the server.
Thanks

Attachments:

You must be logged in to view attached files.

[spacedesk Lea]

Hi @angels11_6,
Thanks for sending the diagnostic logs.
It seems that you have an OSBase display driver on your primary machine.
There’s a possibility that it’s causing a conflict with spacedesk.
Are you using any USB display software while trying to connect a spacedesk? Or any similar software like spacedesk?

[angels11_6]

HI,

I previously had osbase installed, but removed it following your initial device. I can confirm I’m not using any other USB display / adapter.
I’ve included (in the attached doc) a screenshot from device manager showing the display drivers and USB drivers.
It’s not even showing ‚connected display off“ any more.. it just simply won’t connect at all (note: it has definitely previously worked as I had the guy from Monitors Anywhere initially giving me advice about this and remoted into my computer to try to set up. That has since expired but now for some reason I can’t even connect to the monitors.

Note: the screens are not symmetrical, what is the impact of this (if any)?

[angels11_6]

Here’s the screenshots.

Attachments:

You must be logged in to view attached files.

[spacedesk Lea]

Hi @angels11_6,
Thanks for the info.
To verify if any OSBase is already removed on your machine, could you please run Command Prompt as admin, then type the command below to check if the any OSBase driver present in your system and if the status is Stopped or Running.

sc query ddmgr
sc query ddkmd

If you get the status Stopped or Running please follow it up with commands:

sc delete ddmgr
sc delete ddkmd

Then reboot your primary machine, then try again with spacedesk.

[angels11_6]

Thanks for your suggestion – that worked!
Now just have to calibrate the screens… if I have issues doing that, I’ll come back to you.

Thanks so much for your help.

[spacedesk Lea]

Hi @angels11_6, glad to hear that it worked.

[werwerwer]

Hi, I downloaded WiredDisplay before but then removed it. Today I downloaded spacedesk and got an error „display off“ (there are no drivers from WiredDisplay in the device manager) please help to solve the problem as soon as possible

[itamax2073]

@egscherbackov
You have to uninstall, remove all traces of WiredDisplay from tablet devices, smartphones etc etc and from the computer
Are two programs that conflict with one disabling the other from functioning

• Diese Antwort wurde geändert vor 3 Jahren, 2 Monaten von itamax2073.

[werwerwer]

I have already deleted them, they are not in the list of video adapters, but I still get an error

[werwerwer]

@itamax2073 I have already deleted them, they are not in the list of video adapters, but I still get an error(

[itamax2073]

@egscherbackov
In my opinion you have some traces left on your PC
of the previous program I always use revo uninstaller for deep cleaning
Currently I have no problem with the PC driver version 1.0.18 and the app version 0.9.81. Everything works perfectly
Try remove spacedesk re-install the previous program
And uninstall it again with REVO Uninistaller once uninstalled do a deep scan and delete all the files that come your way
Reboot your pc and install spacedesk from scratch

[spacedesk Lea]

Hi @egscherbackov,
To further analyze this issue, please download the spacedesk diagnostic script here, then extract it.
https://www.dropbox.com/s/z8h5llgi8c2ig3g/2021_spacedeskDiagnosticTool.zip?dl=0

Inside you will find spacedeskDiagnosticTool.cmd, just right-click it then run as administrator.
This script will start a debug view app to capture spacedesk debug traces.
On step 5 it will prompt you to reproduce the issue (by connecting the viewer app and wait for the issue to happen), make sure to do this before pressing any key to continue.
After the script is done, a folder will be created on the same folder as the script file which contains various log files that we need for analysis.
Please right-click it -> Send to -> Compressed (zipped) folder, then attach the *.zip file on your next reply.

[Autor]

Beiträge