github-starred/lan-mouse

Fork 0

mirror of https://github.com/feschber/lan-mouse.git synced 2026-05-15 14:15:52 -06:00

[GH-ISSUE #305] Prebuilt lan-mouse.exe GUI cannot establish initial connection #156

New issue

Closed

opened 2026-05-05 22:11:59 -06:00 by gitea-mirror · 3 comments

gitea-mirror commented

2026-05-05 22:11:59 -06:00

Owner

Originally created by @gracchen on GitHub (Jun 20, 2025).
Original GitHub issue: https://github.com/feschber/lan-mouse/issues/305

I attempted to test Lan Mouse between two Windows machines (Windows 10 and Windows 11) using the prebuilt lan-mouse-windows.zip from the latest full release. Any pointers would be appreciated. The only thing I could get to work before is Microsoft Garage Mouse Without Borders, I couldn't get Barrier or Deskflows to connect successfully either.

Goal
Use one machine as the server (sender), and the other as the client (receiver)

Problem
The client side doesn't seem to receive any signals from the server no matter what I do.

Test setup
Both machines on same LAN (Windows 10 server = 10.0.0.68, Windows 11 client = 10.0.0.214)

Firewall fully disabled on both ends for testing

lan-mouse.exe run on both machines (only binary provided in .zip)

Config file provided on server side:

port = 4242

[[clients]]
position = "left"
hostname = "windows11-client"
ips = ["10.0.0.214"]
activate_on_startup = true

Observed behavior
Server log shows:

activated client 0 (left)
resolving (0) 10.0.0.214 ...
10.0.0.214: adding ip 10.0.0.214

But no alert or fingerprint prompt appears on the client gui.

Test-NetConnection -ComputerName 10.0.0.214 -Port 4242 fails (expected for TCP, but testing UDP manually also showed silence)

netstat -ano confirms UDP port 4242 is open on client:

UDP    0.0.0.0:4242    *:*    7200

Manually sent UDP packets to port 4242 via PowerShell — no response on client side (no logs, no network handling)

Originally created by @gracchen on GitHub (Jun 20, 2025). Original GitHub issue: https://github.com/feschber/lan-mouse/issues/305 I attempted to test Lan Mouse between two Windows machines (Windows 10 and Windows 11) using the prebuilt lan-mouse-windows.zip from the latest full release. Any pointers would be appreciated. The only thing I could get to work before is Microsoft Garage Mouse Without Borders, I couldn't get Barrier or Deskflows to connect successfully either. **Goal** Use one machine as the server (sender), and the other as the client (receiver) **Problem** The client side doesn't seem to receive any signals from the server no matter what I do. **Test setup** Both machines on same LAN (Windows 10 server = 10.0.0.68, Windows 11 client = 10.0.0.214) Firewall fully disabled on both ends for testing lan-mouse.exe run on both machines (only binary provided in .zip) Config file provided on server side: ``` port = 4242 [[clients]] position = "left" hostname = "windows11-client" ips = ["10.0.0.214"] activate_on_startup = true ``` **Observed behavior** Server log shows: ``` activated client 0 (left) resolving (0) 10.0.0.214 ... 10.0.0.214: adding ip 10.0.0.214 ``` But no alert or fingerprint prompt appears on the client gui. `Test-NetConnection -ComputerName 10.0.0.214 -Port 4242` fails (expected for TCP, but testing UDP manually also showed silence) `netstat -ano `confirms UDP port 4242 is open on client: ``` UDP 0.0.0.0:4242 *:* 7200 ``` Manually sent UDP packets to port 4242 via PowerShell — no response on client side (no logs, no network handling)

gitea-mirror closed this issue

2026-05-05 22:12:00 -06:00

gitea-mirror commented

2026-05-05 22:12:01 -06:00

Author

Owner

@gracchen commented on GitHub (Jun 21, 2025):

also sorry for an entirely irrelevant comment but - where is ubuntu release? I only see windows and mac.

@gracchen commented on GitHub (Jun 21, 2025): also sorry for an entirely irrelevant comment but - where is ubuntu release? I only see windows and mac.

gitea-mirror commented

2026-05-05 22:12:02 -06:00

Author

Owner

@feschber commented on GitHub (Jun 25, 2025):

This might be a firewall configuration problem.
Could you try whitelisting UDP/4242? (Tcp is irrelevant)

also sorry for an entirely irrelevant comment but - where is ubuntu release? I only see windows and mac.

I have not setup a build process for .deb packages yet. For now, you have to manually install it or use nix.

@feschber commented on GitHub (Jun 25, 2025): This might be a firewall configuration problem. Could you try whitelisting UDP/4242? (Tcp is irrelevant) > also sorry for an entirely irrelevant comment but - where is ubuntu release? I only see windows and mac. I have not setup a build process for `.deb` packages yet. For now, you have to manually install it or use nix.

gitea-mirror commented

2026-05-05 22:12:02 -06:00

Author

Owner

@feschber commented on GitHub (Jun 25, 2025):

Firewall fully disabled on both ends for testing

Ah I missed that part...

Could you run it with trace logs enabled?

That would be

$env:LAN_MOUSE_LOG_LEVEL=trace lan-mouse

in powershell

@feschber commented on GitHub (Jun 25, 2025): > Firewall fully disabled on both ends for testing Ah I missed that part... Could you run it with trace logs enabled? That would be ```ps1 $env:LAN_MOUSE_LOG_LEVEL=trace lan-mouse ``` in powershell