Windows Client not accessible from Linux System on same network

We installed the Windows Client on a Windows 11 System and added it to a Husarnet Network. We had set the windows client to be able to SSH directly into WSL (Ubuntu 22) running on it. However, we are not able to SSH into it from another Linux Box.
On closer inspection we observed that the Windows Box is not being added to the /etc/hosts of the Linux systems. That means Linux systems will not be able to contact any Windows Systems at all.
Is this behaviour built into the Husarnet System? How can this issue be resolved?

Hello,
thank you for the report. No, it should work.

Can you please provide which version Husarnet clients report on both systems?
Have you tried SSH-ing using IPv6 address and not the hostname?

Best regards,
Szymek

How to check the version on Windows?

It should be visible in “Add or remove programs” or in similar area, program reports its name as “Husarnet version x.x.x.x”. Also if you start your installer exe you should see it in title bar of the window.

BR,
Szymek

Windows Client Version: 2021.11.26.1
Ubuntu Client Version: 2021.11.26.1

Where can I get the IPv6 hostname on windows?

Similarly as in Linux version, executing husarnet status in console should report Husarnet IPv6 address.

Additionally, it will be good idea to check your hosts file, please paste the contents here. On Windows its path is C:\Windows\System32\drivers\etc\hosts

BR,
Szymek

Hi ympek,

We’re not able to ssh via the IPv6 address either.
Here’s the content for the hosts file from windows:

# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
#      102.54.94.97     rhino.acme.com          # source server
#       38.25.63.10     x.acme.com              # x client host

# localhost name resolution is handled within DNS itself.
#	127.0.0.1       localhost
#	::1             localhost
0000:0000:0000:0000:0000:0000:0000:0001 ppmt_windows_server # managed by Husarnet
<IPv6_address_redacted_for_security> abhishek # managed by Husarnet
<IPv6_address_redacted_for_security> master # managed by Husarnet

Hello,
the hosts file doesn’t look exactly healthy, but if you can’t SSH using IPv6 the problem lies deeper.

Does the web frontend (app.husarnet.com) see the Windows box as “Online”?

Here I would suggest you attach the client logs to analyze. On Windows they are in %PROGRAMDATA%\husarnet (typically it will be C:\ProgramData\husarnet)

The best would be to compress the whole husarnet folder to ZIP or other archive format. You can then send it to support@husarnet.com in order to protect the sensitive parts. We will continue through email and after we solve the problem, we will share the summary in this thread later.

Thank you,
Szymon from Husarnet team

My Windows PC is always visible as Offline in app.husarnet.com, but communication with ESP32 devices is possible.