x11vnc e schermo nero

[Vakers]

Davvero una mano di aiuto che esco pazzo da 1 settimana.....

Ho un pc dentro la mia lan con su Kali, ed istallato x11vnc server,
lato client... un pc con windows 10, non c'è verso di pilotarlo in remoto..
dato che il client con VNC Viewer, da SEMPRE E SOLTANTO SCHERMO NERO!!

In collo il comando in automatico che do alla partenza sul server:

x11vnc -rfbport 5900 -forever

grazie

https://i.imgur.com/aFShUBk.jpg

[sacarde]

io ho usato sul server:



x11vnc -auth /var/run/xauth/xxxxxxx -display :0

[mmiat]

io non uso più vnc ma teamviewer, ma al tempo seguii questa guida: https://seb.so/vnc-from-boot-without-logging-in-ubuntu-lubuntu-xubuntu-and-mint-lmde/ dopo aver rimosso vino (c'è ancora?)

[Vakers]

ancora schermo nero, poi provo la procedura di mmiat, per ora da questo output:

The VNC desktop is: kali:0
PORT=5900

******************************************************************************
Have you tried the x11vnc '-ncache' VNC client-side pixel caching feature yet?

The scheme stores pixel data offscreen on the VNC viewer side for faster
retrieval. It should work with any VNC viewer. Try it by running:

x11vnc -ncache 10 ...

One can also add -ncache_cr for smooth 'copyrect' window motion.
More info: http://www.karlrunge.com/x11vnc/faq.html#faq-client-caching

23/08/2018 13:53:51 Got connection from client 172.20.10.10
23/08/2018 13:53:51 other clients:
23/08/2018 13:53:51 Normal socket connection
23/08/2018 13:53:51 Disabled X server key autorepeat.
23/08/2018 13:53:51 to force back on run: 'xset r on' (3 times)
23/08/2018 13:53:51 incr accepted_client=1 for 172.20.10.10:58748 sock=11
23/08/2018 13:53:51 Client Protocol Version 3.8
23/08/2018 13:53:51 Protocol version sent 3.8, using 3.8
23/08/2018 13:53:51 rfbProcessClientSecurityType: executing handler for type 1
23/08/2018 13:53:51 rfbProcessClientSecurityType: returning securityResult for client rfb version >= 3.8
23/08/2018 13:53:51 created xdamage object: 0x1c00024
23/08/2018 13:53:52 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000018)
23/08/2018 13:53:52 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000016)
23/08/2018 13:53:52 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000015)
23/08/2018 13:53:52 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x0000000F)
23/08/2018 13:53:52 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0xFFFFFEC6)
23/08/2018 13:53:52 Enabling full-color cursor updates for client 172.20.10.10
23/08/2018 13:53:52 Enabling NewFBSize protocol extension for client 172.20.10.10
23/08/2018 13:53:52 Using ZRLE encoding for client 172.20.10.10
23/08/2018 13:53:52 client useCopyRect: 172.20.10.10 -1
23/08/2018 13:53:52 client_set_net: 172.20.10.10 0.0058
23/08/2018 13:53:52 Pixel format for client 172.20.10.10:
23/08/2018 13:53:52 8 bpp, depth 6
23/08/2018 13:53:52 true colour: max r 3 g 3 b 3, shift r 4 g 2 b 0
23/08/2018 13:53:52 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000018)
23/08/2018 13:53:52 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000016)
23/08/2018 13:53:52 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000015)
23/08/2018 13:53:52 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x0000000F)
23/08/2018 13:53:52 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0xFFFFFEC6)
23/08/2018 13:53:52 Enabling full-color cursor updates for client 172.20.10.10
23/08/2018 13:53:52 Enabling NewFBSize protocol extension for client 172.20.10.10
23/08/2018 13:53:52 Switching from ZRLE to raw Encoding for client 172.20.10.10
23/08/2018 13:53:52 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000018)
23/08/2018 13:53:52 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000016)
23/08/2018 13:53:52 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000015)
23/08/2018 13:53:52 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x0000000F)
23/08/2018 13:53:52 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0xFFFFFEC6)
23/08/2018 13:53:52 Enabling full-color cursor updates for client 172.20.10.10
23/08/2018 13:53:52 Enabling NewFBSize protocol extension for client 172.20.10.10
23/08/2018 13:53:52 Switching from raw to ZRLE Encoding for client 172.20.10.10
23/08/2018 13:53:52 Pixel format for client 172.20.10.10:
23/08/2018 13:53:52 32 bpp, depth 24, little endian
23/08/2018 13:53:52 true colour: max r 255 g 255 b 255, shift r 16 g 8 b 0
23/08/2018 13:53:52 no translation needed
23/08/2018 13:53:52 client 1 network rate 256.2 KB/sec (256.2 eff KB/sec)
23/08/2018 13:53:52 client 1 latency: 4.7 ms
23/08/2018 13:53:52 dt1: 0.0002, dt2: 0.0677 dt3: 0.0047 bytes: 16798
23/08/2018 13:53:52 link_rate: LR_UNKNOWN - 4 ms, 256 KB/s
23/08/2018 13:54:01 created selwin: 0x1c00025
23/08/2018 13:54:01 called initialize_xfixes()

[psimem]

Mi ricordo che un po' di tempo fa' avevo avuto un problema simile (schermo nero lato client) tra due debian 8 ed avevo risolto usando l'opzione -nodpms per "risvegliare" lo schermo del server da low power state:
x11vnc -forever -usepw -nodpms

Poi ho scoperto le meraviglie di ssh ed xpra. Se hai gia' un server ssh installato magari se vuoi dargli un occhio.