Logitech Flow problem

BartZorn said:

Hello,
I have a local network, part wired and part wireless. Core of the network is a TP-link unmanaged gigabit switch, so tools like wireshark will not be very effective.
I am trying to setup Logitech Flow between my laptop (wireless) and my media server (both wired and wireless). Both are running Windows 10 version 1909, with all updates. All types of network functions that I use work without problems, except Logitech Flow.
I have a Logitech M590 mouse, connected to my laptop via Bluetooth and the the media server via the Unifying receiver (shared with a Logitech k400r keyboard). Switching between the two systems is no problem. But when I try to setup Flow, both computers insist that they cannot find each other.

Both computers are connected to the Internet.

What could I be missing here? Has anyone seen similar problems?

The Logitech website does not seem to be very helpful here.

Thanks,

Bart

Windows 10 Pro Version 1909 (OS build 18363.778)

I had plenty of troubles with peer discovery on Logitech Flow and have a solution that works for me repeatably. It may not be technically a "fix", but it works and I thought I'd pass it along in case it helps others.

My Win 10 Pro machine has both, wireless and Ethernet networking capabilities. I only usually connect via Ethernet. In order to get Flow to discover peers, I connect to the wireless network on my main PC, and Flow discovers peers and works on all machines. I can then disconnect from wireless and go on about my business.

I have the flow icon displayed in the system tray. When I reboot, I see an "X" indicating a problem with Flow. I connect to the wireless, the "X" changes to the normal icon, then I disconnect and the icon stays normal.

I use Resource Monitor to watch the listening ports and connections. When wireless is established, I see the TCP connection has been established with the remote machine - which is what Flow needs to do. As I understand it, LogiOptionsMgr uses UDP to establish a connection and when it's established makes a TCP connection - prior to enabling wireless, UDP was unable to find the remote machine.

After searching high and low for weeks and weeks, this method resolves the issue.

Your mileage may vary.

BartZorn said:

Thanks!

So your finding is that both partners need a wireless connection to be able to find each other. In other words, the switch is the problem here.

I will have to add a wireless adapter to my media center, so I will do that later.

I will report the result here.

Regards,

Bart

I wouldn't have phrased it like that. To be clear, I have two machines, one is a Win 7 running on a machine without wireless capabilities. The other is a Win 10 with wireless. On the Win 10 machine, I connect to the wireless network, then bam, it's done. Then I disconnect until I reboot.

Both peers do not need to be wireless, as I've mentioned, one of the machines is not capable.

BartZorn said:

Hmm...

That is very similar to what I am trying to do. My media center is an ordinary PC without a wireless adapter.
My laptop does not have a wired adapter. Both are running the latest Windows 10 Pro.
No way that Logitech Flow is able to find a peer.

Although Flow could be nice to have, it is far from an essential tool.

I will see if Logitech ever comes with an update.

Regards,

Bart

Yeah, in my case, I have at least one machine with both adapters.