Error connection: More Information???

[Tim Robinson]

Ok, even more information,

The error I get is "Failed to Connect to the Server" from the client. This
occurs whether I use the IP address or the name of the machine.

Haven't tried telnet yet, but will do so.

By gone I mean that the tray icon is gone (it disappears on the first reboot
{see bug below}) and I get the "Failed to Connect to Server" message.

By nothing has worked, I mean the steps listed in the parenthesis. Regardless of
what I have tried, the error remains.

Actually, yes, policies do not apply to the supervisor account as nothing has
been disabled. This is so that I can get full control over WIN95 to repair the
misadventures of users.



James \"Wez\" Weatherall wrote:

> > I too an having this same problem, unfortunately, using the IP address
> instead
> > of the name still doesn't work. I can ping any machine on the network, but
> VNC
> > fails to connect to the server.
>
> What error message does the client print?  Can you telnet to port 5900 on
> the offending server?  What display/port number does the server claim to be
> listening on?
>
> > The interesting part of this is that I can
> > install VNC as a service, then reboot once, it is still there, reboot
> again
> > still there, reboot a third time and poof it is gone.
>
> What do you mean by "it is gone"?  The process is missing, the tray icon is
> gone, or what else?
>
> Check the
> HKEY_LOCAL_MACHINE/Software/Microsoft/Windows/CurrentVersion/Explorer/RunSer
> vices key on the offending machine - there should be an entry for WinVNC
> under there if it is installed as a service under Windows 95.
>
> > Then when I try to remove
> > the service, I get a message that "The service could not be removed",
> press "OK"
> > and then the message box "Service Successfully removed" comes up.  Another
> > interesting anomaly is that when I start the service, the icon is visible
> in the
> > system tray, however, when I reboot the icon disappears. Granted this is a
> > documented bug in the version 3.3.2r6, but I am wondering if the failure
> to
> > connect to the server is related to this bug.
>
> Very peculiar.  The message box thing is a sort of half-bug in the service
> uninstall code.  What it's indicating is that it failed to remove the key
> (see above) from the registry.  It's not clear whether this is because it
> couldn't be removed or because it didn't exist in the first place - it would
> be useful to reproduce the above situation and check for the key before
> trying to uninstall WinVNC.
> If the key is just randomly dissappearing when you reboot, this indicates a
> rogue policy setting or something seriously wrong with your registry data
> structures.
>
> > I have tried things like editing the registry to set default behavior
> (disable
> > properties, set password, set sockets etc), uninstalling and
> re-installling, but
> > nothing has worked.
>
> What do you mean by "nothing has worked"?  Do you mean you cannot connect
> from across the network?
>
> > This behavior regardless of the user login. I can login as a supervisor of
> the
> > network or as an end-user, either way, the same behavior occurs so I can
> rule
> > out policies in WIN95.
>
> Do policies not apply to network supervisors, then?  (I've never used Win95
> policies..)
>
> Cheers,
>
> James "Wez" Weatherall
> --
> - Queens' College MCR Entertainments Officer -
> Laboratory for Communications Engineering, Cambridge - Tel : 766513
> AT&T Labs Cambridge, UK                              - Tel : 343000
>
> ---------------------------------------------------------------------
> The VNC mailing list - see http://www.uk.research.att.com/vnc/intouch.html
> ---------------------------------------------------------------------

--
Tim Robinson                        Phone: 204-989-8999
Western Opinion Research Inc.       Fax:   204-947-2410
#806 - 213 Notre Dame Avenue        http://www.worinc.com



---------------------------------------------------------------------
The VNC mailing list - see http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------