Hi
I've somehow managed to get Direct Connection working fine now - maybe I
didn't have the ports forwarded correctly one end.
Now I seem to have uncovered a small problem. I can connect fine and
remote control my master node pc on the other end if I connect using the
Kaboodle Proxy - I am using TightVNC as the remote control software.
However if I connect using the Direct Connection method the remote
control doesn't work - I get an hourglass for a few moments and then
nothing. I try it again and nothing, no sign of TightVNC viewer firing
up.
I've tried this a few times and it seems to be consistent.
I also have a hunch that remote control doesn't work if you one party
makes the connection via Kaboodle proxy and then the other one tries to
remote control a pc on the first network. Although I guess this would be
quite an unusual scenario.
One small point - I can't seem to disconnect by right-clicking the
connected network's name and selecting disconnect. It's never worked for
me. The only way I seem to be able to disconnect is to close down
Kaboodle.
Another small point - when I close down Windows XP Professional with
Kaboodle running Kaboodle doesn't get closed like other programs but
instead I get a dialog requiring me to 'End Now', which is a shame
because I cannot then restart the computer remotely - this blocks the
restart process.
Thanks again for a great free set of programs.
Kind regards
Jeff Cole
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Kaboodle-user mailing list
Kaboodle-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kaboodle-user
To UNSUBSCRIBE, click on the above link.
