FYI, I see that MpVista64.exe is 8/17/*2005* Since I'm running Vista x64, would this possibly be the cause of the problem? When I check task manager, I see both multipl.exe *32 and MpVista64.exe processes are running.
No, it's not an option for those of us on a domain. Will Multiplicity work with the new Vista Ctrl-Alt-Del logon in the future? My multipl.exe version is 10/17 1.1.0.0. My multisrv32.exe and multisrv64.exe and multiwin32.dll and multiwin64.dll versions are 8/28 1.0.3.0. I have a fresh install of 1.10.009 11/2 via Stardock Central on both machines. Are any of these files out of date?
I'm having a series of issues using Multiplicity Pro with a Vista Enterprise secondary machine on a domain: * Cannot log in at the Ctrl-Alt-Del prompt, Ctrl-Alt-Backspace does not work * Connection to the secondary seems to get dropped frequently. Upgrading both sides to 1.10 from 1.06 helped this issue, but didn't solve it. * I frequently have connection problems when the Vista secondary is in screen saver or locked console mode. * One symptom is the connection will
*ping* I'm also a licensed multiplicity pro user being bit by this. Like others, my Vista machine is part of a domain so I don't have the option of switching logon screens.
OK, so I've talked a bit about my "laptop woes" in the past. I think these come down to DHCP reassigning me a new IP address too often as I cross wireless router zones (going from home to work to home or going from building 1 to building 2...) combined with DHCP -> Dynamic DNS registration of these IP addresses not really working like it should (it's very frequent for me to ping my machine name and have an entirely different machine with my old IP address respond). I'd like to sugges
Hey team, thanks for this update! I've noticed that I get reconnected to my secondaries much better now and I also immediately noticed how much better Copy/Paste across machines is working! I'm still running into issues with my laptop when it has multiple NICs (wireless and wired) and issues with my DHCP -> dynamic DNS registration being out of date so I have to manually change my ip address of my laptop secondary almost every time I connect. These aren't really Multiplicity's fault
FYI, I think your "too quick at switching machines" statement was accurate. Since I've been consiously 'a little more leisurely' after Ctrl-C, things have been working well for me. Thanks for the help.
RE: multiple NICs Yes, I've tried telneting to the 2nd NIC's port and it didn't work. I do not get a connect. I've set Multiplicity to allow any IP to connect. Since you're already listening on INADDR_ANY, perhaps this is related to not hooking Address Changed events and restarting your listener. If you open a socket to listen and then the ip address on the nic changes, the socket is no longer listening even though you requested to listen to INADD
Multiplicity has serious bugs. The one's I've personally hit are: Does not listen on all network interfaces. If your computer has more than one network interface, it listens only on Network Interface #0. Particularly troublesome for laptops that have a wired NIC and a wireless NIC. Does not listen for network interface change events. If an IP address changes on a computer, Multiplicity stops working. This is troublesome for la