>Another very interesting item of note is that we can see the connection get
>established on the RH6.2 machine but we also see a connection from the
>RH6.2 machine to the Solaris machine on port 6002. So, it looks like we
>make a connection to the RH machine which then calls up a login script on
>my Solaris machine.
Very, very odd. The key files to watch are the ~/.vnc/*.log files on each
machine - delete all of these before an attempt, and see which one(s)
magically spawn files of this type after a single connection attempt to the
RH box.
If at all possible, can you isolate the Solaris machine from the network
and try connecting again? This might work, but if it doesn't it may yield
some extra information which could help narrow down the problem.
Failing that, isolate one of the RH boxes, add it's own hostname and IP to
/etc/hosts, and attempt to run a vncviewer connecting to itself. This
should yield similar results.
--------------------------------------------------------------
from: Jonathan "Chromatix" Morton
mail: [EMAIL PROTECTED] (not for attachments)
big-mail: [EMAIL PROTECTED]
uni-mail: [EMAIL PROTECTED]
The key to knowledge is not to rely on people to teach you it.
Get VNC Server for Macintosh from http://www.chromatix.uklinux.net/vnc/
-----BEGIN GEEK CODE BLOCK-----
Version 3.12
GCS$/E/S dpu(!) s:- a20 C+++ UL++ P L+++ E W+ N- o? K? w--- O-- M++$ V? PS
PE- Y+ PGP++ t- 5- X- R !tv b++ DI+++ D G e+ h+ r++ y+(*)
-----END GEEK CODE BLOCK-----
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
