Inconsistent or slow reconnection
Tuesday, July 11, 2006 by Guy Gascoigne-Piggford | Discussion: Multiplicity
When I bring it back to my desk, if I want to reconnect quickly I double click on the multiplicity icon in the system tray (I'm using Multiplicity Pro 1.05) then double click on the secondary machine in the list, then hit OK and wait for a reconnect. This works about half the time. What I've found works every single time is to just unload multiplicity and then reload it, fewer clicks, seems to be a bit quicker and is 100% reliable.
Can't we have some sort of similar 'reconnect' function available on the context menu?
Thanks.
Reply #2 Wednesday, July 12, 2006 5:54 PM
There should be no need for a reconnect button.
Multiplicity automatically attempts reconnects in the background every 8 seconds. If you touch the edge of the screen where the machine would be, the reconnect attempt will be attempted. It is designed to be seamless and require no thought from the user.
DNS lookups may result in longer delays.
On builds prior to 1.05 the connections were done one by one, so having one pc that was off listed as a secondary could result in a 30+ second delay in connecting to others. In 1.05 they are all done at once.
Chances are that if it takes more than 8 seconds to reconnect then Multiplicity was already trying to connect to the pc before you turned the secondary on and it is waiting on a socket to timeout. This may take 30 seconds or so.
If it never reconnects after a disconnect then it suggests the IP of the secondary has changed.
Reply #3 Friday, July 14, 2006 2:21 AM
Maybe it's just the nVidia NICs in general, at least in my case?
What kind of NIC do you have, Guy Gascoigne-Piggford?
Reply #4 Wednesday, July 19, 2006 7:51 PM
As for NIC, the desktop is a Broadcomm Netexreme and the laptop is an Intel Pro/Wireless 3945ABG.
Reply #5 Thursday, July 20, 2006 5:23 PM
| Neil, I'm really not sure that this is the behaviour that I'm seeing |
Reply #6 Tuesday, August 8, 2006 11:04 PM
As a side note, another issue I'm getting is that if one of the systems is not on when Multiplicity starts, it won't connect to any of them. I have all systems set to static IP, so it should not be looking up the host names for any of them.
Reply #7 Wednesday, August 9, 2006 9:43 AM
Reply #8 Wednesday, August 9, 2006 4:08 PM
BTW, since I tend to have ongoing issues, I'd be willing to take this to email or IM, if you prefer. I also have test machines, so would be more than happy to try out test builds and obtain more technical info for you (ie, logs from whatever tools you prefer). In the interest of productivity, I would, of course, keep it purely technical (in case there's any concern).
Reply #9 Thursday, August 10, 2006 12:19 AM
BTW, how do I get the latest version of multiplicity? I have version 1.5, maybe updating will fix my problem?
Can I just install the eval version and it will keep my license?
Reply #10 Thursday, August 10, 2006 7:34 AM
https://www.stardock.com/products/sdcentral/
https://www.stardock.com/sdnet_login.asp
Please login to comment and/or vote for this skin.
Welcome Guest! Please take the time to register with us.
There are many great features available to you once you register, including:
- Richer content, access to many features that are disabled for guests like commenting on the forums and downloading skins.
- Access to a great community, with a massive database of many, many areas of interest.
- Access to contests & subscription offers like exclusive emails.
- It's simple, and FREE!







Reply #1 Wednesday, July 12, 2006 5:06 PM