In response to your various points.
Multiplicity uses the INADDR_ANY address on the secondary machines when listening for a connection. I believe this is the correct method for listening to all NICs and testing on machines with multiple network interfaces has shown this works correctly. Have you tried telnet into the remote pcs and see if you get any response on the MP port? It may be the machine is listening, but is then rejecting you based on IP address. In which case you will get a connect before it disconnects you.
Are we talking about a primary or secondary machine changing IP address? On the primary, the connection is reestablished when connection is lost (as it would be if you changed IP address I suspect) and the secondary doesn't care what its local IP address is (as it does not bind to any one specific address) apart from when it processes new incoming connections & you have the local subnet setting on. But that setting obtains the IP addresses from the local PC each time.
The problem with some extended keys (though not left ctrl - that one worked) has been found internally and resolved in the 1.04 beta that kris has mentioned. The problem occured if you held down the keys, switched pcs and then released the keys as the original machine never got a key up event.
On the subject of Intellitype, the new 1.04 build extends support for this and now supports many of the additional MS keyboard keys being passed to secondary machines if the secondary machines also have Intellitype installed. Likewise support for Intellimouse is extended.
The copy paste issue may be related to something else which is fixed in the 1.04 build. The fix is actually related to MP detecting disconnects, but testing with a user who had problems found it also helped them with some unpredicable clipboard problems they were having.
I recall mention of multiple DNS entries for the one PC in a mail. This is something we never considered as its somewhat unusual. We will see about implementing support for this, but it does require some changes to how MP connects to machines.
Regarding the comment on Galciv2, nobody who works on the MP code was moved onto GalCiv2, but there was a problem with internal testing of updates which caused a backlog problem. The developers have not been idle in this time as the 1.04 build shows. There are also some internal changes added for some features which will probably be added in the 1.1 release.
