Friday, July 31, 2015

The SOM Saga 3 - Disconnected

The SOM2 comes with a feature that makes long distance cooperation possible - the SOM2PC software allows one partner to send commands to the second partner's PC in order for it to deliver one or a set of spanks, even if that second partner should be on the opposite side of the globe.

To get the SOM2 software to work, you have to install a free widget called phidgets:  which actually handles the P.C. to P.C. communications.  The SOM panel on one partner's screen sends a "message" through phidgets, which transmits the message onto the host P.C., which then carries out that command.

The network screen on both machines is identical:  you enter an ISP of interest, a "passphrase", indicate whether you are the host or are connecting to the host.   And that is it.   To slightly confuse the issue for a few moments when first entering this screen,  is that a dummy ISP is already displayed:  you have guess that you need to type the real ISP over the top of it.

Then you press the "connect to host" button and after ten seconds or so you might get an error message which means the host said the electronic communications equivalent of "Sod off!  I'm not interested"   (Not the exact words, but that is what they mean in human terms).  Which is exactly what happened when we tried our first link up.

Many, many, many experiments failed to remove the error message and allow access.  

Research suggested firewalls might be to blame.  Both computers had the SOM2PC and the phidgets added to the exceptions file.   No change.    The firewalls were switched off on both machines,   No change.

So - Both machines had the extremely efficient but not without risk TightVNC software downloaded onto them.   One partner would be able to actually take over complete control of the other computer: hence the risk element inherent with this solution.

And then something significant happened.   Trying to connect using the TightVNC   resulted in exactly the same sort of error message.   Perhaps it was not software, but a hardware problem, that we faced.

A chat with an IT specialist seemed to be in order, and an appointment was duly made.


No comments:

Post a Comment