Stopped working...

I have two XP machines, both with the windows firewall completely disabled running Multiplicity inside of a close business network.

Multiplicity had been running flawlessly for several months until last Wednesday when it suddenly just stopped working; not after a reboot or anything but just in the middle of the day.

I have un-installed and re-installed both the primary and secondary probably 5 times now, and still cannot get the two to talk to each other. When I go to add a secondary machine via the wizard on the Primary, it resolves the IP from the machines name and adds it with no issue. When I run troubleshooting, however, Mult claims that it cannot connect to the client machine. Troubleshooting on the secondary says it has no issues.

I have Windows firewall completely turned off, both machines can ping each other, and both Multiplicity installs correctly resolve the IP for the other machine, and both are using the default port.
5,332 views 11 replies
Reply #1 Top
Can you ping and telnet from the secondary to the primary and vice versa?

Any security software installed?

Reply #2 Top
Can you telnet form PC to PC over the Multiplicity port?
Can you verify that the versions are the same (check file dates)?

[As a feature request . . . it sure would be nice if teh primary cuold check the files on the secondary and alert the user if something didn't match . . but of course . . it'd have to be able to connect to check . . forget I said anything at all . .move along, move along)
Reply #3 Top
HOLY COW!  Seabass beat me this time!  Now the game is ON!!
Reply #4 Top
No security software installed...

I can ping just fine... using command line Telnet and opening the secondary machine fails to connect.

edit: yes, both identical versions.
Reply #5 Top
Telnet failing to connect = blocked. Somehow or someway that port or even simply the program is being blocked. I am happy to tell you that Multiplicity is not the culprit, I am unhappy to tell you I don't know what is. Something must have changed in your computer for that to be blocked the way it is. I would start rooting around in the system. Let us know if you have any leads and we will help as best as possible.

Take that gadget!
Reply #6 Top
Don't I have to be running a telnet server on the opened machine for a telnet client to be able to connect to it?
Reply #7 Top
for some reason, the telnet service was disabled on both machines.. I re-started them both and set them to automatic, but still to no avail.
Reply #8 Top
You might want to start a ticket with us then at support@stardock.com

Either that or call us at 734.927.0677

If you start the ticket referance this thread.
Reply #9 Top
Hi Friends,
I share the pain of fellow users and admire the incredible program of Multiciplicity.
We are a Pure-Play Wine retailer in the Net and this glich has caused us much headache. I believe that it is not the fault of Multiplicity/Stardock.
I think it was generated from a Microsoft automatic update.
Using Vista64 as primary and XP32 as secondary, I experienced every sign and symptom listed above.
When I enterered V64 through a user account that had not been used in months, Multiplicity worked perfectly. The minute I re-booted and MS installed its latest updates, Multiplicity failed to work.

Only today did I find a NEW NEW NEW driver released from Nvidia (dated 12/20/07). I installed it then my computer automatically retrieved an update from Microsoft. VIOLA!! for the first time in days I can properly service my Christmas shoppers.

I believe that Nvidia and MS figured out their mistake.

Hope this helps.
Jeff
Reply #10 Top
To PrimeWines:
And you thought there was no Santa. Must be that dreaded virus "Humbug". Microsoft giveth and taketh away....Imagine life without this sort of fun.

To sl0ppy:
Good luck solving this one....maybe PrimeWines is onto something.
Reply #11 Top
I'm not sure how nVidia drivers have much bearing since I'm not using an nVidia chipset mobo..

Regardless, still no success even without all the latest windows updates. :/ I guess I'll start a ticket with support... in the mean time, it's back to Synergy.

note: this is between two XP32 machines, no Vista involved.