Hello,

I have forwarded your report to the Stardock support team for their review and recommendations.

Please keep an eye on this thread for any updates.

We really do appreciate your feedback, thanks.

It is a fine KB article and Im confident it does help the vast majority of issues. It just doesnt even mention the possibility of anything else or what to do to seek further help.

I went to stardock's site and there is no chat support, no phone support, and even no email.

In the past, when I have reached out to communities, 90% of my questions never get a reply and there is nothing I can do to seek vendor assistance.

If your policy is for customers to seek help on the forum and have the moderators forward them as appropriate to the vendor's support team. then thats fine. Its just that there is no mention of this policy anywhere, and I dont have any other vendors that do this so I had no idea this was even possible.

Anyway, heres the info you requested and why I dont think its fw related.

Primary and secondary are both static IP addressed and I connect by IP (removes host resolution issues). I dont need/have VPN installed

Doing a netstat -ano on the secondary shows that port 30564. 30565 and 30569 open and in listening state. I even confirmed this by telneting to the ports from my primary. No problem at all.

Port 30567 is not in listening state and I presume thats because I didnt choose to get remote audio.

Given all other listed ports are open, I am fairly comfortable with this not being a fw issue.

Now I have had symptoms long before I finally lost complete access.

Daily I would get the following intermittant issues:

1) Connect 5 times fine. 6th time no keyboard but mouse moves. All further connection attempts have no keyboard

     resolution: remote console in and then logout. Now remote keyboard works again

2) When keyboard fails, so does pressing ctl-alt-del button on title bar

     resolution: same as #1

3) Get Win 10 notifications on primary occasionally from multiplicity saying something about authentication. It goes away too fast to read. However there is no impact other than nuisance

4) When I get #1/#2, remoting in and restarting the multiplicity service doesnt help. Usually it required a logout or reboot. However for the past 2 weeks I cant get keyboard to work ever.

At this point I uninstalled both primary / secondary and reinstalled. No difference

I guess it could in theory be bug in the latest version. While I always had flaky connections over the past few years shortly after upgrading to the latest version I had complete keyboard loss. I cant say that the two are tied. I dont remember it happening immediately after the upgrade.

I am a device driver engineer that wrote the entire TCPIP stack for OS/2 Warp back and for Novell Netware back in the day. I feel comfortable following any steps you suggest. I have wireshark already loaded. If you want a trace, I can send it. Just tell me what port the keyboard uses.

Thanks for any help

Hi,

I did see the autoresponder. I didnt interpret it as the vendor would be responding in the forums. I thought it would be volunteers, thus I said there appears to be no way to reach the vendor. Either way, since you are using the forums, everything is fine.

i am in kvm mode running 3.37 on both machines on hardwired 1gb ethernet.

However, for the past 2 days it has been working perfectly (without any firewall changes)

The only thing i did do was wander through all the settings and decided out of boredom to change the default encryption code from "changeme". I verified it was changeme on both machines, so i changed it. Now the secondary already had the checkbox unchecked saying "require authenticated connections", so i assumed it would use no encryption if the passcodes were different (which they werent)

Instantly everything is working. Now whats even stranger is that AFTER changing the encryption passcode, I changed it to different values to see what the behavior is. Now, I get a message saying codes dont match (or something similar) and the remote display never shows up.

This is different than seeing a desktop with a moving mouse but no interaction with the desktop.

In the end, things seem to be very stable now. Even reenabling the f/w on both machines and AV is not bothering it.

So Im happy to consider this issue closed