Multiplicity 2 Beta not connecting

Sounds like the same issue I'm having on one computer.

Is the computer that's showing the issue an XP computer with the stock windows firewall?

Please email support@stadock.com so we can get some data to see what the issue is.  Thanks.

{I edited your title to help track it.}

The Carnifex, I had MultiPro110 and had changed the exe file to 1,26 t so another PC could be added. Everything worked well with the Windows Firewall.

Installed Multi2 beta and it would not work. Installed Pro110 on the primary and the secondary and it will not work now. Discovered that instead of using the individual IP addresses that were assigned to each PC by the original edition of Multiplicity, Beta assigns an IP address that the PCs will not recognize. Each time the IP address was changed to the address for a particular PC, it reverted back to the IP that won't work. The Beta assigns the same IP to all the PCs, and there isn't any way to change the address to the correct one for each PC that I can find. Have contacted Support but no resolution yet that works. Tried one the tech suggested and it wouldn't work.

Multiplicity 2 defaults to doing lookups on the machine names to obtain the IP address.  It sounds like for whatever reason your network is returning bad addresses for these.  In that case simply delete the machines you added from the primary UI and add new machines using the IP address rather than the machine name in the add machine dialog.

I suspect if you open a command prompt on the primary machine and try to ping the name of the machines you would find it tries the bad IP address that Multiplicity was listing.

Neil, for some reason Multiplicity is trying to use for all PCs the IP address for the ISP which I use. It will not read the correct IP for each individual machine. I tried your suggestion and it does not work. Mult2 Beta has serious bug in it which has trashed my home net work connections.

Is you pc set to be in the dmz.

Multiplicity 2 makes no changes to your network setup other than opening the firewall ports.

How exactly has it trashed your home network connections?

The Beta changed some entries in the registry so that another program would not work. Not able to move files and text between the PCs so for all practical purposes the net network is trashed since it worked before the Beta install. I redid the registry on each PC with a backup file made a few days before for each PC. That helped three PCs to work. The display on each PC shows the correct PC, but that IP does not appear on the primary control window.

Removed the Beta and installed Multiplicity Pro 110, the primary can't find 3 of the secondary PCS. The IP of the 3 secondary PCs cannot be found by the primary.  The three secondary PCs are using an IP 67. ***. *. 132  which isn't the correct IP. The correct IP for each PC begins with 192.***.*.*** So far it is impossible to make the IP addresses stay changed due to reverting back to the wrong IP.

The beta version makes no changes to any other apps other than opening the firewall ports that MP2 uses (30564, 30565 and 30567).

Moving files and text between PCs, assuming you mean via the clipboard, is a function that is provided by the registered version of Multiplicity 2 only.  If you have purchased it then please make sure you clicked on the upgrade tab on the primary computer and entered your information.  Once activated the tab should go away and those features will be enabled.

Multiplicity 2 and 1 do not share registry keys for configuration so any changes made to the MP2 config will have no impact on your old MP1 settings.

BTW why are you using Multiplicity Pro 1.1?  Thats a very old version and if you wanted to go back to v1.x then 1.26 would be the version to revert to.

I am unclear on what you mean by IP addresses reverting back to the wrong IP.  Do you mean the secondary machine itself is using that IP, or do you mean Multiplicity on the primary is not remembering the IP for a secondary PC?  Is this with MP1 or MP2 as you are not especially clear in your posts.

If you open a command prompt on the secondary and type ipconfig what does it actually show for the IP addresses?  If you open a command prompt on the primary and try to ping the name of the secondary machine, what IP address does it try to ping?

Neil, MULTI Pro110 was installed in 2007 as an upgrade to the first addition. In February 2012, an exe. file 1.26 Mega Mode which Aaron Klenke sent to me in February replaced the original exe, file so I could add the 7th PC. It worked to perfection. 

The respective IP config for each PC is correct including the primary, but the primary when pinged returns the IP 67.215.65.132. All the secondary PCs when pinged show the correct IP.

The Multiplicity 2 applet window shows each secondary PC with the correct IP, but when Add is clicked, the IP shows the 67. 215.65.132. When the correct name and IP address for any given machine is entered in the applet window, it reverts to 67.215.65.132 as soon as it tries to connect. Beta was removed and 1.26 installed. The primary saw three PCs, but it could not see the others because it was also trying to connect to the other secondary PCs with 67.215.65.132.

Both M1.26 and M2 have the same problem of trying to use 67.215.65.132. M2 tries to use it for all secondary PCs and 1.26 tries to use it on 4 machines.

For what it is worth, when each PC is pinged from the primary, 67.215.65.132 returns. When the primary is pinged from any other secondary PC the return is 67.215.65.

The question that remains is how can it be fixed? I have removed and and installed, cleaned the registry with fine tooth comb. Nothing has worked.

I'm not seeing that issue.  The MP2 beta does show the correct IP address is on the XP machine and the machine name if I bring up the MP2 window from the system tray.  

As I mentioned in my other thread, 1.26 worked fine with the XP machine.  MP2 also works fine if I turn the XP firewall off.  With the XP firewall on, that's when the machine suddenly turns invisible, even disconnecting an already established connection.

To The Carnifex; After laboring nearly all day last Saturday, 7/28/2012 and installing M2 numerous times and turning Windows firewall off, it would not work. When the primary scanned for the secondary PCs it tried to connect each time with the the IP 67.215.65.132. When the correct IP for any given PC was entered, it would not recognize the correct IP and attempt to use the 67. IP. I gave up on it and re-installed 1.26 which took quite a bit of work to clear M2 from the registry. M1 is working again and does what I need. I use the copy folders and files feature of M1 so not having drag and drop is of no consequence. And neither is the sound feature since I use sound on only two PCs. One of them I use for sound editing.

Neil Banfield said in the post, 07/28, that M2 and M1 have no commonalty in the registry. I found  at least four cross referenced keys of M2 with M1. After removing the M2 keys that were in the M1 list, 1,26 installed and worked correctly. I didn't take the time to make a note of them and don't remember   which ones were referenced. I used C Cleaner and I0bit registry cleaners. C Cleaner found them. I used I0Bit on other removals and it found the same ones. One day I may try M2 again, but not any time soon.

I have been working with PCs for nearly 20 years, having built, repaired, and upgraded them. Have resolved software issues but nothing like this one. it has me totally stumped.