Bonjour,

Voici ma configuration:
1 modem routeur adsl netgear
2 pc fixe avec debian testing, on vas dire pc.A et pc.B
1 pc portable avec debian instable on vas dire pc.C
Le tout en ip fixe sans proxy

Le but et que le pc.A ce connecte au pc.B ou C avec x11vnc (directement sur le bureau utilisateur) via ssh.

Sur le pc.A la commande:
#ssh -L 5905:localhost:5901 pc B x11vnc -localhost -display :0
permet de lancer le serveur x11vnc sur le pc.B

Sur le pc.A la commande:
#vncviwer localhost:5
permet de s'y connecté via ssh.

Mon probleme est avec le pc C.

Sur le pc.A la commande:
#ssh -X -L 5900:localhost:5900 pc c x11vnc -localhost -display :0
me renvoi:
21/10/2006 11:45:09 x11vnc version: 0.8.2 lastmod: 2006-07-12
Xlib: connection to ":0.0" refused by server
Xlib: Invalid MIT-MAGIC-COOKIE-1 key

21/10/2006 11:45:09 ***************************************
21/10/2006 11:45:09 *** XOpenDisplay failed (:0)

*** x11vnc was unable to open the X DISPLAY: ":0", it cannot continue.
*** There may be "Xlib:" error messages above with details about the failure.

Some tips and guidelines:

* An X server (the one you wish to view) must be running before x11vnc is
started: x11vnc does not start the X server.

* You must use -display <disp>, -OR- set and export your DISPLAY
environment variable to refer to the display of the desired X server.
- Usually the display is simply ":0" (in fact x11vnc uses this if you forget
to specify it), but in some multi-user situations it could be ":1", ":2",
or even ":137". Ask your administrator or a guru if you are having
difficulty determining what your X DISPLAY is.

* Next, you need to have sufficient permissions (Xauthority)
to connect to the X DISPLAY. Here are some Tips:

- Often, you just need to run x11vnc as the user logged into the X session.
So make sure to be that user when you type x11vnc.
- Being root is usually not enough because the incorrect MIT-MAGIC-COOKIE
file will be accessed. The cookie file contains the secret key that
allows x11vnc to connect to the desired X DISPLAY.
- You can explicity indicate which MIT-MAGIC-COOKIE file should be used
by the -auth option, e.g.:
x11vnc -auth /home/someuser/.Xauthority -display :0
x11vnc -auth /tmp/.gdmzndVlR -display :0
you must have read permission for the auth file.

- If NO ONE is logged into an X session yet, but there is a greeter login
program like "gdm", "kdm", "xdm", or "dtlogin" running, you will need
to find and use the raw display manager MIT-MAGIC-COOKIE file.
Some examples for various display managers:

gdm: -auth /var/gdm/:0.Xauth
kdm: -auth /var/lib/kdm/A:0-crWk72
xdm: -auth /var/lib/xdm/authdir/authfiles/A:0-XQvaJk
dtlogin: -auth /var/dt/A:0-UgaaXa

Only root will have read permission for the file, and so x11vnc must be run
as root. The random characters in the filenames will of course change,
and the directory the cookie file resides in may also be system dependent.
Sometimes the command "ps wwaux | grep auth" can reveal the file location.

La seul solution est de taper:
#xhost +
sur ce pc et, en plus il faut le faire physiquement, se déplacer (un comble) car via ssh il me renvoi l'erreur:

connect PC.C port 6000: Connection refused
X connection to localhost:10.0 broken (explicit kill or server shutdown).

Donc si sa marche pour un PC sa doit marcher pour l'autre, mais qu'est-ce qui cloche???

Si quelqu'un à une petite idée.
Merci

Poste le Saturday 21 October 2006 18:22:02