Connection problems - just started, used to connect perfectly

Are you connected via wireless or ethernet cable?

Also is this a home network, or a work network?

Given the error messages, it sounds like you are suffering from dataloss on the network.

I'm running into the same problem. I upgraded to the recent version that's on Impulse and am fine as far as connecting to the initial secondary PC on the right that I use.

But I just recently set up a new PC to connect to on the left. It connects fine via the systray but as soon as I move my mouse over to that screen it throws up an error message saying that it has lost a connection to that machine. As soon as I move the cursor back over into the primary monitor Multiplicity immediately re-connects to that PC. I move the cursor over there again, it dumps. Move it back, it reconnects.

Any suggestions?

What OS is the secondary running?

Also which message does it show?

My Primary is running XP. The right hand secondary is Vista. The left hand secondary that is having this problem is XP.

All three are running the version that was on Impulse as of last night... so... 1.21.017.

The message I see is as follows. [machine name] is where the name of my secondary PC is normally:

Connection to [machine name] lost

Your connection to [machine name] has been lost due to a network error. Multiplicity will try to connect in the background and will inform you when a connection has been made.
------------

The message only barely stays up so that's my best guess at what it is.

There isn't anything on the left secondary that should be blocking the connection. I can connect to it via \\[machine name] just pefectly fine, etc.

To add to this. All of the PC's are physically connected via network cable. They all run into the same local switch as well.

Same problem starting.

2 of my 3 machines work fine , after i installed version .017 on my 3rd that computer kept rebooting.. i had to restart in vga mode (i know it's strange) and uninstall by hand .. the service didnt even install either..

The computer in question is runing XP64 on a athlon X2 .

After uninstalling the new beta , and installing 1.21 over it , i started getting the disconnect messages. with any version of multiplicity i still have on my computer the problem remains the same.

I¨move my cursor to the screen of the XP64 machine , and multiplicity on the primary instantly gives a disconnect message.!!

I have 2 interfaces in each machine , connected to 2 different networks all my machines have a 192.168.3.x address and a 192.168.1.X address. the 1.X ones are the default route and connect to internet through a small linux machine , the whole thing is a 100 mbit network. the 3.X one is a gigabit network i use for file transfers , multiplicity , and X11 ..

I have tried over both networks.. but as soon as the XP64 machine gets the pointer it disconnects.. i have also tried with a combination of 2 tunnels , i connect the primary with putty to my linux firewall , and my secondary also , on the primary i had a '4L30564 0.0.0.0:30564' tunnel running.
and on the secondary a '4R030564 127.0.0.1:30564' tunnel. telnet worked fine , adding a machine with multiplicity worked fine.. but again , as soon as a connection gets made by moving the mouse in that scree, multiplicity disconnects.

I'm pretty sure this isn't network related, my certainty about this gets underlined by the fact i tried it on 2 different interfaces in 3 different ways. and file transfers and X11 sessions transfer and display just as well as they did before.

Due to all this , multiplicity has become unusable for me and i'm back to my 2 hardware kvm switches .

I also did a restore to a restore point a few days ago when everything still worked fine , but to no avail.


Hoping for a speedy resolution to this issue.

Kind regards.


(i will make a new post for the infinite reset issue since the two probably aren't related)

My problem is slightly different from those in this thread, but I will post this anyway. I recently got a new primary PC at work (I lost a drive on my old one), and downloaded and installed the latest version of Multiplicity (1.21). It's been around for a pretty long while now, so I assumed that it was the version I'd previously used. After installing 1.21 and getting everything setup with my secondary PC, I noticed that I was getting the "Connection to [machine name] lost" error message. For me, I was getting that error popping up on my primary machine every 11 seconds. I would lose the connection the secondary machine for about 1 second, then the connection was restored. It was really irritating. Finally, after reading on this forum for a while, I thought to check the Multiplicity version numbers on the primary and secondary PC. While my newly installed primary PC was running 1.21, my secondary PC was running Multiplicity version 1.02. So I uninstalled the 1.02 version from my secondary PC and then installed version 1.21 on my secondary PC, and my connection problems appear to have vanished. Hope this helps somebody.

I had this problem.  Here are some things to check:

    * Check the IP address on the "Connection to [machine name] lost" message.  Verify that it is the correct address of the desired machine.  If not, set "Lookup the IP address each time" in the Add Secondary Machine dialog box brought up by the "Configure" option on the primary computer.
    * Check if the Wire IP address and the Wireless IP address is interfering with each other if you have more than one secondary computer configured.

Hope this help.

 

Just got the same problem myself.
Main computer is running Windows 7 Beta (I know Stardock doesn't support that one yet) but it worked perfectly before I decided my secondary computer needed a format and re-install of Windows XP Pro.
Yes, I'm using wired network and both computers go through the same router. Both computer also find each other on the network and is on the Internet.

*pokes random Stardock developers in the ribs*

Cheers!

UPDATE!
Re-installed Windows XP Pro on my main computer to see if that solved the issue, but alas! Still having the problem.

Back to running Vista on the main comp and XP on the secondary, still not working. E-mailed support with the two logs from both comps (when both ran XP) like 3-4 days ago and still haven't got a reply yet. Starting to getting a bit annoyed to say the least, because it's a real pain having to switch betwean two keyboards and mice.

May not be the same case, but I got very similar symptoms (connection dropped then almost immediately restored) recently. Turned out that, thanks to an oversight on my part, two different master machines were trying to connect to the same secondary. Whichever master wasn't connected would try to re-connect, and kick the connected master in the process (not the most graceful of behaviour in this situation!). This then carried on ad-infinitum, with control cycling between the two masters every 5 seconds or so.

 

Again, might not be your issue, but worth checking.

The trial version of multiplicity worked fine with both my primary and secondary machines but the problems started after i installed multiplicity pro after my trial version expired.

My primary machine is vista 64 while my secondary is an xp. the screen turn black when the mouse is moved to the left most edge of my primary computer and i get a message later saying that the internet connection was lost.

It seems like several of you are having the same problem. Did anyone find a solution to this problem. It is strange that there is no 'help', FAQ or 'contact' sections anywhere in the software.

Any help resolving this issue will be much appreciated.