Unable to connect to Warpinator (after update to Warpinator)

[TeaDrinkingProgrammer]

A few weeks ago I installed Winpinator and it worked flawlessly. Sadly today I tried to send another file and it didn´t work. I think the update to warpinator I installed have something to do with it.
Steps:

1. Boot Warpinator on Linux machine
2. Boot Winpinator
3. Click on Warpinator on Linux to detect machine

Result:
When Winpinator starts searching machines, Warpinator says "Waiting for two-way connection". After a while, it says "Unable to connect". Winpinator doesn´t find the device at all and times out after a while.

[basianoamigo]

try this, restart winpinator on the windows pc, and then warpinator on linux, the windows pc must be active on the network first for warpinator to find it.
best regard

[fridayshoes]

try this, restart winpinator on the windows pc, and then warpinator on linux, the windows pc must be active on the network first for warpinator to find it. best regard

Tried this suggestion and it's not resolving the issue.

The Linux machine appears to be able to see the Windows machine (but can't connect). The Windows machine doesn't see the Linux machine at all.

[fridayshoes]

Linux machine can see and connect to Android fine. Android can see the Windows machine but can't connect. Windows machine can't see Android machine either.

[swiszczoo]

Can you check if Winpinator selects the correct network interface? Current automatic selection is quite broken. Like here, issue #11.

It seems that outgoing traffic is working fine but incoming does not work at all - when Winpinator starts, it notifies all devices on the network. However, when it asks for present devices, it doesn't receive anything at all. That can also mean that your firewall is blocking incoming traffic. I assume you're using Windows Defender, which is enabled by default. First, check if your current network is set to Private profile. Then check if there is a rule in Windows Defender that allows Winpinator to accept incoming connections on all ports. You should also ensure that it applies to at least Private network profile (double click a rule in Windows Defender, go to Advanced tab and there should be 3 checkboxes that specify profiles of the rule).

Hope that helps.

[PurifierUnit]

I have the same issue. Winpinator connections are permitted on all ports, and I have manually selected the correct network interface. By starting Winpinator first, I've managed to get the Windows side to see the Linux side, and it says the Linux side is ready, but Linux goes through what OP says: first "waiting for two-way connection", then "unable to connect". Files can't be transferred.