Ok, i was afraid this might happen on Windows in the newest patch. It looks like it's stuck in an update loop. It retrieves the newest peers, re-sets it's interface, which changes its own port, and that causes the other windows machine to update and change their port, and then it goes back and forth like that.