Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

*** Need help in connecting to VNC at Solaris 10 server ***

93 views
Skip to first unread message

underh20

unread,
Sep 29, 2010, 2:58:30 PM9/29/10
to
Our Solaris 10 server is running VNC Enterprise Edition 4.4.2.
Websphere admin (wasadmin) started up a new VNC session #2 :

wasadmin > /usr/local/bin/vncserver :2


# ps -ef | grep vnc

wasadmin 10570 1 0 16:45:27 ? 0:01 Xvnc :2 -
PasswordFile /export/home/wasadmin/.vnc/passwd -auth /export/home/
wasadmin

root 10571 10570 0 16:45:27 ? 0:00 Xvnc :2 -
PasswordFile /export/home/wasadmin/.vnc/passwd -auth /export/home/
wasadmin

wasadmin 10574 1 0 16:45:29 ? 0:00 vncconfig -iconic


User wasadmin resetted the VNC password :

wasadmin > /usr/local/bin/vncpasswd


Unfortunately, the wasadmin user still can't connect to VNC from the
VNC client.
Below is the content of server:2.log under the /export/home/
wasadmin/.vnc directory :

Could anyone assist me in resolving this connection issue ? Thanks,
Bill

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Xvnc Enterprise Edition E4.4.2 (r13160) - built Jun 16 2008 13:26:47
Copyright (C) 2002-2008 RealVNC Ltd.
See http://www.realvnc.com for information on VNC.
Underlying X server release 60900000, The X.Org Foundation


Tue Sep 28 16:45:26 2010
vncext: VNC extension running!
vncext: created VNC server for screen 0
TcpListener: listening on IPv4, port 5902
TcpListener: listening on IPv4, port 5802


Tue Sep 28 16:45:28 2010
Wed Sep 29 09:16:10 2010
Connections: connected: 172.27.175.52::4934
SConnection: Client needs protocol version 4.0
SConnection: Client requests security type RA2(5)
SecurityRA2: Local private key has 2048 bits
SecurityRA2: Remote public key has 2048 bits

Wed Sep 29 09:16:11 2010
SecurityRA2: using AES-128

Wed Sep 29 09:16:22 2010
SConnection: AuthFailureException: Either the username was not
recognised, or
the password was incorrect
Connections: disconnected: 172.27.175.52::4934 (Either the username
was not
recognised, or the password was incorrect)

Wed Sep 29 09:42:48 2010
Connections: connected: 172.27.175.52::1882
SConnection: Client needs protocol version 4.0
SConnection: Client requests security type RA2(5)
SecurityRA2: Local private key has 2048 bits
SecurityRA2: Remote public key has 2048 bits
SecurityRA2: using AES-128

Wed Sep 29 09:42:54 2010
SConnection: AuthFailureException: Either the username was not
recognised, or
the password was incorrect
Connections: disconnected: 172.27.175.52::1882 (Either the username
was not
recognised, or the password was incorrect)

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Oscar del Rio

unread,
Sep 29, 2010, 3:54:01 PM9/29/10
to
On 09/29/10 02:58 PM, underh20 wrote:

> wasadmin> /usr/local/bin/vncserver :2

> User wasadmin resetted the VNC password :
>
> wasadmin> /usr/local/bin/vncpasswd
>
>
> Unfortunately, the wasadmin user still can't connect to VNC from the
> VNC client.

> SConnection: AuthFailureException: Either the username was not


> recognised, or
> the password was incorrect

Just a wild guess: perhaps the vncserver needs to be restarted so that
it re-reads the password file?

underh20

unread,
Sep 29, 2010, 4:19:47 PM9/29/10
to

Good suggestion Oscar. We restarted vncserver few times but still not
working :-(

diti

unread,
Sep 29, 2010, 5:40:08 PM9/29/10
to

Hi

I'll check access rights for your user wasadmin and focus on remote
access;
anyway what did U find in logs on U;'r server ...?

brgrds
marcin

0 new messages