Link to home
Start Free TrialLog in
Avatar of andieje
andieje

asked on

can't run mysql workbench

Hi

I am connecting to a linux virtual machine from a windows xp machine via cygwin/x

mysql workbench wont start and i dont know what to do as I know nothing about x11 or xwin

:~# /usr/bin/mysql-workbench
** Message: Gnome keyring daemon seems to not be available. Stored passwords will be lost once quit
X11 connection rejected because of wrong authentication.

(mysql-workbench-bin:4438): Gtk-WARNING **: cannot open display: localhost:17.0


thanks
Avatar of AriMc
AriMc
Flag of Finland image

Are you connecting from cygwin/x to the virtual Linux via SSH?

If so, have you enabled X-forwarding with the command line option -X?

Avatar of andieje
andieje

ASKER

yes i connect with ssh -X
Avatar of andieje

ASKER

i tried almost everything in this link

http://www.cyberciti.biz/faq/x11-connection-rejected-because-of-wrong-authentication/

the ssh_config file did not have ForwardX11 yes. I added this line but it made no difference

I didnt do this line as i didnt know what it meant
ssh -X user@remote.box.example.com xeyes
ASKER CERTIFIED SOLUTION
Avatar of andieje
andieje

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Ok good, checking the X-forwarding permissions in the SSH-daemon configuration would've probably come next to my mind. :)

Avatar of andieje

ASKER

i don't know what any of these things mean. I'm a linux beginner. i dont know what x11 is or x forwarding of the difference between ssh -X and ssh -Y
When you start an application on a remote X-window server (like in your case), the server attempts to open a connection back to your local workstation. This connection is needed to open the application window on your workstation.

Normally in a local network this works fine. When you are connecting to a remote server with SSH things get tricky because there usually are several firewalls between you and the server preventing the connection. The SSH options -X and -Y are ways to overcome this. The basic option -X forwards calls from your remote X-server to your local workstation through the encrypted SSH-tunnel, but because of historical reasons, newer versions require more configuration to secure both ends of the communication from attackers. For this reason a more relaxed option -Y has been introduced to override those restrictions.

It's a bit complicated in all but that's because we live in a constant combat between users and illicit hackers.

Avatar of andieje

ASKER

i solved the problem myself