Troubleshooting second connection

[James B. White]

To Telnet to it of course the telnet server must be installed and
running on the other machine.

I do recommend as a tool only
http://www.snapfiles.com/get/superscan.html this will let you see what
ports are open on the other machine.

Disable all Firewalls

Can you ping from machine 1 to machine 2

If you can, Try telneting to machine2 5900 - 
e.g. 

c:\> telnet machine2 5900

It will not work much, all you will see is "RFB 003.008" 
exit with ctrl ] then type quit, if it connects. If it does not or you
cannot ping then you have a network connectivity issue.

If it connects then try with the vncviewer.

Can you see machine2 from machine 1 in "my network places/entrire
network/ etc", or type \\machine2 in the address bar of windows
explorer.


James B. White
C.S.H. Consultants Pty Ltd
Phone....:+61(0)3 97151033
Fax......:+61(0)3 97151400
Mobile...:+61(0)418 558 184
 

-----Original Message-----
From: Michael Rosen [mailto:mrosen "at" gmail.com] 
Sent: Saturday, 8 January 2005 00:03
To: James Weatherall
Cc: James B. White; vnc-list "at" realvnc.com; Brian
Subject: Re: Troubleshooting second connection

I now think something else is causing the problem due to the fact that
I cannot even connect from machine #2 to #1.  I am running Windows XP
Home on both.  I did check the Windows Firewall last night and it had
been reenabled somehow.  I disabled it again but still no go.  I can't
even telnet to the first machine's port.


On Fri, 7 Jan 2005 11:23:58 -0000, James Weatherall <jnw "at" realvnc.com>
wrote:
> > On the second machine, did you check the connections network/mask
> > setting, i.e. +0.0.0.0/0.0.0.0, out of the box it seems to have just
a
> > "+", and I am note sure if this works. Set it the same as your
first.
> 
> "+" is equivalent to "+0.0.0.0/0.0.0.0", and verifiably works.
> 
> > all work together. I must say the principle of the concept of
multiple
> > connections to the same port e.g. port 80, from different
> > clients at the
> > same time escapes my understanding so - be assured I am no
> > TCP/IP guru.
> 
> Each connection has two "endpoints", each consisting of an IP address
& port
> pair.  Thus different connections made to the same server IP on the
same
> port are distinguished by the viewer IP and port from which they
originated.
> 
> > If the second (new) server is Win 2003 and you have terminal
services
> > (admin) running one it (or possibly even not), VNC does not
> > seem to know
> > what to connect to if it is running as a service, well that is my
> > experience, and if the server is not logged on, you can whistle
dixie.
> > Sometimes the viewer frame comes up, but just with a black
> > screen. Still
> > the website does not say that 4.0 works on 2003. There are also
issues
> > with XP if you are running fast user switching, sorry,
> > correction; there
> > are problems with VNC 4.0 if you are using XP with fast user
switching
> > (apparently it uses some features of terminal services to enable
> > multiple "sessions" on the one PC). I am told that version 4.1 has
> > resolved this, but, where do you get it.
> 
> VNC 4.1 will not resolve the fast user switching issue - this is an
issue we
> are working on a good method of resolving.  The problem is caused by
> "session zero" not being "connected".  Normally, "session zero" is
> "connected" to the local console.  Remote Desktop & Fast User
Switching &
> Windows 2003's "Console Connection" features can all result in
"session
> zero" being "disconnected", and so innaccessible to VNC Server.
> 
> If you get a machine into that state, there are ways to get session
zero
> connected to the console again, the simplest of which is to log on to
> session zero from the console of the machine (but of course that
requires
> local access...)
> 
> Cheers,
> 
> Wez @ RealVNC Ltd.