[GH-ISSUE #183] Can't connect to Windows via Linux, "os error 10040" #83

New issue

Closed

opened 2026-05-05 22:08:29 -06:00 by gitea-mirror · 4 comments

gitea-mirror commented

2026-05-05 22:08:29 -06:00

Owner

Originally created by @TheGershon on GitHub (Aug 29, 2024).
Original GitHub issue: https://github.com/feschber/lan-mouse/issues/183

Posting from my Windows machine, here's my configuration:

Linux machine is the same except the connection is set to the Windows IP (192.168.0.207). When I try to move the mouse over to Windows from Linux, I get this output on Windows:

[2024-08-29T16:58:03Z INFO  lan_mouse::config] using config: "C:\Users\TheGershon\AppData\Local\lan-mouse\config.toml"
[2024-08-29T16:58:03Z INFO  lan_mouse] release bind: [KeyLeftCtrl, KeyLeftShift, KeyLeftMeta, KeyLeftAlt]
[2024-08-29T16:58:03Z INFO  lan_mouse::config] using config: "C:\Users\TheGershon\AppData\Local\lan-mouse\config.toml"
[2024-08-29T16:58:03Z INFO  lan_mouse] release bind: [KeyLeftCtrl, KeyLeftShift, KeyLeftMeta, KeyLeftAlt]
[2024-08-29T16:58:03Z INFO  lan_mouse] Press [KeyLeftCtrl, KeyLeftShift, KeyLeftMeta, KeyLeftAlt] to release the mouse
[2024-08-29T16:58:03Z INFO  lan_mouse::server] running service
[2024-08-29T16:58:03Z INFO  input_capture] using capture backend: windows
[2024-08-29T16:58:03Z INFO  lan_mouse::server::emulation_task] creating input emulation...
[2024-08-29T16:58:03Z INFO  input_emulation] using emulation backend: windows

(lan-mouse.exe:21492): GLib-GIO-WARNING **: 09:58:03.631: win32 session dbus binary not found
[2024-08-29T16:58:09Z INFO  lan_mouse::server] added client 0
[2024-08-29T16:58:20Z INFO  lan_mouse::dns] resolving (0) `192.168.0.208` ...
[2024-08-29T16:58:20Z INFO  lan_mouse::dns] 192.168.0.208: adding ip 192.168.0.208
[2024-08-29T16:58:24Z WARN  lan_mouse::server::ping_task] client not responding, releasing pointer!
[2024-08-29T16:58:32Z WARN  lan_mouse::server::emulation_task] network error: network error: `A message sent on a datagram socket was larger than the internal message buffer or some other network limit, or the buffer used to receive a datagram into was smaller than the datagram itself. (os error 10040)``

(The last line repeats itself on every attempted movement, I've removed the repeated lines for readability)

When trying to move the mouse from Windows to Linux I simply get the client not responding, releasing pointer! line repeating.

On Linux to Windows, I get WARN lan_mouse::server::emulation_task] network error: invalid event id: `8 repeating.

Windows side is Win 10, Linux side is Arch Linux w/ KDE Plasma 6 & Wayland. input emulation is running via libei, but I've tried xdg and gotten the same result. I've made sure Windows Firewall isn't blocking anything as well.

Originally created by @TheGershon on GitHub (Aug 29, 2024). Original GitHub issue: https://github.com/feschber/lan-mouse/issues/183 Posting from my Windows machine, here's my configuration: ![image](https://github.com/user-attachments/assets/e09ed000-ad9e-4f5f-be68-b1614f6cd717) Linux machine is the same except the connection is set to the Windows IP (192.168.0.207). When I try to move the mouse over to Windows from Linux, I get this output on Windows: ``` [2024-08-29T16:58:03Z INFO lan_mouse::config] using config: "C:\Users\TheGershon\AppData\Local\lan-mouse\config.toml" [2024-08-29T16:58:03Z INFO lan_mouse] release bind: [KeyLeftCtrl, KeyLeftShift, KeyLeftMeta, KeyLeftAlt] [2024-08-29T16:58:03Z INFO lan_mouse::config] using config: "C:\Users\TheGershon\AppData\Local\lan-mouse\config.toml" [2024-08-29T16:58:03Z INFO lan_mouse] release bind: [KeyLeftCtrl, KeyLeftShift, KeyLeftMeta, KeyLeftAlt] [2024-08-29T16:58:03Z INFO lan_mouse] Press [KeyLeftCtrl, KeyLeftShift, KeyLeftMeta, KeyLeftAlt] to release the mouse [2024-08-29T16:58:03Z INFO lan_mouse::server] running service [2024-08-29T16:58:03Z INFO input_capture] using capture backend: windows [2024-08-29T16:58:03Z INFO lan_mouse::server::emulation_task] creating input emulation... [2024-08-29T16:58:03Z INFO input_emulation] using emulation backend: windows (lan-mouse.exe:21492): GLib-GIO-WARNING **: 09:58:03.631: win32 session dbus binary not found [2024-08-29T16:58:09Z INFO lan_mouse::server] added client 0 [2024-08-29T16:58:20Z INFO lan_mouse::dns] resolving (0) `192.168.0.208` ... [2024-08-29T16:58:20Z INFO lan_mouse::dns] 192.168.0.208: adding ip 192.168.0.208 [2024-08-29T16:58:24Z WARN lan_mouse::server::ping_task] client not responding, releasing pointer! [2024-08-29T16:58:32Z WARN lan_mouse::server::emulation_task] network error: network error: `A message sent on a datagram socket was larger than the internal message buffer or some other network limit, or the buffer used to receive a datagram into was smaller than the datagram itself. (os error 10040)`` ``` (The last line repeats itself on every attempted movement, I've removed the repeated lines for readability) When trying to move the mouse from Windows to Linux I simply get the `client not responding, releasing pointer!` line repeating. On Linux to Windows, I get ```WARN lan_mouse::server::emulation_task] network error: invalid event id: `8``` repeating. Windows side is Win 10, Linux side is Arch Linux w/ KDE Plasma 6 & Wayland. input emulation is running via libei, but I've tried xdg and gotten the same result. I've made sure Windows Firewall isn't blocking anything as well.

gitea-mirror closed this issue

2026-05-05 22:08:30 -06:00

gitea-mirror commented

2026-05-05 22:08:31 -06:00

Author

Owner

@feschber commented on GitHub (Aug 29, 2024):

Are you using the same version of lan-mouse on both ends? There have been some changes to the protocol in latest master

@feschber commented on GitHub (Aug 29, 2024): Are you using the same version of lan-mouse on both ends? There have been some changes to the protocol in latest master

gitea-mirror commented

2026-05-05 22:08:32 -06:00

Author

Owner

@TheGershon commented on GitHub (Aug 30, 2024):

Yes, both are running 0.9.1

EDIT: Silly me, I installed on linux via pacman and despite both reporting version 0.9.1 via -V the Windows version was actually the latest dev build. Using that version on Linux fixed the problem, so closing.

@TheGershon commented on GitHub (Aug 30, 2024): Yes, both are running 0.9.1 EDIT: Silly me, I installed on linux via pacman and despite both reporting version 0.9.1 via `-V` the Windows version was actually the latest dev build. Using that version on Linux fixed the problem, so closing.

gitea-mirror commented

2026-05-05 22:08:33 -06:00

Author

Owner

@feschber commented on GitHub (Aug 30, 2024):

Yeah I should probably somehow include the commit hash in the version

@feschber commented on GitHub (Aug 30, 2024): Yeah I should probably somehow include the commit hash in the version

gitea-mirror commented

2026-05-05 22:08:34 -06:00

Author

Owner

@matthewtapps commented on GitHub (Nov 25, 2024):

I am getting this error when using a Linux host and connecting to a Windows client with both systems using version 0.10.0 - I have also tried 0.9.1 but no luck there either. On the Linux side it says the client isn't responding, on the Windows side it gives the network error/ os error 10040.

@matthewtapps commented on GitHub (Nov 25, 2024): I am getting this error when using a Linux host and connecting to a Windows client with both systems using version 0.10.0 - I have also tried 0.9.1 but no luck there either. On the Linux side it says the client isn't responding, on the Windows side it gives the network error/ os error 10040.

gitea-mirror referenced this issue

2026-05-05 22:16:54 -06:00

[PR #202] [MERGED] MacOS Multimonitor support #327