Schlagwörter: Manually adding IP address 192.168.1.133 (hangs)
August 5, 2021 um 10:17 pm #1728yusufTeilnehmer
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!!August 6, 2021 um 1:30 am #1731
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.
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.
August 8, 2021 um 5:38 am #1748
- Diese Antwort wurde geändert vor 1 Monat, 2 Wochen von spacedesk Lea.
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.August 9, 2021 um 4:00 am #1767
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.August 10, 2021 um 7:52 am #1779
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 *:*August 10, 2021 um 7:55 am #1780
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=21August 11, 2021 um 2:17 am #1785
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.August 11, 2021 um 8:03 am #1801
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!August 12, 2021 um 2:28 am #1805
OK, thanks for answering the questions.
Could you please send us again the updated diagnostic logs?August 14, 2021 um 6:40 am #1818
Thanks for your reply – I’ve re-run the diagnostic tool and attached the zip file here.
Thanks in advance!August 16, 2021 um 7:21 am #1836
The zipped file you sent does not contain the diagnostic logs (debugview.log, *.etl logs, etc..) that we need for analysis.August 16, 2021 um 8:32 am #1841
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.
ThanksAugust 17, 2021 um 5:18 am #1852
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?August 17, 2021 um 9:01 am #1856
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)?August 17, 2021 um 9:02 am #1857
- Du musst angemeldet sein, um auf dieses Thema antworten zu können.