Scott, Basically I'd like to be able to access my home PC (and network) while I'm on the road or while I'm at work. All PCs running Kaboodle are running XP. As I said earlier, I think I properly set up port forwarding from my router to the PC running Kaboodle (home network), but from your response it seems like it shouldn't matter since I'm using the demo proxy.
I'm not sure what other information I could provide that might allow you to help me figure out what's wrong. I followed the instructions for setting up connections and partnerships, but most of the other settings I left at default. I didn't have any installation problems, and the software has never crashed. I have ZoneAlarm firewall on my home PC and Norton firewall on my laptop, but I gave full access for Kaboodle, WinVNC, and Zebedee on both systems so the software firewalls probably aren't the problem. In the mean time I'll try the echovnc program to see if that can give me some of what I need. - Ted P.S. - I noticed (at work) how it's not possible to have two PCs on the same network as masters. However, for whatever reason, when I was using my laptop at home (thru a wireless connection) it did allow me to have the main desktop as master and the laptop as master as well. That's when I was able to do a connection from the desktop to the laptop (but not the other way around). I guess this points to a problem with the network setup? -----Original Message----- From: Scott C. Best [mailto:[EMAIL PROTECTED] Sent: Thursday, September 08, 2005 7:15 PM To: Ted Barham Cc: kaboodle-user@lists.sourceforge.net Subject: Re: [Kaboodle-user] Kaboodle won't connect? Ted: Heya. Sounds like you have some things a bit jumbled (not your fault; that part of Kaboodle *is* a bit jumbled). When two or more PC's are on the same LAN, only one of them (ie, the "Master Node") can participate in a LAN-to-LAN GetEngaged connection. So if your PC and laptop are on the same LAN, only one of them can be the "Master Node", and so you won't be able to make a GetEngaged connection between them. If your laptop and PC are on *different* LANs (ie, one on the LAN, one connected via dialup), they can both become "Master Nodes", and they can then make a GetEngaged connection with each other. As for the KaboodleProxy capability, it can be used to help facilitate the GetEngaged connection -- it's an alternative to doing port-forwarding. If you've already port-forwarded for the PC on the LAN, you won't need to use KaboodleProxy (though it will still work, of course). Lastly...what *is* the "connection you really care about"? If you just want to connect from one Windows PC to another Windows PC across the Internet regardless of firewalling, you should try EchoVNC: "http://www.echovnc.com";. It connects just to PC's together, whereas Kaboodle attempts to connect two LAN's together. hope that helps, Scott On Thu, 8 Sep 2005, Ted Barham wrote: > I just discovered Kaboodle yesterday and excitedly installed it on my > home computer, my work computer and my laptop. I registered three > different email addresses (on for each PC), and I created partnerships > for each combination. And I added the demo proxy to Kaboodle in each > computer. I also set up port forwarding on my home router for ports > 4182, 4183, and 11965 (being a novice at TCP/IP stuff I can't be certain > I did this part correctly, though). And I verified that Zebedee was > running. > > But so far I've only been able to make a connection from my home PC to > my laptop - not the connection I really care about. And even that > connection may not have been a good test since both PCs were on the same > network at the time. What I really want to do is connect from my laptop > to my computer at home, or from my work computer to my home computer. > But trying to connect I always get a message along the lines of > "Sorry...your GetEngaged partner xxxx could not be connected with via > any of your KaboodleProxy connections." > > Is the problem my firewall settings, or should the demo proxy allow > connections beyond a firewall? I'd gladly purchase the $25 software that > allows connecting behind a firewall, but only if I'm fairly certain that > it will fix my current problem. And are there any other things I could > play with to fix the problem? > > - Ted Barham ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Kaboodle-user mailing list Kaboodle-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kaboodle-user To UNSUBSCRIBE, click on the above link.
