On Friday 09 December 2005 16:58, Mello wrote:

Hi Jerry, thanks for your prompt reply.

I went into YAST2/sysconfig editor and I believe I've found those settings you mentioned. Under the following hierarchy: Desktop -> Display manager I've checked: DISPLAYMANAGER = kdm DISPLAYMANAGER_REMOTE_ACCESS = yes DISPLAYMANAGER_ROOT_LOGIN_REMOTE = yes (this even scares me a bit) DISPLAYMANAGER_STARTS_XSERVER = yes

The problem still stays: no login manager in vncviewer.

Will be waiting for more ideas :)

THX, -mw Okay, DISPLAYMANAGER_ROOT_LOGIN_REMOTE allows you to login as Root when connecting via vnc. Choose your poison...

Several times I've found that specifically those options did take effect until I dropped to "init 3" and back to "Init 5", I usually reboot... Although It's a nono to say something like that about linux! Jerry

On Friday 09 December 2005 11:38, Mello wrote:

That's exactly what I'd done. First "init 3", then "init 5" and finally rebooted (must be the Win syndrome).

I've also checked /var/log/messages but couldn't find any error/alert (nor I expected to find any).

My googling continues... -mw

On 12/9/05, Jerry Westrick wrote:

...

On Friday 09 December 2005 16:58, Mello wrote:

...

Hi Jerry, thanks for your prompt reply. I went into YAST2/sysconfig editor and I believe I've found those settings you mentioned. Under the following hierarchy: Desktop -> Display manager I've checked: DISPLAYMANAGER = kdm DISPLAYMANAGER_REMOTE_ACCESS = yes DISPLAYMANAGER_ROOT_LOGIN_REMOTE = yes (this even scares me a bit) DISPLAYMANAGER_STARTS_XSERVER = yes

The problem still stays: no login manager in vncviewer. Will be waiting for more ideas :) THX, -mw

Okay, DISPLAYMANAGER_ROOT_LOGIN_REMOTE allows you to login as Root when connecting via vnc. Choose your poison... Several times I've found that specifically those options did take effect until I dropped to "init 3" and back to "Init 5", I usually reboot... Although It's a nono to say something like that about linux! Jerry

-- Do you have more than one net interface? I was running VNC successfully until I added another interface to do some testing, it caused the exact same thing as you have. I disabled the interface and all is well.

hth Mike

You are almost there - having enabled the remote option in Sax2, now open a terminal window, su to root, and execute vncpasswd to set the vnc password for the root user - once you do that, you will be able to VNC into the box. Mello wrote:

I do have a second network i/f in fact but it is shown as "Not configured" in YAST2 (Network Devices -> Network Card). What do exactly mean by "disabling"?

BTW, I've noticed that SaX2 has an "Allow Access... VNC Protocol" option. I've enabled that as well and now, when I try to access by browser (HTTP port 5801) I get until the VNC Authentication page but there it stops.

THX, -mw

On 12/9/05, ka1ifq wrote:

...

On Friday 09 December 2005 11:38, Mello wrote:

...

That's exactly what I'd done. First "init 3", then "init 5" and finally rebooted (must be the Win syndrome).

I've also checked /var/log/messages but couldn't find any error/alert

(nor

...

I expected to find any).

My googling continues... -mw

On 12/9/05, Jerry Westrick wrote:

...

On Friday 09 December 2005 16:58, Mello wrote:

...

Hi Jerry, thanks for your prompt reply. I went into YAST2/sysconfig editor and I believe I've found those

settings

...

you mentioned. Under the following hierarchy: Desktop -> Display manager I've

checked:

...

...

...

DISPLAYMANAGER = kdm DISPLAYMANAGER_REMOTE_ACCESS = yes DISPLAYMANAGER_ROOT_LOGIN_REMOTE = yes (this even scares me a bit) DISPLAYMANAGER_STARTS_XSERVER = yes

The problem still stays: no login manager in vncviewer. Will be waiting for more ideas :) THX, -mw

Okay, DISPLAYMANAGER_ROOT_LOGIN_REMOTE allows you to login as Root

when

...

...

connecting via vnc. Choose your poison... Several times I've found that specifically those options did take

effect

...

...

until I dropped to "init 3" and back to "Init 5", I usually reboot... Although It's a nono to say something like that about linux! Jerry

--

Do you have more than one net interface? I was running VNC successfully until I added another interface to do some testing, it caused the exact same thing as you have. I disabled the interface and all is well.

hth Mike

-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com

-- --Moby They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. -- Benjamin Franklin First they came for the Jews and I did not speak out because I was not a Jew. Then they came for the Communists and I did not speak out because I was not a Communist. Then they came for the trade unionists and I did not speak out because I was not a trade unionist. Then they came for me and there was no one left to speak out for me. -- Pastor Martin Niemöller

While I thank you all for the good comments I must admit that they didn't solve the issue so my googling went on... Eventually I have found an email thread which, although related to Suse 9.2, pointed me in the right direction: <snip> The fact that you are getting the screen with the X cursor indicates that the VNC Server program is working properly. The absence of a logon screen would indicate that KDM is not allowing XDMCP connections. </snip> You can find the message here: http://lists.suse.com/archive/suse-linux-e/2005-Apr/1049.html So, now my problem is SOLVED, I'll briefly recap what happened below: PROBLEM: 1. PC running Suse 10, VNC connection shows a grey screen but no login 2. YAST2: allow Remote Administration, make sure Port is Open In Firewall is checked 2a. at least service "vnc1" should be ON by default in xinetd (YAST2) 2b. Remote Administration should be actually allowed in Firewall (YAST2) SOLUTION: 2. su to root and "vi /etc/opt/kde3/share/config/kdm/kdmrc", at the bottom of the file look for "[Xdmcp]" section, right below it there should be "Enable=true" instead of "Enable=false" 3. don't forget to "rcxdm restart" Comments are welcome. Thanks, -mw NOTE: - "$defaultXStartup" defined in "/usr/X11R6/bin/vncserver" seems to be totally irrelevant (in fact KDE starts in my case despite "twm" is at line 63) - also SaX2, which has a VNC tab where one can enable/disable the service, doesn't seem to have any effects On 12/9/05, ka1ifq wrote:

On Friday 09 December 2005 12:52, Mello wrote:

...

I do have a second network i/f in fact but it is shown as "Not configured" in YAST2 (Network Devices -> Network Card). What do exactly mean by "disabling"?

Sorry, thats what I meant. I set mine to "not configured" and init3 / init5 and all was well again.

-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com