![]() See X server insecure (must use xauth-style authorization). McC: Or try simply running this: xhost +localhost Check that the computer name resolves to the correct IP address e.g. This error usually occurs when the IP address belongs to a different network to the network VNC Viewer is running on. I don't know if it's a good idea, but the problem went away.Īh! This also works (just needs to be done once): # xauth merge /home/luc/.Xauthorityĭ. VNC Viewer does not have a network route to connect to the specified computer name/IP address. What worked for me (as root): # cp /home/luc/.Xauthority /home/root/ Xauth: (argv):1: unable to read any entries from file "(stdin)" Luc/> ssh -l luc localhost xauth extract - $DISPLAY | xauth merge. Xauth: error in locking authority file /home/luc/.Xauthority LES: That doesn't work for me on Ubuntu 10.10: luc/> xauth extract - $DISPLAY | xauth merge. If you don't have ssh, try rsh or whatever you use to execute a remote command. Where USERID is the user that you logged in as HOST is the name of the host where you originally logged in $DISPLAY is just $DISPLAY - the DISPLAY environment variable. Often the correct magic is ssh -l USERID HOST xauth extract - $DISPLAY | xauth merge. On the machine where you originally logged in, as the same user, do xauth extract - $DISPLAYĪnd pipe the result of that into xauth merge -Īs the user you now are on the machine where you now are. Ping works on both Windows hosts with IP or hostname. This is one of the few cases where there's actually an application for the xauth command. Could not open connection to the host, on port 5901: Connect failed And neither RealVNC nor TightVNC will connect (using hostname or IP). xauth in the home directory that contains the required magic cookie that you need to access the display. If you see this message when trying to connect from VNC Viewer, please check the following. This isn't a catastrophe, as long as you can become that user. Xtigervnc is the X VNC (Virtual Network Computing) server. The most likely explanation is that you're not logged in as the same user as when you entered your name and password to the display manager or ran x11start (startx, whatever your command is that starts the X server). ![]() You've successfully locked down your X server, and discovered that you've locked yourself out. ![]() X server insecure (must use xauth-style authorization) Well, at least you're not getting the dreaded message Xlib: Client is not authorized to connect to ServerĪpplication initialization failed: couldn't connect to display "host.domain:0.0" Purpose: Help users deal with the problem if launching a Tk application reports: Xlib: connection to "host.domain:0.0" refused by server ![]()
0 Comments
Leave a Reply. |