Vista_B2 x64 on Remote

I am not sure that particular setup has been tested.

Do you have a file called MpVista64.exe in your Multiplicity directory?

Thanks for your reply!

Yes, I have \program files(x86)\Stardock\Thinkdesk\Multiplicity\MpVista64.exe

It is listed as Modified: August 17, 2005.

After executing MpVista64.exe on the VistaBeta2x64 remote, the troubleshooting report shows Winlogon.dll is both running and has passed testing.

However, the XP_SP2 32-bit machine cannot connect - Multiplicity sees theVistaBeta2x64 remote as a secondary machine to be remotely controlled, attempts to connect to it, but never actually does connect (there are no error messages).

Make sure the firewall is set to allow Multiplicity access.  Vistas firewall may need manual configuring.

Any guidance as to how I can modify Vista's firewall settings? Thankx.

I "turned off" windows firewall on BOTH the remote (vista x64) and the primary (xp-sp2) ............ I have no 3rd party firewall running on either machine. Result is I still cannot connect to remote from primary machine. Any other suggestions - many thankx !

Running the "Troubleshooting" routine from the primary PC it responds that it was able to connect without any problems.

Running the "Troubleshooting" routine on the remote PC everything is also OK.

Problem is that I cannot move the cursor from the primary over to the remote (whereas I was able to do so to same remote PC before I re-formatted it as vista x64) - Multicity icon on the primary is not highlighted and indicated as ("disconnected").

You have set that machine to be positioned to the left or right of the primary?

Interface tab-> Seamless mode-> Configure

 

Issue resolved .............. thanks very much (I had not set the monitor position for the remote). User error the whole time !!! Thanks very much for your patience and assistance.

I had not set the monitor position for the remote

I did that once too. The sound of the slapping of the forehead was proportional to the time I had spent reinstalling and configuring. Very, very, loud.

Neil, How about a internal check and an alert somewhere if you are a doofus like me and forget. Or set a default for the secondary system to the left of primary?