RE : Starting VNCViewer by right clicking on Machine in Network

I have created the registry entries and the .cmd file described, but my Win2K system will not run the Viewer from a right click on the network name. The new startvnc.cmd file is located in the root directory (c:\). Win2K displays a window and reports that it cannot locate the file .exe, and

xp home limited user no vnc

Has anyone managed to connect to a VNC server running on xp home under a limited user?? It works fine under administrator, so i suspect it has something to do with the user not being able to open to port 5900. Any ideas? _ Protect

Blue screenwatch

A linux/tightvnc newbie here. I want to use tightvnc to link my win2k desktop to our mandrake linux server (internal network). I am sure I have a session, put in the password, and I have connection info which says I have a connection - but all I get is a blue screen with a watch cursor - not

Reset by peer

I'm connecting behind companys firewall (nat included) (XP - XP) and all goes well until i punch in the password.. java console gives this msg.. may b a n00b prob.. but so am i java.net.SocketException: Connection reset by peer: connect at java.net.PlainSocketImpl.socketConnect(Native

Re: Apparent socket problem

Elwin Green said: When I try run vncserver on the second machine, the Current User Properties has the Accept Socket Connections box unchecked. If I check it and start vncserver again, the box appears unchecked again. The same thing happens with the Default Local System Properties. When I

Re: Apparent socket problem

Elwin, Check that both machines have TCP setup correctly. If it seems to be setup OK but doesn't work then try removing and reinstalling the TCP stack. Cheers, Wez @ RealVNC Ltd. ___ VNC-List mailing list [EMAIL PROTECTED] To remove yourself from the

RE: Blue screenwatch

Please send replies to the list. Alan Dunn said: Thank you for responding. In the log I found this which looked like the problem zone: Fonttranssocketunixconnect: can't connect errorno=2 failed to set default font path 'unix/:7100' Fatal server error could not open default font fixed

Re: [suse 8 | vncviewer] F8 Not working...

Oh and btw, i just downmloaded 4.0b3 src and F8 works. any help with 4.0b4 would be appreciated. On Tue, 11 Nov 2003 [EMAIL PROTECTED] wrote: Hi All! I have 4.0b4, compiled from source, on SuSE linux 8.0. I am having trouble with the F8 menu not showing up... i tried doing a manual

Re: [suse 8 | vncviewer] F8 Not working...

On Tue, 11 Nov 2003 [EMAIL PROTECTED] wrote: Hi All! I have 4.0b4, compiled from source, on SuSE linux 8.0. I am having trouble with the F8 menu not showing up... i tried doing a manual modification of the .Xresources file to put in a custom menu (i used the sample), and it did not

Re: Can't connect to Win 2000 machine when remote computer is locked

Nigel Baker said: I cannot connect to the remote Windows 2000 machine if it has been locked using the Task Manager-Lock Computer function (remote computer is still logged on, just locked). If the computer is not locked then VNC works fine. Using version 3.3.7

Re: Can't connect to Win 2000 machine when remote computer is locked

The VNC server is running as a system service on the remote machine. I cannot connect to the remote Windows 2000 machine if it has been locked using the Task Manager-Lock Computer function (remote computer is still logged on, just locked). If the computer is not locked then VNC works fine. Using

RE : Can't connect to Win 2000 machine when remote computer is locked

Is VNC server registered as a service? -Message d'origine- De : Nigel Baker [mailto:[EMAIL PROTECTED] Envoyi : vendredi 14 novembre 2003 17:38 @ : [EMAIL PROTECTED] Objet : Can't connect to Win 2000 machine when remote computer is locked I cannot connect to the remote

DOS command window problem for Windows 2000

I have seen several people in the past commenting that they have no cursor control in DOS windows when using VNC. The only solution I saw was to click command prompt instead of Start..Run...cmd. This does not work for me. I am running VNC from Windows XP to log into a Windows 2000 machine.

Re: Can't connect to Win 2000 machine when remote computer is locked

The problem only seems to exist in Ver 3.3.7 of VNC. Use version 3.3.6 and it works fine. ___ VNC-List mailing list [EMAIL PROTECTED] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list

Re: [suse 8 | vncviewer] F8 Not working...

Lets see *Certain other companie$* have prompt service like that!! Thanks Tristan, it worked! On Fri, 14 Nov 2003, Tristan Richardson wrote: This sounds like a bug in the 4.0b4 unix viewer whereby the F8 menu won't pop up when either caps lock or num lock are on. The following simple patch