Hello Scott. It seems to me that a problem of VNC port number 80 is complete. Here are details.
I found that my yesterday's source code wasn't completed: there was a restart of WinVNC but with previous registry settings only. I fixed that. I looked into the Vnc viewer source code and found: if we want to start Vnc viewer on the port number 80, then we have to use a command line *a.b.c.d:-5820*. Yesterday I wrote: > 2 - field *Accept Socket Connections* = checked out. > I reset WinVNC registry setting *SocketConnec*=1 by regedit.exe, > but every time if open that tab with *Display number* = 4294961476, > then I see *SocketConnect*=0 and > again *Accept Socket Connections* = checked out. Today I see that above #2 indicates that the port number is in useing by another application. Therefore I implemented following: After restarting of WinVNC with new registry settings (port number) Kaboodle performs a detection of result. There is a check like in "Vnc running auto detection" but only for single port on itself IP address - loopback "127.0.01" if WinVNC have "AllowLoopback" registry setting, or really itself IP address otherwise. If that check isn't successful, then Kaboodle shows a Messagebox *Failed to restart WinVNC on the port number XX.* *That port may be in use by another application.* *Please change that port number, or close that application.* Please let me know the exact text of that Messagebox. - Igor ----- Original Message ----- From: "Scott C. Best" <[EMAIL PROTECTED]> To: "Igor Kotelevsky" <[EMAIL PROTECTED]> Cc: "Kaboodle-devel" <[EMAIL PROTECTED]> Sent: Wednesday, September 04, 2002 9:43 PM Subject: Re: [Kaboodle-devel] Re: A problem of VNC port number 80 > Igor: > Sorry to keep replying to my own messages. :) I think > that #2 down below was a bug with the TridiaVNC service. For > some reason, a ghost of the service got stuck. Am trying to > repeat the situation, but no luck yet. So please ignore #2 > below. > But there is a #3. :) > > 3. Using the fport utility, I can see that WinVNC is running on > port 80. I use the PropPabel to change this to 180, and then > hit "Autostart". I use fport again, and it's still running on > port 80. > > thanks, > Scott > > PS: fport is here: http://www.foundstone.com/knowledge/proddesc/fport.html > > > > On Wed, 4 Sep 2002, Scott C. Best wrote: > > > Igor: > > Using the TridiaVNC viewer, I can connect to the service > > running on port 80 if I use "-5820" as the display number. It > > does *not* work if I use 59716. I'm going to try the two major > > flavors of VNC: the AT&T version, and the TightVNC version. I > > suspect that -5820 will work on both. If so, we should change > > how Kaboodle tries to start the viewer; the 59716 calculation > > might only be valid for unix versions. > > > > Or, alternatively, Kaboodle could try both -5820 and > > 59716 when connecting, and the user will never know. Whichever > > one works, works. > > > > -Scott > > > > On Wed, 4 Sep 2002, Scott C. Best wrote: > > > > > Igor: > > > I compiled and tested the latest stuff. I can confirm > > > that WinVNC *does* startup and listen to port-80. I used the > > > "fport" utility to see everything on my system and it's there. > > > Also, I ran "telnet 192.169.123.130 80" from a unix command > > > line, and it connected to the service (ie, I get the response > > > from the service: "RFB 003.003"). So the service is running. > > > > > > I am having difficult connecting to the service, but > > > I think that's a problem with my VNC viewer. The correct number > > > to put into the viewer is calculated like this: > > > > > > Display Number = [desired port number] - 5900 + 65536 > > > > > > So for port-80, it's Display number 59716. Is this how > > > Kaboodle calculates the display number for non-standard ports? > > > > > > Two other bugs to report: > > > > > > 1. When I set the display number in the PropTab to something > > > beyond the range of 0 to 99, the default position of the > > > Display/Port dropdown should be "port". Right now, the > > > default is always "Display". > > > > > > 2. When VNC is installed as a service, Kaboodle gets an error > > > when it tries to shut that service down. I also get an > > > error when I try to use the Task Manager to shut it down. > > > Weird. I need to use "Programs -> VNC -> Admin -> Remove > > > WinVNC Service" to get it to shut down. Since I'm logged > > > on as Administrator, I'm surprised I'd get any error > > > trying to shut down a service. > > > > > > Thanks for looking into these! > > > > > > -Scott > > > > > > > > > On Wed, 4 Sep 2002, Igor Kotelevsky wrote: > > > > > > > Hello Scott. > > > > I implemented an "Autostart Now" button to the server PropertyTab > > > > like you asked. > > > > You wrote: > > > > > Also, I want to make this change: users are still asking > > > > > for an easy way to get the VNC service to listen to port-80. > > > > I cannot VNC connect on port number 80. > > > > It does not matter "direct connection" or "Kaboodle tunnels". > > > > - I install WinVNC registry setting *PortNumber*=80, > > > > - I start Vnc viewer as "a.b.c.d:-5800", > > > > - I didn't see a successful VNC session. > > > > > > > > Also I see following things in the WinVNC property tab: > > > > 1 - field *Display number* = 4294961476. > > > > Of course the TCP port number 4294961476 isn't possible, > > > > but it looks like a value 80 - 5900 in "unsigned int" format; > > > > 2 - field *Accept Socket Connections* = checked out. > > > > I reset WinVNC registry setting *SocketConnec*=1 by regedit.exe, > > > > but every time if open that tab with *Display number* = 4294961476, > > > > then I see *SocketConnect*=0 and > > > > again *Accept Socket Connections* = checked out. > > > > > > > > I didn't know how it possible to VNC connects on port number 80. > > > > I have to know a valid WinVNC registry settings and > > > > a valid Vnc viewer command line for such connection. > > > > > > > > - Igor > > > > > > > > > > > > ----- Original Message ----- > > > > From: "Scott C. Best" <[EMAIL PROTECTED]> > > > > To: "Igor Kotelevsky" <[EMAIL PROTECTED]> > > > > Cc: "Kaboodle-devel" <[EMAIL PROTECTED]> > > > > Sent: Wednesday, September 04, 2002 3:32 AM > > > > Subject: Re: WinVNC log file > > > > > > > > > > > > > Igor: > > > > > Okay...what we could then do is have Kaboodle keep its > > > > > own logfile, which recorded the real source IP, using the same > > > > > timestamp that's in the WinVNC log file itself. KaboodlePad.exe > > > > > could then merge the two pieces of data. > > > > > > > > > > Also, I want to make this change: users are still asking > > > > > for an easy way to get the VNC service to listen to port-80. So > > > > > lets add an "Autostart Now" button to the server PropertyTab. If > > > > > the user does not have "Let Kaboodle auto start VNC" selected, > > > > > then this button is greyed out. If the user has it selected, when > > > > > they click it any running VNC service is stopped and VNC is then > > > > > restarted with the current settings. > > > > > > > > > > thanks, > > > > > Scott > > > > > > > > > > > > > > > On Tue, 3 Sep 2002, Igor Kotelevsky wrote: > > > > > > > > > > > Hello Scott. > > > > > > The thing you offer could be a best decision, but that not possible. > > > > > > The VNC server opens the log file in monopoly mode for writing. > > > > > > If Kaboodle tries to open that file for writing also, then > > > > > > the system error (error code 32) occurs > > > > > > "The process cannot access the file > > > > > > because it is being used by another process." > > > > > > > > > > > > - Igor > > > > > > > > > > > > ----- Original Message ----- > > > > > > From: "Scott C. Best" <[EMAIL PROTECTED]> > > > > > > To: "Igor Kotelevsky" <[EMAIL PROTECTED]> > > > > > > Cc: "Kaboodle-devel" <[EMAIL PROTECTED]> > > > > > > Sent: Tuesday, September 03, 2002 8:36 AM > > > > > > Subject: Re: WinVNC log file > > > > > > > > > > > > > > > > > > > Igor: > > > > > > > Was looking at this tonight. Would it be possible to > > > > > > > replace any occurances of 127.0.0.1 with the IP address of > > > > > > > the machine Kaboodle was tunneling from? That is, since it's > > > > > > > Kaboodle doing the tunneling, it should be able to report: > > > > > > > > > > > > > > - Connection Source: Kaboodle tunnelled from 192.168.1.129 > > > > > > > > > > > > > > That'd be more useful, clearly. Since other apps > > > > > > > besides Kaboodle can tunnel VNC connections, I was thinking > > > > > > > that we could have Kaboodle itself write directly into the > > > > > > > WinVNC.log file, using some specially tagged data, and then > > > > > > > KaboodlePad could look for that data when it saw 127.0.0.1. > > > > > > > > > > > > > > Interested in your thoughts. > > > > > > > > > > > > > > thanks, > > > > > > > Scott > > > > > > > > > > > > > > > > > > > > > On Mon, 19 Aug 2002, Igor Kotelevsky wrote: > > > > > > > > > > > > > > > Hello Scott. > > > > > > > > I found 2 problems of WinVNC log file. > > > > > > > > > > > > > > > > 1. If VNC server starts and finds that WinVNC.log file already > > > > exists, > > > > > > > > then VNC server renames current WinVNC.log file into WinVNC.log.bak > > > > > > file. > > > > > > > > If WinVNC.log.bak already exists, then VNC server removes current > > > > > > > > WinVNC.log.bak file. > > > > > > > > > > > > > > > > 2. I found that only debug level = 9 provides data about > > > > unsuccessful > > > > > > > > connections. > > > > > > > > But that data isn't sufficient. > > > > > > > > There absent information about *IP address* of unsuccessful > > > > connection - > > > > > > > > D:\ORL\vss\winvnc\vncServer.cpp : removing unauthorised client. > > > > > > > > I can guess that it was last attempt of connection only. > > > > > > > > But that not safely. > > > > > > > > > > > > > > > > You can see my changes of in the CVS server. > > > > > > > > KaboodlePad now shows data like next > > > > > > > > - Connection Start Time: Mon Aug 19 16:59:46 2002 > > > > > > > > - Connection Success: YES > > > > > > > > - Connection Source: 127.0.0.1 > > > > > > > > - Connection End Time: Mon Aug 19 16:59:57 2002 > > > > > > > > > > > > > > > > - Igor > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ----- Original Message ----- > > > > > > > > From: "Scott C. Best" <[EMAIL PROTECTED]> > > > > > > > > To: "Igor Kotelevsky" <[EMAIL PROTECTED]> > > > > > > > > Cc: "Kaboodle-devel" <[EMAIL PROTECTED]> > > > > > > > > Sent: Monday, August 19, 2002 9:43 AM > > > > > > > > Subject: Re: WinVNC log file > > > > > > > > > > > > > > > > > > > > > > > > > Igor: > > > > > > > > > I hope another debug level gives you what we need: a > > > > > > > > > timstamp, a viewer IP address, success status. > > > > > > > > > > > > > > > > > > On another note, I found a new bug. I installed Kaboodle > > > > > > > > > on a machine that has a VNC viewer installed, but not a VNC > > > > > > > > > server. Kaboodle wouldn't let me even "browse" for the viewer. > > > > > > > > > It probably just didn't find VNC in the registry and so greys > > > > > > > > > out every option. > > > > > > > > > > > > > > > > > > -Scott > > > > > > > > > > > > > > > > > > On Fri, 16 Aug 2002, Igor Kotelevsky wrote: > > > > > > > > > > > > > > > > > > > Hello Scott. > > > > > > > > > > You wrote: > > > > > > > > > > > what they *want* > > > > > > > > > > > to see in a "VNC log" is one entry per connection: > > > > > > > > > > I found that WinVNC.log file doesn't provide necessary data > > > > always. > > > > > > > > > > > > > > > > > > > > For example, I made only VNC scan port number. > > > > > > > > > > I found in the log file only 2 strings: > > > > > > > > > > - D:\ORL\vss\winvnc\vncSockConnect.cpp : accepted connection > > > > from > > > > > > > > > > 192.168.1.225 > > > > > > > > > > - D:\ORL\vss\winvnc\vncClient.cpp : client connected : > > > > 192.168.1.225 > > > > > > (1) > > > > > > > > > > I can't understand that above connection wasn't success. > > > > > > > > > > I can think that above connection continue. > > > > > > > > > > > > > > > > > > > > I'll research that problem. > > > > > > > > > > I'll try to use another *debug level* of WinVnc registry > > > > settings. > > > > > > > > > > (But as result of big debug level, WinVnc log file will be very > > > > > > big). > > > > > > > > > > > > > > > > > > > > - Igor > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ----- Original Message ----- > > > > > > > > > > From: "Scott C. Best" <[EMAIL PROTECTED]> > > > > > > > > > > To: "Igor Kotelevsky" <[EMAIL PROTECTED]> > > > > > > > > > > Cc: "Kaboodle-devel" <[EMAIL PROTECTED]> > > > > > > > > > > Sent: Thursday, August 15, 2002 9:31 PM > > > > > > > > > > Subject: Re: WinVNC log file > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Igor: > > > > > > > > > > > if we stay with #1, then I think we should modify > > > > > > > > > > > KaboodlePad.exe. I've asked many users, and what they *want* > > > > > > > > > > > to see in a "VNC log" is one entry per connection: > > > > > > > > > > > > > > > > > > > > > > --------------- > > > > > > > > > > > Connection Start Time: 15 Aug 2002, xx:yy:zz > > > > > > > > > > > Connection Success: YES/NO > > > > > > > > > > > Connection Source: 192.168.1.12 > > > > > > > > > > > Connection End Time: 15 Aug 2002, xx:yy:zz > > > > > > > > > > > --------------- > > > > > > > > > > > > > > > > > > > > > > So if we stay with #1, we should change how KaboodlePad > > > > > > > > > > > "parses" the information that WinVNC writes into the log file. > > > > > > > > > > > There's a lot of gunk in there. > > > > > > > > > > > > > > > > > > > > > > Your modifications to the "current working directory" > > > > > > > > > > > are good -- now Kaboodle at least knows where the file is > > > > > > > > > > > reliably. If it can't find the file, please change the > > > > messageBox > > > > > > > > > > > that comes up to read: "Please help Kaboodle find the file > > > > > > > > > > > "WinVNC.log". Right now, it doesn't say what filename the user > > > > > > > > > > > is supposed to browse for. > > > > > > > > > > > > > > > > > > > > > > Thanks! > > > > > > > > > > > > > > > > > > > > > > -Scott > > > > > > > > > > > > > > > > > > > > > > On Thu, 15 Aug 2002, Igor Kotelevsky wrote: > > > > > > > > > > > > > > > > > > > > > > > Hello Scott. > > > > > > > > > > > > I prefer thing #1 for WinVNC log file. > > > > > > > > > > > > Real WinVNC log file describes connections more fully. > > > > > > > > > > > > > > > > > > > > > > > > I looked into the source code of WinVnc and found following. > > > > > > > > > > > > WinVnc creates log file as "WinVNC.log" without any path. > > > > > > > > > > > > Therefore that file creates into the current working > > > > directory. > > > > > > > > > > > > > > > > > > > > > > > > Now before starting WinVnc Kaboodle > > > > > > > > > > > > - saves current working directory, > > > > > > > > > > > > - changes current working directory as WinVNC installation > > > > > > > > directory. > > > > > > > > > > > > After starting WinVnc Kaboodle restores previous working > > > > > > directory. > > > > > > > > > > > > > > > > > > > > > > > > - Igor > > > > > > > > > > > > > > > > > > > > > > > > ----- Original Message ----- > > > > > > > > > > > > From: "Scott C. Best" <[EMAIL PROTECTED]> > > > > > > > > > > > > To: "Igor Kotelevsky" <[EMAIL PROTECTED]> > > > > > > > > > > > > Cc: "Kaboodle-devel" <[EMAIL PROTECTED]> > > > > > > > > > > > > Sent: Thursday, August 15, 2002 9:33 AM > > > > > > > > > > > > Subject: Re: [Kaboodle-devel] Release build problem > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Igor: > > > > > > > > > > > > > You're right that VNC server discovery, particularly > > > > > > > > > > > > > in Win98, has become less reliable. As Jeff suggested, it > > > > may > > > > > > > > > > > > > be interesting to try a heap walker or bound checker to > > > > see if > > > > > > > > > > > > > we can isolate the cause. > > > > > > > > > > > > > > > > > > > > > > > > > > On a related subject, I was hoping you could modify > > > > > > > > > > > > > the behavior of the "log VNC usage" button. Right now all > > > > it > > > > > > > > > > > > > does is set the registry entry for WinVNC. Problem is, > > > > when > > > > > > > > > > > > > I hit "View Log" it never finds the file, I always have to > > > > > > > > > > > > > browse for it. I was hoping you could do one of two > > > > things: > > > > > > > > > > > > > > > > > > > > > > > > > > 1. Have the WinVNC log be written into the installation > > > > dir, > > > > > > > > > > > > > and have ViewLog always look there first. > > > > > > > > > > > > > > > > > > > > > > > > > > 2. Alternatively, don't use WinVNC log at all. Kaboodle > > > > has > > > > > > > > > > > > > its own debug info now that's written to > > > > > > VncServerSessionLog > > > > > > > > > > > > > when built in Debug mode. Perhaps we could output some > > > > (not > > > > > > > > > > > > > all) of that info into a .txt file. > > > > > > > > > > > > > > > > > > > > > > > > > > The intent with logging was for the user to be able to > > > > > > > > > > > > > find out who connected, or tried and failed to connect, to > > > > > > their > > > > > > > > > > > > > VNC server. All it needs to show are timestamps, IP > > > > address of > > > > > > > > > > > > > the Viewer, and connection status (failed, connected, > > > > > > > > disconnected, > > > > > > > > > > > > > etc). Unfortunately, the debug info shows a whole lot more > > > > > > than > > > > > > > > > > > > > just that. > > > > > > > > > > > > > > > > > > > > > > > > > > Perhaps we could combine both: if the user has "Log > > > > > > > > > > > > > VNC usage" we could both set the debug flag in the VNC > > > > > > registry, > > > > > > > > > > > > > *and* record Kaboodle-detected info. So if someone > > > > connected > > > > > > > > > > > > > directly, we could show that from grep'ing the VNC log > > > > file. > > > > > > > > > > > > > If someone connected via Kaboodle, we could show that > > > > > > directly. > > > > > > > > > > > > > > > > > > > > > > > > > > Eager for your thoughts. I suppose getting #1 to work > > > > > > > > > > > > > above would be sufficient for the needs of 0.90. > > > > > > > > > > > > > > > > > > > > > > > > > > -Scott > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Wed, 14 Aug 2002, Igor Kotelevsky wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > Hello Scott. > > > > > > > > > > > > > > I see that VNC server discovery has become less > > > > reliable. > > > > > > > > > > > > > > That unreliability shows itself in release build, > > > > > > particularly > > > > > > > > in > > > > > > > > > > Win98 > > > > > > > > > > > > OS. > > > > > > > > > > > > > > It isn't possible that one of my recent updates broke > > > > > > > > something - > > > > > > > > > > > > > > I didn't changed something pertaining to that part. > > > > > > > > > > > > > > Here is what I have found. > > > > > > > > > > > > > > Now VNC discovery sometimes cannot create a client > > > > socket > > > > > > for > > > > > > > > scan > > > > > > > > > > port. > > > > > > > > > > > > > > I see the system error's code 10055. > > > > > > > > > > > > > > That error has following text > > > > > > > > > > > > > > "An operation on a socket could not be performed because > > > > > > > > > > > > > > the system lacked sufficient buffer space or because a > > > > queue > > > > > > was > > > > > > > > > > full". > > > > > > > > > > > > > > It looks like another thread simultaneously makes big > > > > lot of > > > > > > > > socket > > > > > > > > > > > > work. > > > > > > > > > > > > > > > > > > > > > > > > > > > > Here is what I can implement for the button "Check > > > > Again" > > > > > > only. > > > > > > > > > > > > > > If VNC server discovery receives above error code 10055, > > > > > > > > > > > > > > then it waits 0.3 second and repeats the operation one > > > > more > > > > > > > > time. > > > > > > > > > > > > > > It seems to me that the button "Check Again" will be > > > > more > > > > > > > > reliable. > > > > > > > > > > > > > > > > > > > > > > > > > > > > I cannot implement above check error code 10055 for VNC > > > > > > server > > > > > > > > > > discovery > > > > > > > > > > > > > > at the first start Kaboodle (empty registry setting). > > > > > > > > > > > > > > It seems to me that it is uselessly in that case. > > > > > > > > > > > > > > We have to find and fix the reason of error code 10055. > > > > > > > > > > > > > > > > > > > > > > > > > > > > - Igor > > > > > > > > > > > > > > > > > > > > > > > > > > > > ----- Original Message ----- > > > > > > > > > > > > > > From: "Scott C. Best" <[EMAIL PROTECTED]> > > > > > > > > > > > > > > To: "Igor Kotelevsky" <[EMAIL PROTECTED]> > > > > > > > > > > > > > > Cc: "Kaboodle-devel" > > > > <[EMAIL PROTECTED]> > > > > > > > > > > > > > > Sent: Wednesday, August 14, 2002 8:37 AM > > > > > > > > > > > > > > Subject: Re: [Kaboodle-devel] Release build problem > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Igor: > > > > > > > > > > > > > > > Your changes look good. I noticed one thing though: it > > > > > > > > > > > > > > > seems as if the VNC server discovery has become less > > > > > > reliable > > > > > > > > > > > > > > > since you made these changes. Sometimes it takes two > > > > or > > > > > > three > > > > > > > > > > > > > > > "Check Again" tries for it to find the VNC server one > > > > one > > > > > > of > > > > > > > > > > > > > > > my machines. It used to catch it right away. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > This is in release build, latest stuff. Is it possible > > > > > > > > > > > > > > > that one of the recent updates broke something? > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -Scott > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Tue, 13 Aug 2002, Igor Kotelevsky wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Hello Scott. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > I inserted exact your texts > > > > > > > > > > > > > > > > into the top of "VNC setup" tab in the device icon. > > > > > > > > > > > > > > > > Now only the "Check Again" button is active > > > > > > > > > > > > > > > > if VNC connection is not possible. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Also I found that Kaboodle saves special debug data > > > > into > > > > > > the > > > > > > > > log > > > > > > > > > > > > files > > > > > > > > > > > > > > > > - KaboodleNIDPreAlpha.xml, > > > > > > > > > > > > > > > > - Kaboodle_Dbg.htm, > > > > > > > > > > > > > > > > - Gnutella.log. > > > > > > > > > > > > > > > > That files appeared both in debug and release > > > > builds. > > > > > > > > > > > > > > > > Now that files appear in debug build only. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > - Igor > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ----- Original Message ----- > > > > > > > > > > > > > > > > From: "Scott C. Best" <[EMAIL PROTECTED]> > > > > > > > > > > > > > > > > To: "Igor Kotelevsky" <[EMAIL PROTECTED]> > > > > > > > > > > > > > > > > Cc: "Kaboodle-devel" > > > > > > <[EMAIL PROTECTED]> > > > > > > > > > > > > > > > > Sent: Tuesday, August 13, 2002 8:28 AM > > > > > > > > > > > > > > > > Subject: Re: [Kaboodle-devel] Release build problem > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Igor: > > > > > > > > > > > > > > > > > Good, thanks; VNC tunneling is working again > > > > nicely. > > > > > > > > > > > > > > > > > Only bug I can find right now: when I'm on PC1 and > > > > I > > > > > > open > > > > > > > > the > > > > > > > > > > > > > > > > > device icon for PC2 (which is not running a VNC > > > > > > service) > > > > > > > > it > > > > > > > > > > > > > > > > > says at the top "when connecting to <b>PC2</b> > > > > from > > > > > > > > > > <b>PC1></b> > > > > > > > > > > > > > > > > > use these settings". It *used* to say "PC2 is not > > > > > > running > > > > > > > > a > > > > > > > > > > > > > > > > > VNC Service" and only the "Check Again" button was > > > > > > active. > > > > > > > > > > > > > > > > > Did that get changed somehow? > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -Scott > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Mon, 12 Aug 2002, Igor Kotelevsky wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Hello Scott. > > > > > > > > > > > > > > > > > > I found next VNC problem: > > > > > > > > > > > > > > > > > > - PC1 run independent VNC service; > > > > > > > > > > > > > > > > > > - PC1 run Kaboodle with option "Enable Kaboodle > > > > > > Tunnels > > > > > > > > for > > > > > > > > > > > > VNC"; > > > > > > > > > > > > > > > > > > - I open PC1 device icon on PC2 machine and > > > > > > > > > > > > > > > > > > try to start up "Connect through Kaboodle". That > > > > > > > > connection > > > > > > > > > > > > failed. > > > > > > > > > > > > > > > > > > I found conflict in port number: > > > > > > > > > > > > > > > > > > - independent VNC service on PC1 listen some > > > > port > > > > > > > > number. > > > > > > > > > > > > > > > > > > That number by default is 5900. > > > > > > > > > > > > > > > > > > (it is number by default); > > > > > > > > > > > > > > > > > > - Kaboodle on PC1 reads port number of VNC > > > > viewer > > > > > > and > > > > > > > > > > > > > > > > > > uses it for start up VNC viewer,... > > > > > > > > > > > > > > > > > > That number by default is 5900 also. > > > > > > > > > > > > > > > > > > Now that bug fixed. > > > > > > > > > > > > > > > > > > Before start "Connection through Kaboodle" > > > > > > > > > > > > > > > > > > Kaboodle on the viewer side make check: > > > > > > > > > > > > > > > > > > if there is running independent VNC server on > > > > the > > > > > > port > > > > > > > > > > number > > > > > > > > > > > > > > > > N_VNC_SERVER, > > > > > > > > > > > > > > > > > > then port for start VNC viewer cannot be same as > > > > > > > > > > N_VNC_SERVER > > > > > > > > > > > > > > > > > > and same as port, which use for tunnel. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > I continue test Kaboodle in release and debug > > > > mode. > > > > > > > > > > > > > > > > > > I see that Kaboodle works both in release and > > > > debug > > > > > > > > mode. > > > > > > > > > > > > > > > > > > If you will find any VNC bug, please send me > > > > next > > > > > > log > > > > > > > > files > > > > > > > > > > > > > > > > > > - SessionVncServerLog.txt, > > > > > > > > > > > > > > > > > > - SessionVncViewerLog.txt, > > > > > > > > > > > > > > > > > > - ViewerThreadLog.txt > > > > > > > > > > > > > > > > > > for both Kaboodles. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > About port number 7000. > > > > > > > > > > > > > > > > > > Kaboodle always listens TCP connection on port > > > > > > number > > > > > > > > 7000. > > > > > > > > > > > > > > > > > > Please see > > > > > > > > > > > > > > > > > > > > > > > > > > http://www.geocrawler.com/archives/3/16728/2002/5/0/8657977/ > > > > > > > > > > > > > > > > > > If PC1 need to start independent VNC server on > > > > PC2, > > > > > > > > > > > > > > > > > > then PC1 send special message to the PC2 on port > > > > > > number > > > > > > > > > > 7000. > > > > > > > > > > > > > > > > > > Also that port used for initialization "File > > > > > > Transfer". > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > - Igor > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ----- Original Message ----- > > > > > > > > > > > > > > > > > > From: "Scott C. Best" <[EMAIL PROTECTED]> > > > > > > > > > > > > > > > > > > To: "Igor Kotelevsky" > > > > <[EMAIL PROTECTED]> > > > > > > > > > > > > > > > > > > Cc: "Kaboodle-devel" > > > > > > > > <[EMAIL PROTECTED]>; > > > > > > > > > > > > > > "mailbox" > > > > > > > > > > > > > > > > > > <[EMAIL PROTECTED]> > > > > > > > > > > > > > > > > > > Sent: Sunday, August 11, 2002 9:17 PM > > > > > > > > > > > > > > > > > > Subject: Re: [Kaboodle-devel] Release build > > > > problem > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Igor: > > > > > > > > > > > > > > > > > > > I agree that the Release builds are not > > > > working > > > > > > right > > > > > > > > > > > > > > > > > > > now. However, even in Debug mode, I cannot get > > > > VNC > > > > > > > > > > tunneling > > > > > > > > > > > > > > > > > > > to work anymore. So I used WinCVS to get a > > > > code > > > > > > > > snapshot > > > > > > > > > > from > > > > > > > > > > > > > > > > > > > August-8, so that VK's NID-synch bugs were not > > > > > > > > involved. > > > > > > > > > > Still > > > > > > > > > > > > > > > > > > > doesn't work. Details: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > 1. I'm running the VNC server on PC1, WinNT, > > > > debug > > > > > > > > build. > > > > > > > > > > > > > > > > > > > No VNC service is active, Kaboodle is setup to > > > > > > > > "autostart > > > > > > > > > > if > > > > > > > > > > > > > > > > > > > needed". On PC2, running Win2k, in the Device > > > > Icon > > > > > > for > > > > > > > > > > PC1, in > > > > > > > > > > > > > > > > > > > the VNC Setup tab, "Connect Directly" is > > > > greyed > > > > > > out. > > > > > > > > Since > > > > > > > > > > > > > > > > > > > no server is running on PC1, both choices > > > > should > > > > > > be > > > > > > > > > > active. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > 2. Then on PC2 I open the VNC Service Icon, > > > > and go > > > > > > to > > > > > > > > the > > > > > > > > > > > > > > > > > > > list of viewers. I enter the password for PC1, > > > > hit > > > > > > > > > > connect. I > > > > > > > > > > > > > > > > > > > immediately get an error from VNC "Cannot > > > > connect > > > > > > to > > > > > > > > > > server". > > > > > > > > > > > > > > > > > > > Over on PC1, the VNC server icon is in my > > > > service > > > > > > > > tray, > > > > > > > > > > and > > > > > > > > > > > > > > > > > > > it's lit-up, indicating it's receiving a > > > > > > connection. > > > > > > > > The > > > > > > > > > > log > > > > > > > > > > > > > > > > > > > file on PC1 has just two lines: "BEGIN: > > > > > > > > StartVNCServer" > > > > > > > > > > and > > > > > > > > > > > > > > > > > > > "StartVNCServer: Ok start Independent > > > > VNCserver > > > > > > port > > > > > > > > > > number > > > > > > > > > > > > > > > > > > > 5900". I look at the tcpdump traffic on my > > > > LAN, > > > > > > and > > > > > > > > see > > > > > > > > > > the > > > > > > > > > > > > > > > > > > > following. When I hit connect: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > 16:36:57.351343 192.168.123.134.1189 > > > > > > > > > > > 192.168.123.130.7000: S > > > > > > > > > > > > > > > > > > > 2008127198:2008127198(0) win 16384 <mss > > > > > > > > > > 1460,nop,nop,sackOK> > > > > > > > > > > > > (DF) > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > In the above, PC1 is .130 and PC2 is .134. Why > > > > > > would > > > > > > > > port > > > > > > > > > > > > > > > > > > > 7000 be involved in a VNC tunnel? I wait a few > > > > > > seconds > > > > > > > > to > > > > > > > > > > see > > > > > > > > > > > > > > which > > > > > > > > > > > > > > > > > > > port the VNC viewer on PC2 is trying to use. > > > > Keep > > > > > > in > > > > > > > > mind > > > > > > > > > > that > > > > > > > > > > > > > > > > > > > "Connect Directly" was not a valid choice: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > 16:36:57.807921 192.168.123.134.1190 > > > > > > > > > > > 192.168.123.130.5900: S > > > > > > > > > > > > > > > > > > > 2008283092:2008283092(0) win 16384 <mss > > > > > > > > > > 1460,nop,nop,sackOK> > > > > > > > > > > > > (DF) > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > So PC2 has tried to connect directly, even > > > > though > > > > > > > > > > > > > > > > > > > Kaboodle on PC1 has opened a tunnel and > > > > connected > > > > > > > > > > successfully > > > > > > > > > > > > > > > > > > > with the VNC server (which is why the VNC icon > > > > in > > > > > > the > > > > > > > > > > service > > > > > > > > > > > > > > > > > > > tray is lit-up bright white). > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > 3. I then try connecting again from PC2. I get > > > > a > > > > > > > > Kaboodle > > > > > > > > > > > > error > > > > > > > > > > > > > > > > > > > saying "You already have a VNC session > > > > > > connected > > > > > > > > with > > > > > > > > > > PC1". > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Thanks for looking into this. I was very > > > > surprised > > > > > > > > that > > > > > > > > > > > > > > > > > > > port-7000 got involved with this connection > > > > > > attempt. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -Scott > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Fri, 9 Aug 2002, Igor Kotelevsky wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Hello Scott. > > > > > > > > > > > > > > > > > > > > I have tested all my changes in both debug > > > > and > > > > > > > > release > > > > > > > > > > > > builds. > > > > > > > > > > > > > > > > > > > > All worked. > > > > > > > > > > > > > > > > > > > > Then I merged my code with CVS code. > > > > > > > > > > > > > > > > > > > > Now Kaboodle works in debug builds only. > > > > > > > > > > > > > > > > > > > > There is a problem in realise build - > > > > > > > > > > > > > > > > > > > > Kaboodle starts, but a user don't see GUI. > > > > > > > > > > > > > > > > > > > > I found a problem. > > > > > > > > > > > > > > > > > > > > Please look into the function int > > > > > > > > > > CEFController::Start(). > > > > > > > > > > > > > > > > > > > > There is a line > > > > > > > > > > > > > > > > > > > > while > > > > (!m_pNetworkManager->bStartUpFinished); > > > > > > > > > > > > > > > > > > > > It seems to me that there is infinite loop > > > > in > > > > > > > > realize > > > > > > > > > > build. > > > > > > > > > > > > > > > > > > > > The member > > > > m_pNetworkManager->bStartUpFinished > > > > > > > > > > > > > > > > > > > > sets as "TRUE" in the function > > > > > > > > > > > > > > > > > > > > int CNetworkManager::OnStartup(DWORD > > > > > > nIDController, > > > > > > > > > > CGUID > > > > > > > > > > > > > > > > KaboodleID). > > > > > > > > > > > > > > > > > > > > It seems like that function don't works > > > > > > correctly in > > > > > > > > > > release > > > > > > > > > > > > > > build. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > - Igor > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > > > > > > > > > > > > > > > > > This sf.net email is sponsored by:ThinkGeek > > > > > > > > > > > > > > > > > > > > Welcome to geek heaven. > > > > > > > > > > > > > > > > > > > > http://thinkgeek.com/sf > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > > > > > > > > > > > > > > Kaboodle-devel mailing list > > > > > > > > > > > > > > > > > > > > [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > https://lists.sourceforge.net/lists/listinfo/kaboodle-devel > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > This sf.net email is sponsored by: OSDN - Tired of that same old > > > cell phone? Get a new here for FREE! > > > https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 > > > _______________________________________________ > > > Kaboodle-devel mailing list > > > [EMAIL PROTECTED] > > > https://lists.sourceforge.net/lists/listinfo/kaboodle-devel > > > > > > > > > > > ------------------------------------------------------- > > This sf.net email is sponsored by: OSDN - Tired of that same old > > cell phone? Get a new here for FREE! > > https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 > > _______________________________________________ > > Kaboodle-devel mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/kaboodle-devel > > > > ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 _______________________________________________ Kaboodle-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kaboodle-devel