github-starred/barrier

Fork 0

mirror of https://github.com/debauchee/barrier.git synced 2026-05-15 14:16:02 -06:00

[GH-ISSUE #768] Barrier showing multiple IP addresses on Windows (Server Side) #602

New issue

Open

opened 2026-05-05 06:45:47 -06:00 by gitea-mirror · 6 comments

gitea-mirror commented

2026-05-05 06:45:47 -06:00

Owner

Originally created by @ghost on GitHub (Jun 25, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/768

IMPORTANT NOTE : The issue is caused by Windows. I have just tested barrier across two Linux systems and it was working fine. Both of the two Linux system are reporting only one IP address that is also bolded.

Operating Systems

Server: Windows 10 Enterprise N 1909 18363

Client: Debian 10.2 KDE

Barrier Version

Windows Version 2.3.2-snapshot-210c2b70
Linux Version 2.2.0-Release-00000000

Steps to reproduce bug

I pick the Windows machine to be a Server (share it's mouse and keyboard)
Under the "IP addresses" I see multiple entries one with bolded text
The IP with bolded text is the VMware Adapted for Virtual Machines
The other IP addresses are also adapters for different program that require networking protocols access
The last IP is the IP address of the actual computer on the local network.
I don't know which IP address to fill in when filling the "Server IP" on the Client (Linux Debian) machine.

Other info

Previously I've encountered the "Cannot write into configuration file bug" error that occurred only on Windows. I used a workaround fix in which you interactively configure the server after that you save the configuration into a file manually and then you mark "Use existing configuration" with the proper path to the configuration file
When I fill in the original IP address of the computer and click "Start" on both ends I see the "Barrier is starting" text and the "Start" button changes to "Stop" but I don't see any connection happening
Does this bug prevent you from using Barrier entirely? > Yes

I don't see any error messages popping up. I've also setup the next client in the "Configure Server" window, properly positioned the location of the other monitor and renamed it's "Screen name" to the one I see written in the client's side. I am not sure if I'm filling the IP address in properly since there is multiple IPs.

Originally created by @ghost on GitHub (Jun 25, 2020). Original GitHub issue: https://github.com/debauchee/barrier/issues/768 IMPORTANT NOTE : The issue is caused by Windows. I have just tested barrier across two Linux systems and it was working fine. Both of the two Linux system are reporting only one IP address that is also bolded. ### Operating Systems ### Server: Windows 10 Enterprise N 1909 18363 Client: Debian 10.2 KDE ### Barrier Version ### Windows Version 2.3.2-snapshot-210c2b70 Linux Version 2.2.0-Release-00000000 ### Steps to reproduce bug ### 1. I pick the Windows machine to be a Server (share it's mouse and keyboard) 2. Under the "IP addresses" I see multiple entries one with bolded text 3. The IP with bolded text is the VMware Adapted for Virtual Machines 4. The other IP addresses are also adapters for different program that require networking protocols access 5. The last IP is the IP address of the actual computer on the local network. 6. I don't know which IP address to fill in when filling the "Server IP" on the Client (Linux Debian) machine. ### Other info ### * Previously I've encountered the "Cannot write into configuration file bug" error that occurred only on Windows. I used a workaround fix in which you interactively configure the server after that you save the configuration into a file manually and then you mark "Use existing configuration" with the proper path to the configuration file * When I fill in the original IP address of the computer and click "Start" on both ends I see the "Barrier is starting" text and the "Start" button changes to "Stop" but I don't see any connection happening * Does this bug prevent you from using Barrier entirely? > Yes I don't see any error messages popping up. I've also setup the next client in the "Configure Server" window, properly positioned the location of the other monitor and renamed it's "Screen name" to the one I see written in the client's side. I am not sure if I'm filling the IP address in properly since there is multiple IPs.

gitea-mirror commented

2026-05-05 06:45:51 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (Sep 18, 2020):

This issue has been automatically marked as stale due to inactivity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions[bot] commented on GitHub (Sep 18, 2020): This issue has been automatically marked as stale due to inactivity. It will be closed if no further activity occurs. Thank you for your contributions.

gitea-mirror commented

2026-05-05 06:45:53 -06:00

Author

Owner

@p12tic commented on GitHub (Jan 10, 2021):

Let's not close valid bugs without a valid reason.

Barrier probably binds to the VMware adapter and waits for connections there.

@p12tic commented on GitHub (Jan 10, 2021): Let's not close valid bugs without a valid reason. Barrier probably binds to the VMware adapter and waits for connections there.

gitea-mirror commented

2026-05-05 06:45:56 -06:00

Author

Owner

@lrvl commented on GitHub (Apr 29, 2021):

Same problem. The bold IP on the Windows server points to Hyper-V Virtual Ethernet Adapter instead of LAN.

@lrvl commented on GitHub (Apr 29, 2021): Same problem. The bold IP on the Windows server points to Hyper-V Virtual Ethernet Adapter instead of LAN.

gitea-mirror commented

2026-05-05 06:45:58 -06:00

Author

Owner

@mhmdibrahimm commented on GitHub (May 2, 2021):

@lrvl
I had the same problem, I just disabled the adapters in my Windows Device Manager settings, and now it is showing one IP address.

@mhmdibrahimm commented on GitHub (May 2, 2021): @lrvl I had the same problem, I just disabled the adapters in my Windows Device Manager settings, and now it is showing one IP address.

gitea-mirror commented

2026-05-05 06:46:00 -06:00

Author

Owner

@brice-gros commented on GitHub (May 10, 2021):

Same here with VirtualBox host-only adapter, the only workaround I found is to specify the correct server ip address manually on the client (i.e. not using the auto config)
Being able to specify the ip address to be advertised by the server would help mitigate the issue.

@brice-gros commented on GitHub (May 10, 2021): Same here with VirtualBox host-only adapter, the only workaround I found is to specify the correct server ip address manually on the client (i.e. not using the auto config) Being able to specify the ip address to be advertised by the server would help mitigate the issue.

gitea-mirror commented

2026-05-05 06:46:02 -06:00

Author

Owner

@gwillen commented on GitHub (Jun 9, 2021):

I'm also seeing this -- note that the server DOES bind all addresses, the bolded one seems to just be the one that it advertises to autoconfig clients. So manually telling the client the correct IP is sufficient.

Ironically, the client could possibly do better by just using the source IP that it gets the advertisement from, and ignoring the IP provided by the server. (I'm not familiar with the underlying protocol here.)

@gwillen commented on GitHub (Jun 9, 2021): I'm also seeing this -- note that the server DOES bind all addresses, the bolded one seems to just be the one that it _advertises_ to autoconfig clients. So manually telling the client the correct IP is sufficient. Ironically, the client could _possibly_ do better by just using the source IP that it gets the advertisement from, and ignoring the IP provided by the server. (I'm not familiar with the underlying protocol here.)

No labels

Rows
Columns