Wez, I have done this about 20 times. Even after you provided the switches to get a log file, that is exactly what happened, it opened, asked for the IP address, I provided that and then it flashed a very brief (almost unreadable) "trying to connect" message, and leaving an instance of VNC running each time I tried this. I did not have a C:\Temp dir and the switch did not create one to place the log file in.
I then created a temp dir, but it was in the c:\Program Files\ directory, at which point the symptoms changed. The log file was still not created of course, because the temp dir was in the wrong place, but it began to leave a message window open - "Attempting to connect to host", which eventually timed out and popped up "unable to connect to host: Connection timed out (1006). I then discovered the wrong location of the temp dir and created one in c:\ at which point the log file was created. Something has changed. I went back and deleted the C:\Temp as well as the c:\Program Files\Temp dir. To see if the message went back to a brief flash. The VNC still pops up and leaves the error message up (attempting to connect), and does not leave an instance running but not visible. What was happening originally is something I can't help you with. I can tell you that it only occurred when attempting to connect with the sister-in-law's machine, i.e. I have always been able to vnc in to my client from the same laptop. Now I still have to figure out why I can't connect, but at least the "can't connect" message stays up and doesn't leave an invisible instance of vnc running every time. I am attempting to connect within the network (over a wireless router) to machine 192.168.0.2 running the VNC4 Server. The server IS at local IP 192.168.0.2 according to IPConfig on that machine. OK... It appears that the machine is "powering down" or going into a sleep mode. When I go up and wiggle the mouse, the machine comes up and then I log on. After that I get the same symptoms described initially, i.e. it asks for the IP address but then just creates an invisible instance of VNC4 viewer. Is it possible it has to do with "fast user switching stuff" on XP? There are two users defined and when the computer comes out of sleep mode (wiggle the mouse) I have to select one of the two users but seem to be instantly at the desktop for that user, whereas on my laptop machine after keying in my password it takes a minute or so to "finish booting". At any rate... The following is the current contents of the log file after one attempt to connect, leaving an invisible instance: Fri Apr 22 21:20:22 2005 Config: set immutable Log main: unable to close console:87 Registry: duplicated 80000001 to 80000001 RegConfig: unable to process dummy Threading: created RegConfig(8c6f50) Registry: duplicated 7bc to 7b4 Registry: duplicated 80000001 to 80000001 MsgWindow: creating window "CViewManager" Threading: started RegConfig(8c6f50) RegConfig: RegReaderThread started RegConfig: waiting for changes MsgWindow: null _this in 25007a, message 24 MsgWindow: null _this in 25007a, message 81 MsgWindow: null _this in 25007a, message 83 MsgWindow: created window "CViewManager" (25007a) Threading: created Native(8c57e0) Threading: created CView(8c5840) Threading: started CView(8c5840) MsgWindow: creating window "Clipboard" MsgWindow: null _this in e0104, message 24 MsgWindow: null _this in e0104, message 81 MsgWindow: null _this in e0104, message 83 MsgWindow: created window "Clipboard" (e0104) Clipboard: local clipboard changed by 105be Clipboard: no clipboard notifier registered Clipboard: registered clipboard handler CView: null _this in 1c00d2, message 36 CView: null _this in 1c00d2, message 129 CView: null _this in 1c00d2, message 131 CView: created window "VNC Viewer 4.0b" (1c00d2) Fri Apr 22 21:20:24 2005 Threading: created ConnectingDialog(f3fecc) Threading: started ConnectingDialog(f3fecc) Threading: joining ConnectingDialog(f3fecc) Threading: stopped ConnectingDialog(f3fecc) Threading: checking ConnectingDialog(f3fecc) Threading: joined ConnectingDialog(f3fecc) Threading: destroying ConnectingDialog(f3fecc) Threading: already joined ConnectingDialog(f3fecc) Threading: destroyed ConnectingDialog(f3fecc) John W. Colby www.ColbyConsulting.com Contribute your unused CPU cycles to a good cause: http://folding.stanford.edu/ -----Original Message----- From: James Weatherall [mailto:[EMAIL PROTECTED] Sent: Friday, April 22, 2005 11:15 AM To: 'John W. Colby' Subject: RE: VNC Client doesn't display John, I'm afraid I'm very confused now. Originally, you said that VNC Viewer briefly popped up the Connecting dialog and then took it away again, but did not quit. Your log output indicates that it is indeed trying to connect and is then failing, putting up an error message indicating that the host to which you are trying to connect is not contactable within the specified timeout, and then quitting. Can you clarify what the actual problem is that you are seeing? Have you checked whether you can telnet to port 5900 on the problem machine? BTW, we seem to have gone off-list - please remember to use Reply-To-All to ensure that correspondence is Cced to the mailing list, for the benefit of others! Cheers, Wez @ RealVNC Ltd. > -----Original Message----- > From: John W. Colby [mailto:[EMAIL PROTECTED] > Sent: 22 April 2005 16:07 > To: 'James Weatherall' > Subject: RE: VNC Client doesn't display > > VNC is shutting down now though, not putting an invisible > instance in the > process list. > > John W. Colby > www.ColbyConsulting.com > > Contribute your unused CPU cycles to a good cause: > http://folding.stanford.edu/ > > -----Original Message----- > From: James Weatherall [mailto:[EMAIL PROTECTED] > Sent: Friday, April 22, 2005 10:51 AM > To: 'John W. Colby' > Subject: RE: VNC Client doesn't display > > > John, > > You will definitely get a log file created in > C:\temp\vncviewer4.log with > the command-line I provided, unless you do not have access rights to > C:\temp. Are you sure you have rights to create files in C:\temp? > > Regards, > > Wez @ RealVNC Ltd. > > > > -----Original Message----- > > From: John W. Colby [mailto:[EMAIL PROTECTED] > > Sent: 22 April 2005 15:41 > > To: 'James Weatherall' > > Subject: RE: VNC Client doesn't display > > > > I shut down the Sygate firewall on both machines. Checked and the > > server is monitoring port 5900. > > > > I tried running with the log switch but no log file was created with > > the filename vncviewer4.log. I searched the whole hard disk. > > > > I'm still getting the same thing happening. VNC Opens, flashes a > > VERY brief message (can't really read it) "attempting to connect" > > then "goes away". It > > is in the task manager process list but not visible. > > > > BTW, I am trying it from inside the local LAN using > 192.168.0.2 as the > > server machine address and the same thing happens. This eliminates > > all trips through the firewall, over the internet etc. > > > > John W. Colby > > www.ColbyConsulting.com > > > > Contribute your unused CPU cycles to a good cause: > > http://folding.stanford.edu/ > > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > On Behalf Of James Weatherall > > Sent: Friday, April 22, 2005 6:15 AM > > To: 'John W. Colby'; [email protected] > > Subject: RE: VNC Client doesn't display > > > > > > John, > > > > Which versions of VNC Viewer and Server are you running on the two > > machines? > > > > Are you sure that you are not telling VNC Viewer to connect to the > > HTTP port on the server (port 5800)? This could cause the behaviour > > you describe, > > since the server would then be waiting for HTTP data and the > > viewer for an > > RFB initialisation message, and so neither would proceed. > > > > You can run VNC Viewer 4 with the command-line: > > > > Vncviewer.exe -log=*:file:100 > > > > which will cause it to write verbose output to > > C:\temp\vncviewer4.log, which you can then check to see what the > > last few messages are when it is running > > but not presenting you with a dialog. > > > > There is no "vnc.exe" in the VNC distribution, so adding that as an > > exception to Sygate won't help. > > > > Regards, > > > > Wez @ RealVNC Ltd. > > > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > > > On Behalf Of John W. Colby > > > Sent: 22 April 2005 02:20 > > > To: [email protected] > > > Subject: VNC Client doesn't display > > > > > > I am trying to setup VNC to run on my sister-in-law's computer so > > > that I can do tech support. Windows XP Home on her > machine, Windows > > XP Pro on my > > > laptop. > > > > > > I set up no-ip.com so that there is a dynamic tracking of her IP > > > address. I set up the VNC server on her machine and it seems to be > > > running. I set up > > > the firewall to do port forwarding to her machine I run the > > > client on my > > > laptop and attempt to connect to her machine. > > > > > > I have a couple of issues, but the immediate issue is that the > > > client runs, doesn't give any error message, but also > doesn't pop up > > > the login screen, > > > nor display anything at all. If I look in Task manager, > > VNC Client is > > > running in the Processes tab but NOT in the Applications tab. If > > > I try to start it again, connecting to her machine, ANOTHER copy > > > of the VNC viewer > > > opens, does not display, but appears in Task Manager. If I > > > run it again, > > > and connect to a client where I VNC in all the time, ANOTHER > > > copy opens, > > > displays the login screen, and allows me access to the > > > desktop of my client. > > > Thus it appears that it is something to do with connecting to > > > the server on > > > her machine. > > > > > > I run Sygate personal on both my Laptop and on her > machine. It has > > > been in place and functioning on both machines for > months. IF I try > > > to log in to > > > her machine with the firewall running, I get a "can't find > > > the host" kind of > > > message from VNC, so I know that the VNC requests are getting > > > out to the > > > web, through the No-IP translation, back to her router, > > > THROUGH her router, > > > and are blocked by Sygate if it is running on her machine. > > > That in itself > > > is the other problem since I have VNC.EXE listed in Sygate as > > > "allowed", but > > > I need to tackle one problem at a time. I disable the Sygate > > > firewall on > > > her end and then the VNC client I am trying to connect > just silently > > > connects but will not display. > > > > > > Does anyone have a clue what is happening here? I have tried to > > > find these symptoms on Google but come up empty. > > > > > > TIA > > > > > > John W. Colby > > > www.ColbyConsulting.com > > > > > > Contribute your unused CPU cycles to a good cause: > > > http://folding.stanford.edu/ > > > _______________________________________________ > > > VNC-List mailing list > > > [email protected] > > > To remove yourself from the list visit: > > > http://www.realvnc.com/mailman/listinfo/vnc-list > > _______________________________________________ > > VNC-List mailing list > > [email protected] > > To remove yourself from the list visit: > > http://www.realvnc.com/mailman/listinfo/vnc-list _______________________________________________ VNC-List mailing list [email protected] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
