Greetings, One more, the blasted VNC was working last week on tuesday, after I was finished using it , I turned it off. On friday I turned it on again with yast, there were no errors, on screen or in the logs, but it didn't present the remote user with the kdm login screen. Instead it logged in directly to tvm. I have played around since then and now it fails to start with the same old error: ========================================================== chadlap:~ # rcxinetd restart Shutting down xinetd: done Starting INET services. (xinetd) failed chadlap:~ # tail -f /var/log/messages Dec 5 12:35:25 chadlap xinetd[20946]: removing uucp Dec 5 12:35:25 chadlap xinetd[20946]: removing vnc2 Dec 5 12:35:25 chadlap xinetd[20946]: removing vnc3 Dec 5 12:35:25 chadlap xinetd[20946]: removing vnchttpd1 Dec 5 12:35:25 chadlap xinetd[20946]: removing vnchttpd2 Dec 5 12:35:25 chadlap xinetd[20946]: removing vnchttpd3 Dec 5 12:35:25 chadlap xinetd[20946]: removing ftp Dec 5 12:35:25 chadlap xinetd[20946]: bind failed (Address already in use (errno = 98)). service = vnc1 Dec 5 12:35:25 chadlap xinetd[20946]: Service vnc1 failed to start and is deactivated. Dec 5 12:35:25 chadlap xinetd[20946]: 20946 {init_services} no services. Exiting... ============================================================ Looks like DNS but how do I fix it? If my hosts file is right, and so is my resolv.conf. But now check this out, If as a user I start Xvnc with vncserver start, it prompts for a passwd which is stored in ~user/.vnc/ There is a xstartup file in there, where I can change the default desktop to kde. It works but the KDM login is not presented but it logs into KDE as a different user and does not capture my current desktop, but if you logout, you have to run a vncserver -kill and a vncserver again to restart the session.. Has anyone got a solution, please.. The way it worked on tuesday was fine. User connects with vncviewer, a login screen is presented and the user logs in with his own username and passwd, and a new desktop session is spawned on display:2. What do you need from me? There are almost no config files for Xvnc and it is xinetd service. TIA Chadley
Chadley Wilson said:
Greetings,
One more, the blasted VNC was working last week on tuesday, after I was finished using it , I turned it off.
I know this isn't an answer to your VNC problem, but have a look at NX server and KNX client. This has been on the SuSE disks since 9.3 and works an absolute treat and cross platform clients are available. Clients for other platforms can be downloaded from www.nomachine.com as can the commercial version of NX server. Setting up the NX server is as simple as: nxsetup --install --setup-nomachine-key NX only uses SSH for it's connectivity and is inherently more secure than VNC and it's compression over slow links is phenominal. David -- David Bottrill david@bottrill.org www.bottrill.org Registered Linux user number 330730 Internet Free World Dialup: 683864
On Mon, 2005-12-05 at 11:34 +0000, David Bottrill wrote:
Chadley Wilson said:
Greetings,
One more, the blasted VNC was working last week on tuesday, after I was finished using it , I turned it off.
I know this isn't an answer to your VNC problem, but have a look at NX server and KNX client. This has been on the SuSE disks since 9.3 and works an absolute treat and cross platform clients are available.
Clients for other platforms can be downloaded from www.nomachine.com as can the commercial version of NX server.
Setting up the NX server is as simple as:
nxsetup --install --setup-nomachine-key
NX only uses SSH for it's connectivity and is inherently more secure than VNC and it's compression over slow links is phenominal.
David
Hi David, I gave this a try.. I like...a LOT.. GOOD on you mate, Do you prehaps, have a windows client of preference to recommend..? Thanks Chadley
On Monday 05 December 2005 12:47, Chadley Wilson wrote:
Hi David, I gave this a try.. I like...a LOT.. GOOD on you mate, Do you prehaps, have a windows client of preference to recommend..?
Thanks Chadley
Umm, I think there is a free one at www.nomachine.com Jerry... Ps. I've been trying to get NX setup to work and have constantly problems... I'll start a thread asking for your support this evening after work!
On Mon, 2005-12-05 at 12:53 +0100, Jerry Westrick wrote:
On Monday 05 December 2005 12:47, Chadley Wilson wrote:
Hi David, I gave this a try.. I like...a LOT.. GOOD on you mate, Do you prehaps, have a windows client of preference to recommend..?
Thanks Chadley
Umm, I think there is a free one at www.nomachine.com
Jerry...
Ps. I've been trying to get NX setup to work and have constantly problems... I'll start a thread asking for your support this evening after work!
Thanks 10 time buddy...:) Chadley
On Monday 05 December 2005 06:47, Chadley Wilson wrote:
On Mon, 2005-12-05 at 11:34 +0000, David Bottrill wrote:
Chadley Wilson said:
Greetings,
One more, the blasted VNC was working last week on tuesday, after I was finished using it , I turned it off.
I know this isn't an answer to your VNC problem, but have a look at NX server and KNX client. This has been on the SuSE disks since 9.3 and works an absolute treat and cross platform clients are available.
Clients for other platforms can be downloaded from www.nomachine.com as can the commercial version of NX server.
Setting up the NX server is as simple as:
nxsetup --install --setup-nomachine-key
NX only uses SSH for it's connectivity and is inherently more secure than VNC and it's compression over slow links is phenominal.
David
Hi David, I gave this a try.. I like...a LOT.. GOOD on you mate, Do you prehaps, have a windows client of preference to recommend..?
Thanks Chadley
The VNC on Suse (10) is TightVNC, and there is a windows client on the Suse dvd under /dosutils/tightvnc. I installed this and it works well. You will prob want to modify the default command line stuff on the windows end to include your login name, -u name if I remember correctly.
On Monday 05 December 2005 12:50, Chadley Wilson wrote:
Dec 5 12:35:25 chadlap xinetd[20946]: bind failed (Address already in use (errno = 98)). service = vnc1
It's not DNS, it's vnc1 already running (ports 5801 and 5901 in use). netstat -anp | grep 5801
On Mon, 2005-12-05 at 13:35 +0200, Silviu Marin-Caea wrote:
netstat -anp | grep 5801
Even if I disable vnc in yast2 xinetd and reboot and I usually run netstat -tulpen | grep Xvnc And I am sure it is dead or not running anywhere, still complains with this error, but what you say does make a alot of sense, it means there could be a lock file somewhere, I will hunt it down.. Shoot it and makesure it dies.. LOL! :} Thanks :) Chadley
participants (6)
-
Chadley Wilson -
David Bottrill -
James Knott -
Jerry Westrick -
ka1ifq -
Silviu Marin-Caea