Remote Administration with openSUSE 12.3

English Applications
#1

Hey guys,

I enabled this, configured /etc.xinet.d/vnc to use 5901 with my username, created a vnc password using vncpasswd for my user, but when I try to connect it says:

no password configured for vnc auth

What else do I need to do?

Thanks,

#2

So I am no expert on desktop remote control, but I just used VNC/Krfb to remote an openSUSE 12.3 KDE desktop to an openSUSE 12.2 PC running VNC/Remmina and it worked just fine. ON the openSUSE 12.3 I did three things:

  1. Enabled Services in Firewall for VNC:

http://paste.opensuse.org/view/download/29631534

  1. I enabled VNC from Terminal:
vncserver :1
  1. I fired up Krfb and configured as seen here:

http://paste.opensuse.org/view/download/83636332

  1. Opened up Remmina on remote openSUSE 12.2 (where VNC had already been setup and Firewall opened)

http://paste.opensuse.org/view/download/41721770

And it all works like a champ. So perhaps you are missing a step or two?

Thank You,

#3

Hello James,

I followed your instructions, and it sucks this way, I configured Krfb to “NOT TO ASK BEFORE ACCEPTING CONNECTIONS”, but when I checked if it worked, I never got my desktop on the remote computer, what I did get was the question asking me to allow the connection I opened from the Remote computer, even though this was turned off.

What happened with the previous way OpenSUSE had in 12.2 that one worked perfectly fine?

Thanks anyway.

#4

Since this procedure does work, there must be some detail that is not correct on your setup. Don’t forget the firewall setting on both PC’s. I can say that it did not work in openSUSE 12.3 RC2 for me, but does work in final. I did a clean install on all PC’s I used this on and it does work between openSUSE 12.2 and 12.3 in both directions. I only use KDE and always load a desktop. It may be time to post some terminal sessions so we can see and/or screen captures pasted here: SUSE Paste ( Why not save it as a file and post it here: SUSE Paste, select image over code (top right), set delete after to never,keep image under 512 meg, Gwenview is great is resizing images when needed. Post a link to the image in your next message).

Thank You,

#5

Both of the firewalls are turned off, also, this what I’m trying to connect:

Server: OpenSUSE 12.3 using Remote Adminitration (so I can login using VNC Client)
Client: Windows 7 Machine using VNC Client

With OpenSUSE 12.2 I could Login from a VNC session, but with 12.3 and the instructions that James posted I need to leave my user logged on to get the connection, I don’t want/need that, what I need is to be able to **login **to my OpenSUSE server using VNC Client using port 5901 or suseserver:1 for my user configured in /etc/xinet.d/vnc, but this is giving me the no password error which also exist in my user’s $HOME/.vnc

Thanks

#6

So from the Windows 7 computer using a VNC client, are you expecting to remote in using a terminal session or to remote a KDE or GNOME desktop?

Thank You,

#7

I am using KDE, since GDM has not worked for me, I already reported a bug with GDM with OpenSUSE and GNOME, but I don’t know how far it’s gone.

#8

So, to get to the point of the question, you are trying to remote control a KDE desktop, version 4.10 running in openSUSE 12.3 using a VNC client run from a Windows 7 PC. The primary differences from older openSUSE versions is a newer kernel and a newer KDE version in openSUSE 12.3 and perhaps the VNC version as well. The fixes may require a newer version of VNC in Windows 7. What is the version and source of your Windows 7 VNC client and can it be updated? In openSUSE 12.3, upgrading anything is a problem with such a new product, but I would suggest a kernel update because it can cause video issues, though there is no indication video is the problem in this case. Can you find a newer VNC client for Windows that is suggested to work with KDE 4.10? You can find a way to upgrade your kernel version here: openSUSE and Installing New Linux Kernel Versions - Blogs - openSUSE Forums

Thank You,

#9

I tried with 2 versions of VNC, (VNC Clients from RealVNC and TightVNC), both latest versions of it, both gave me the same no password error, any other ideas?

#10

And the new kernel idea? What about that one?

Thank You,

#11

I just downloaded TightVNC, a free download, installed it into a Windows 8 PC. I followed my Instructions on the openSUSE 12.3 and used TightVNC on the other and it is working like a champ. It makes me think you have set something wrong on one side or the other. For instance, I had to muddle through the settings in TightVNC before I found the working combination, which is working with the Firewalls on on both sides, which is highly recommended.

Free, Lightweight, Fast and Reliable: Download TightVNC

Thank You,

#12

I’m sorry James, your instructions work, they just don’t work for me because you need to be logged in to OpenSUSE to work I want it to be where you’ll get KDM or GDM asking you for your username and password connecting to opensuse:1 (vnc1 on /etc/xinet.d/vnc) instead of having to leave a session opened in OpenSUSE.

I hope I did make myself clearer this time.

By the way, thanks for the link fro S.A.C.K.S. I was looking for it couple of weeks ago.

#13

On a PC I want to remote into, I have it autostart directly into the desktop. And in general, users remote into a desktop already loaded or you do everything in terminal, with no desktop loaded at all. I am not sure of a setup designed to work and switch between terminal and desktop though I wonder if starting with a terminal session and using it to launch a desktop and then switch to a graphic remote desktop is possible? If the PC is yours, have it go straight into a desktop is my suggestion as I do that for my disabled wife’s remote PC so I can help start something for her. If the PC is not yours, some inconvenience will be required to remotely do what you want.

Of course, others reading here are free to come in with a solution if they have one.

Thank You,

#14

On 2013-03-28 17:06, jdmcdaniel3 wrote:
>
> jurgen73;2542169 Wrote:
>> I’m sorry James, your instructions work, they just don’t work for me
>> because you need to be logged in to OpenSUSE to work I want it to be
>> where you’ll get KDM or GDM asking you for your username and password
>> connecting to opensuse:1 (vnc1 on /etc/xinet.d/vnc) instead of having to
>> leave a session opened in OpenSUSE.
>>
>> I hope I did make myself clearer this time.
>>
>> By the way, thanks for the link fro S.A.C.K.S. I was looking for it
>> couple of weeks ago.
>
> On a PC I want to remote into, I have it autostart directly into the
> desktop.

That’s another usage. From times immemorial you could log in remotely
and open a new session as any user, from another computer. That’s why X
is a server/client setup.

This should work.

I don’t think the kernel is involved at all. I would suspect pam, the
window manager, the remote “client” (actually server in X parlance)…

–
Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

#15

I cannot believe that this is SO difficult, when there is a Yast ‘switch’ to turn this on.Why do they even bother to have the switch there, when you still have to jump though hoops to get everything to work??The answer is to just ignore it, install a VNC server independently, and configure.Thanks.

#16

I am having exactly the same issue. I have a number of SuSE 11.4 and 12.2 systems that I connect to from a Windows 7 client running tightVn using vnc on the remote system started via xinetd . I have a new SuSE 12.3 configured exactly the same way and I get the No password configured for vnc auth error no matter what I try. It does work if I login to the SuSE 12.3 system and manually start vncserver, which is difficult when the machines are three states away, and my only access is using vnc. Something has changed between 12.2 and 12.3

#17

Having the same problem as well. went from working 11.4 to 12.3. No password configured for VNC Auth.

#18

vi /etc/xinitd.d/vnc
add “securitytype=none” to server_args
change -query localhost to -query ipv4-localhost
:wq
vi /etc/hosts
add ipv4-localhost as alias to 127.0.0.1 localhost
:wq

restart xinitd /etc/init.d/xinitd restart
should work. woohoo or at least it did for me.

#19

Did all that but even though a VNC connection opens, it immediately closes saying:

“Connection has been gracefully closed”

And all that /var/log/xinetd says is connection started, connection closed, duration=0s or 1s

So more work needs to be done.

#20

I can suggest you another way if you are interested.

#zypper in x11vnc

and then add x11vnc -forever -display :0 in startup
This will not ask for any passwords.
You can then connect with any vnc viewer #vncviewer <ipaddress>