Dave:
Heya. Sorry for the delay in writing...kids came home sick from school and shared it all around. :)
It sounds like your working with version 0.99e; please try working with our latest beta instead:
ftp://ftp.echogent.com/Kaboodle/beta/Kaboodle/Kaboodle_12Feb05_BETA.zip
There is a "known issue" right now that Kaboodle can relay VNC connections, but it seems to struggle with terminating VNC connections. That is, if you make a LAN-to-LAN connection with Kaboodle, you can VNC from the Kaboodle-PC on one end to a VNC-Server on another, as long as that VNC-Server isn't the Kaboodle PC itself. I know: that's pretty lame. I hope to get it fixed soon and into an up-to-date beta release.
-Scott
On Sun, 13 Feb 2005, Dave Dyment wrote:
I've now managed to go one small step further. My home pc says its connected after clicking on the get engaged connect button. However when I click on the icon for my office pc and click on the button "click here to take remote control of this pc" the window freezes with the message pc not responding on the title bar. What is supposed to happen? I also note some odd parameters under the VNC setup tab. Under server status it says office pc running on port 0. Other times it says port 59636. Under the viewer setup tab it says "connect to VNC on display 59636. or by clicking on the dropdown menu bar beside display it changes to port 0. Help. Dave
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Kaboodle-user mailing list Kaboodle-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kaboodle-user To UNSUBSCRIBE, click on the above link.
