Troubleshooting second connection
James B. White
jimbo "at" csh.com.au
Fri Jan 7 09:04:00 2005
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.
You do not need a wide separation, one port is fine, remember there is
nothing physical about ports, they are just a logical figment of
imagination. One port is just as far away from the next numbered port as
one hundreds or thousands away. They are all on the same wire, they can
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.
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.
You could use a scanner (Superscan) from the first machine to the second
to see if its port 5900 (or 5901) is open, if it is, and you cannot
connect, then the problem is within VNC (connection mask). If you cannot
see the second from the first, problems are elsewhere. If they are on
the same subnet, try using the IP address from first to second, set
second box up as 5900, - box standard, and fiddle till you can get from
first box to second, then increment the port, and retry using w.x.y.z:1
or w.x.y.z:5901. Then try using the hostname, try a systematic approach,
changing one thing at a time.
Next make sure your firewall/portforward is set up 5900 to "first
ip":5900 and 5901 to "second ip":5901 - I do note that it is quite
acceptable to do a port switch on many firewalls so port 5900 goes to
"first ip":5900 and 5901 goes to "second ip":5900 - I have this set up
at one client and can get to all three workstations.
As to the Bleeding obvious, is the SP2 firewall enabled on the NEW
machine as well as MCAFEE? - just a thought
James B. White
C.S.H. Consultants Pty Ltd
Mobile...:+61(0)418 558 184
From: vnc-list-admin "at" realvnc.com [mailto:vnc-list-admin "at" realvnc.com] On
Behalf Of Michael Rosen
Sent: Friday, 7 January 2005 15:12
Cc: vnc-list "at" realvnc.com
Subject: Re: Troubleshooting second connection
Oh, based on previous advice from this list, I was told "localhost"
was good to use for testing. But I guess that was when I was testing
the java viewer on the same PC. Either way, I am also trying my IP.
On Fri, 7 Jan 2005 13:07:52 +0900, Brian <brianbreedlove "at" hotmail.com>
> based on what you wrote. you have two computers that you want to
> VNC. You are allowed to set each computers VNC server to listen to
> you wish. I have two computers that have realVNC installed and I
> through port 9559 and the other through 7575. On the listening
> you set the appropriate port. Then on the calling computer, you call
> based on the ip:port. Localhost shouldn't be used to call the VNC
> because that means you are connecting to the computer you are calling
> ----- Original Message -----
> From: "Michael Rosen" <mrosen "at" gmail.com>
> To: "Brian" <brianbreedlove "at" hotmail.com>
> Cc: <vnc-list "at" realvnc.com>
> Sent: Friday, January 07, 2005 12:54 PM
> Subject: Re: Troubleshooting second connection
> >I tried it and it didn't work. I'm testing on the other computer by
> > connecting to "localhost:6900".
> > On Thu, 6 Jan 2005 22:38:06 -0500, Michael Rosen <mrosen "at" gmail.com>
> >> Can I do that? I thought multiple connections had to be 5900+X?
> >> when I connect it would be "host:1". If I did as you say, would I
> >> just specify the hole port as "host:6900"?
> >> Thanks,
> >> Mike
> >> On Fri, 7 Jan 2005 11:44:31 +0900, Brian
<brianbreedlove "at" hotmail.com>
> >> wrote:
> >> > Michael,
> >> >
> >> > Try changing the ports so that there is a larger separation... In
> >> > words, try 5900 and 6900.
> >> >
> >> > ----- Original Message -----
> >> > From: "Michael Rosen" <mrosen "at" gmail.com>
> >> > To: <vnc-list "at" realvnc.com>
> >> > Sent: Friday, January 07, 2005 11:29 AM
> >> > Subject: Troubleshooting second connection
> >> >
> >> > >I currently have a VNC server running on my first computer
> >> > > on port 5900. I set up a new computer, installed VNC,
> >> > > to listen on port 5901, duplicated the router port forwarding
> >> > > new port and the new IP, and enabled the port in the McAfee
> >> > > But when I try to connect to the second computer I get "unable
> >> > > connect to host: Connection refused (10061)."
> >> > >
> >> > > Disabling the McAfee firewall does nothing either. I even get
> >> > > same error if I shut the other computer down. I can't figure
> >> > > what
> >> > > could be wrong.
> >> > >
> >> > > Any help would be appreciated.
> >> > >
> >> > > Thanks,
> >> > > Mike
> >> > > _______________________________________________
> >> > > VNC-List mailing list
> >> > > VNC-List "at" realvnc.com
> >> > > To remove yourself from the list visit:
> >> > > http://www.realvnc.com/mailman/listinfo/vnc-list
> > _______________________________________________
> > VNC-List mailing list
> > VNC-List "at" realvnc.com
> > To remove yourself from the list visit:
> > http://www.realvnc.com/mailman/listinfo/vnc-list
VNC-List mailing list
VNC-List "at" realvnc.com
To remove yourself from the list visit: