VNC connection closed unexpectedly

From: Glen Gunselman (Gunselmg_at_emporia.edu)
Date: 09/26/05

  • Next message: Bhavesh Shah: "Jumpstart Issue" 
    Date: Mon, 26 Sep 2005 15:45:32 -0500
To: <sunmanagers@sunmanagers.org>

    Help. I've been working on this off and on for several weeks and now
    I'm down to the wire and need to make it work ...
     
    I'm trying to get tightVNC server ( 1.2.8,REV=2003.04.27 from
    BlastWave) running on a test server (V490 - Solaris 9). Opening the
    vncviewer (RealVNC 4.1.1.0 on Windows XP) gets error - "The Connection
    Closed Unexpectedly Do you wish to attempt to reconnect to
    localhost:1?".
     
    Here's the server side log file:
     
    robin ~ gunselmg $cat .vnc/robin\:1.log
    23/09/05 19:42:22 Xvnc version 3.3.tight1.2.8
    23/09/05 19:42:22 Copyright (C) 1999 AT&T Laboratories Cambridge.
    23/09/05 19:42:22 Copyright (C) 2000-2002 Constantin Kaplinsky.
    23/09/05 19:42:22 All Rights Reserved.
    23/09/05 19:42:22 See http://www.uk.research.att.com/vnc for
    information on VNC
    23/09/05 19:42:22 See http://www.tightvnc.com for TightVNC-specific
    information
    23/09/05 19:42:22 Desktop name 'X' (robin:1)
    23/09/05 19:42:22 Protocol version supported 3.3
    23/09/05 19:42:22 Listening for VNC connections on TCP port 5901
    23/09/05 19:42:22 Listening for HTTP connections on TCP port 5801
    23/09/05 19:42:22 URL http://robin:5801
    _FontTransSocketINETConnect: Can't connect: errno = 146
    failed to set default font path 'tcp/localhost:7100'
    Fatal server error:
    could not open default font 'fixed'
    23/09/05 19:42:23 Xvnc version 3.3.tight1.2.8
    23/09/05 19:42:23 Copyright (C) 1999 AT&T Laboratories Cambridge.
    23/09/05 19:42:23 Copyright (C) 2000-2002 Constantin Kaplinsky.
    23/09/05 19:42:23 All Rights Reserved.
    23/09/05 19:42:23 See http://www.uk.research.att.com/vnc for
    information on VNC
    23/09/05 19:42:23 See http://www.tightvnc.com for TightVNC-specific
    information
    23/09/05 19:42:23 Desktop name 'X' (robin:1)
    23/09/05 19:42:23 Protocol version supported 3.3
    23/09/05 19:42:23 Listening for VNC connections on TCP port 5901
    23/09/05 19:42:23 Listening for HTTP connections on TCP port 5801
    23/09/05 19:42:23 URL http://robin:5801
    /usr/openwin/bin/xrdb: No such file or directory
    /usr/openwin/bin/xrdb: can't open file '/home/gunselmg/.Xresources'
    xterm: fatal IO error 32 (Broken pipe) or KillClient on X server
    "unix:1.0"

     
    (Note: TightVNC is running on two production servers and does work from
    the Windows box in question.)
     
    Thanks,
     
    Glen Gunselman
    Systems Software Specialist
    TCS
    Emporia State University
    _______________________________________________
    sunmanagers mailing list
    sunmanagers@sunmanagers.org
    http://www.sunmanagers.org/mailman/listinfo/sunmanagers

  • Next message: Bhavesh Shah: "Jumpstart Issue"

    Relevant Pages

    • Re: VNC Problem
      ... 01/10/2004 18:24:45 Listening for VNC connections on TCP port 5901 ... 01/10/2004 18:24:45 Listening for HTTP connections on TCP port 5801 ...
      (comp.os.linux.networking)
    • share problems
      ... I could not add computers to the domain and I could not access a shared folder on a Windows 2008 Server from Vista and XP 64. ... If I choose diagnose it will say the the computer "is not set up to establish a connection on port "File and printer sharing " with this computer. ... NOT LISTENING ... TCP port 445: ...
      (microsoft.public.windows.server.general)
    • VNC connection closed unexpectedly
      ... BlastWave) running on a test server. ... 23/09/05 19:42:22 Listening for VNC connections on TCP port 5901 ... 23/09/05 19:42:22 Listening for HTTP connections on TCP port 5801 ...
      (comp.unix.solaris)
    • VNC connection closed unexpectedly
      ... BlastWave) running on a test server. ... 23/09/05 19:42:22 Listening for VNC connections on TCP port 5901 ... 23/09/05 19:42:22 Listening for HTTP connections on TCP port 5801 ...
      (comp.sys.sun.admin)
    • TCP port 135 (epmap service): NOT LISTENING
      ... it was first discovered by failing to log into DHCP mmc on that server ... TCP port 135 (epmap service): NOT LISTENING ...
      (microsoft.public.windows.server.active_directory)