Remote Kernel connection not functional

  • I am using kernel 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.

  • Railtracer

    Please try to open the Ports 12351 on your Kernel computer and the Port 12451 on the GUI Computer. These are the ports used to connect. If the Windows firewall blocks them no connection is possible. Alternatively you can disable the firewall completely. Maybe you can disable the firewall to check whether that solves the issue and in case it does, go the more secure approach of just opening the ports that DMXControl needs.



  • I will grab you the log files of the connecting gui. Does the Kernel keep its own log by default? I will put it up as well if that is the case Soon5 I have disabled the firewall on the target kernel and the connecting gui in my tests and unfortunately got the same results. Thanks for the replies.

  • Alright, I finally figured it out. Slightly obscure of course. Since I am connected to my home network, and windows 10 viewed the network at a private network, I assumed just turning off the windows defender firewall on the private network category would do the trick. Funny story there....This laptop is running a hyperv instance and as such actually interfaces with the network via a virtual ethernet switch in hyperv which the machine chose to reference as a public network by officially that was the active firewall...shut off public firewall and got connected immediately, so of course it was always a firewall issue, it was the only thing that made sense anyways. Thanks again.