Cant connect to the secondary

It used to work.....

from Stardock Forums
Hello all.

I stumbled upon this product the other day and it looked great. So i decided to install it on my computers in my dorm room.

Both machines are running WinXP Pro SP2

Machine A is where the incoming ethernet cable(from wall jack)plugs in.

Machine A is sharing that internet connection with Machine B through a switch and using Windows built in Internet Connection Sharing function.

Machine B is the Primary (192.168.0.123)
Machine A is the Secondary (192.168.0.1)

I am using:

Stardock Multiplicity 1.03 Trial

Copyright © 2003-2005 Stardock.net, Inc


Okies, here is the deal. I cannot connect to my secondary. It keeps poping up the menue about cannot connect to the secondary maching.

Error : Unable to contact machine (Firewall?) You should ensure your firewall allows multipl.exe and multipl32.exe access to the network and that port 30564 is open

Well. I had thought that it might be my firewall (ZoneAlarm), but with all firewalls disabled (windows as well) it still cannot see the other computer.

Help plz..

Hienrich Jager

multiplicity
19,512 views 17 replies
Reply #1 from WinCustomize Forums Top

Can you ping the secondary from the primary?

Is multisrv32.exe running on the secondary (it may show as multis~1.exe in taskmanager)?

Reply #2 from Stardock Forums Top
yes i can ping the secondary from the primary through the telnet.exe feature the manual told me to do. any yes there is a MultiSrv32.exe in the taskmanager on the secondary
Fences - Organize your desktop icons today!
Reply #3 from WinCustomize Forums Top

What do you mean by it 'used to work'?  When did it stop working?

If you can telnet on that port from the primary on to the secondary then it may be a firewall on the primary is preventing MP from connecting to the secondary (rather than a firewall on the secondary blocking incoming MP connections). 

Reply #4 from Stardock Forums Top
When i first installed the trial last night it did take a while, and i had had to disable all firewalls, but i had been able to get it to work for a while. And it worked perfectly. But since a restart of both computers, over night, i cant get it to connect again.

And i have made doubly sure. There are no firewalls. Not Window's nor ZoneAlarm on either machine while i have been trying to get it to work today.

It is weird. The primary can see the secondary (through telnet.exe), and all ports are open and operating, but it still wolnt connect.
Reply #5 from WinCustomize Forums Top

If Multiplicity is still bringing up the message about the firewall, I would suggest that you check the IP address specified is right (and make sure the lookup option is disabled unless it changes often).  I assume you have not overriden the ports at either end. 

Reply #6 from Stardock Forums Top
Ihe ip addresses are both correct. and the ports are set as the default 30564 on both machines. You think maby that the problem is due to the fact that both computers are on a ICS connection? That is the only thing that i can think of causing problems.

sry bout the reply delay, had class
Reply #7 from Stardock Forums Top
SAme problem for me.. 2 XP working fine for web, for remote desktop (WIndows or VNC)..no firewall.. and have the same "unable to connect message" ... pleaz help
Reply #8 from WinCustomize Forums Top
I am getting the message as well but MultiSrv32.exe is not loading on the secondary machine. Ping works but telnet won't connect. I don't know what to set up on the secondary machine to make it accept telnet though. This all worked about 2 weeks ago. I have removed firewalls and all other programs in memory. I have uninstalled and reinstalled several times on each machine.

What's Next

Thanks,
Mason Landstreet
Reply #9 from Stardock Forums Top
I'm having a similar problem. My machines would connect fine, but then I reinstalled the OS on the slave machine, and reinstalled multiplicity. I've rebooted several times, but still it won't work. There is no firewall enabled, though I do have the lookup IP on since my IP addys are dynamic. I've tried it with and without security on, I can ping and do everything else between computers. But it still doesn't work. Even when I add a computer, it can see every other computer on my network but that one. Help... I'm getting very frustrated.
Reply #10 from WinCustomize Forums Top
Do you get a response when you telnet between teh two PCs on the MP part? You should get a response ("MULTIPLICITY#####"). (From the command prompt "telnet [ipaddress] [port]")

Have you verified that the versions are exactly the same? Do the ports match?

Verify that the Stardock Multiplicity service is pointig to C:\PROGRA~1\Stardock\THINKD~1\MULTIP~1\MULTIS~1.EXE (or wherever you installed it). Is it started?
Reply #11 from Stardock Forums Top
If I telnet from the secondary to the primary, I get a response MULTIPLICITYPB. I get no response from the primary to the secondary. Both are version 1.05 of multiplicity, and both use port 30564. I have turned off all security to test. The service is pointed to C:\PROGRA~1\Stardock\THINKD~1\MULTIP~1\MULTIS~2.EXE which is where it is installed, and the service is started.

Thoughts?
Reply #12 from WinCustomize Forums Top

Did you get the B after MULTIPLICITYP instantly?

Make sure your connection password has been set on both as the B indicates incorrect password, but that could happen if you hit a key after the telnet.

I assume you have set the new machine up in the seamless dialog.  As you changed machines you may need to check settings like that.  What does MP say when you troubleshoot that connection from Multiplicity? (system tray icon on the primary)

Reply #13 from Stardock Forums Top
The B appeared after a second or so, then the message connection to host lost. I have no connection password on- in fact, I have no security on at all. Yes, the machine is set up in the seamless dialog. Now that you mention password, when I first installed it, it did say something about a password, but I checked to make sure there was no password set, and there was none. I tried it with a password just now, and made sure that they were correct, and still cannot connect, and still get the B when I telnet. The troubleshooting gives the same exact error- unable to contact (firewall?)

Anything else I can do?
Reply #14 from WinCustomize Forums Top

What if you manually enter the machines IP instead of using lookup ip?

Reply #15 from Stardock Forums Top
I've done that, and it doesn't help. This has actually always happened, thinking back- it's just that it used to be if I rebooted one machine or the other (or rarely both), they would begin to see each other, so I never worried about it. But now, that doesn't work...
Reply #16 from Stardock Forums Top
I might have stumbled onto the problem. I ran troubleshooting on the secondary, and I received the following errors:
Multiplicity Paths are NOT set correctly
Multiplicity Winlogon dll is NOT running
Winlogon dll has FAILED testing

What does this mean? Could this be the problem? If so, how do I fix it?

Thanks!
Reply #17 from Stardock Forums Top
Well, I uninstalled the application and all stardock applications, rebooted, and reinstalled, then rebooted again. It now works- and hopefully won't stop working again. Not really sure what was wrong, but just glad it works!

Thanks for all the help!