[angels11_6]

Here’s a better pic with all the measurements included.

THanks in advance !

Attachments:

You must be logged in to view attached files.

[angels11_6]

Pic of video wall

Attachments:

You must be logged in to view attached files.

[angels11_6]

Picture of video wall in attachment

[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.

[angels11_6]

Here’s the screenshots.

Attachments:

You must be logged in to view attached files.

[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]

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.

[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.

[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!

[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

[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]

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.

[Autor]

Beiträge