Peter Doshi ()
Tue, 31 Mar 1998 17:16:44 -0500
Well, I've never gotten the same windows machine to control itself, so
let's rule that out. After that, If you're getting a 'connection
refused' it probably means that it's not even getting to talk to VNC so
somehow it's not finding the IP:port
What kind of IP addresses are you using? (see below,too)
> Also, the viewer at home couldn't find the server until I added its name
> and IP address to C:/windows/hosts - if that is expected then it should
> be in the "getting started".
It won't find the server if you're using IP addresses which appear on
the net. Obviously, if the Ip address you're using appears on the net,
your vncviewer is going to try to access some other machine.. There are
some private, reserved networks, through, for instance, the 192.168.*.*
and 10.*.*.* are reserved. If your network isn't setup in that fashion
and is local and *does not* appear on the internet, then either set it
up with reserved addresses OR put it in c:\windows\HOSTS
So, it sounds like we're dealing with a networking problem and not a VNC
one... did you try pinging the address? If the ping goes to the right
machine, then try VNC on it.
Peter
This archive was generated by on Wed Feb 03 1999 - 15:33:11 GMT