I am using kernel 220.127.116.11 on two different windows 10 machines. Between the two I cannot get either one's gui to connect to the others kernel. Here is what happens:
Computer 1 kernel running, local gui connected
Computer 2 gui sees the server on network, attempt connection
Computer 1 and 2 gui's stop responding for about 25 seconds
Computer 2 gives generic windows ding, both gui's now respond.
Computer 2 gui is not connected, but the Computer 1 kernel reports 2 sessions being connected despite no session event ever appearing in the kernel window.
Both gui's report the kernel as having two sessions as well. If I attempt another connection gui #2 warns of a session with the same name existing.
At no point can I get the second gui to do anything more than stop responding, beep, and then go back to responsive showing no change. Firewalls are off for testing.
Gui 2 logs say timeout when registering session. I don't seem to have any network connectivity issues otherwise. One is wired, one is wireless, same subnet, there are smb shares between them, pings respond, everything appears normal, the gui server lists pick up the kernels but neither one will connect to the other kernel with the same results and log either direction.
Is it possible this is a windows 10 bug on either the kernel or gui side? I have a 7 vm I will try to test with.