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:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Kaboodle-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
