I just installed the latest version of Slowroll. The only issue I am having is that the computer can’t be pinged by other computers (all those run Windows 10) on the LAN by its DNS name. I receive «host can’t be found» messages. However, should I use the IP-address in stead of the DSN name, ping requests are successful.
Temporary disabling firewall did not remedy the situation.
I would appreciate any ideas of what else can be tried (I must admit my knowledge about networking to be very limited, so please do not be too laconic).
P. S. The computer with OpenSuSE is connected via Wi-Fi, if it matters.
P. P. S. I found a few threads with similar questions on this forum (it is curious that the most recent of them is ten years old, apparently, my problem is not very common nowadays), no solution has worked for me (or, I was unable to understand what to do exactly).
As you explain it, the Windows systems can not resolve the hostname (you do not mention it) into the IP address. Which is a problems in the Windows systems, not in the openSUSE (please remark how it is spelled) system. Maybe the one responsible for managing the DNS server used by those Windows systems did not add the system into the DNS database.
When you get the connection name do this:
nmcli con show myconnectionname|grep hostname
^does this send hostname for ipv4 and also have an ipv4 hostname set?
if not,
nmcli con modify myconnectioname ipv4.dhcp-send-hostname yes
Or something similar. I’ve not tested it myself. This assumes I guess that the windows dns is set to your router and you don’t have multiple routers and such making it more complicated
Perhaps a silly question, but what are you using for DNS in your local area network?
Is there an A record in the DNS server for the hostname? If there is, does the IP address actually match the host’s address?
Firewall wouldn’t make a difference - if you can ping by IP address, the host will respond to ping regardless of whether you use the name or the IP address.
Name resolution happens before any ICMP packet is sent to the host. The hostname is never used in the packet itself in order for it to traverse the network - it always resolves first, gets an IP address, and then uses that to send the request - that’s the foundation of how network routing works (it doesn’t work by DNS names at all).
If desired you could make use of Avahi hostname resolution. You will need to allow ‘mdns’ if the linux host has an active firewall. By default, it takes the form ‘hostname.local’.
As you explain it, the Windows systems can not resolve the hostname (you do not mention it) into the IP address. Which is a problems in the Windows systems, not in the openSUSE (please remark how it is spelled) system. Maybe the one responsible for managing the DNS server used by those Windows systems did not add the system into the DNS database.
Another distribution of Linux was installed on this computer before openSUSE (by the way, thank you for the spelling correction). No changes were made to the settings of either router (okay, it was rebooted) or of other computers on LAN. Given that, I draw the conclusion that the problem is with openSUSE default settings.
When you want more analyzing from the people here, you better explain what was already hidden in my answer and is more explicit asked in those of others: where is the DNS server those Windows systems (and probably also the openSUSE system) have to use and how is it supposed to be configured with the new partner (the openSUSE system).
When you get the connection name do this:
nmcli con show myconnectionname|grep hostname
^does this send hostname for ipv4 and also have an ipv4 hostname set?
I did what you suggested. It seems to be not it. Sending the host name is enabled (set to yes) by default.
You’ve shown no evidence of anything that helps make any definitive conclusion. Do you have a domain name server on your LAN? Does the router provide such a service? (I once had one that did.)
As I said, I am really not that much in the LAN business. This is a usual home LAN managed by router (everything has been working without tinkering up to now, so there has been no need to worry). I am not sure I can answer your questions fully, but you’ll find the screen-shot of the network settings windows below (I manually copied IPs of DNS-servers from the router settings addresses; the same goes for additional static address field). The router is configured to assign fixed IP-addresses for all computers including the one with freshly installed openSUSE (it run another Linux distribution before that and networking worked just fine, so it has to be something with openSUSE configuration, I trust).
Actually, I found a workaround. Every thing plays out nicely if I add IP-address/DNS name of the openSUSE computer to the hosts files of all other computers on LAN. I am just not sure if it is a proper solution (it was never needed in the past).
I would be happy to provide you the information you requested, if only I could understand your question fully. I believe, the screen-shot I attached to another answer might shed some light. I never set up any DNS server myself, I have no idea how to do that, the router refers to some IPs in the fields called «DNS server 1» and «DNS server 2», I added these IPs to the properties of the wi-fi connection for the openSUSE computer; it did not make any difference, though.
If that manual method works for you - all good. Is the linux host acting as a samba server? Maybe the other linux distro you referred to was advertising itself via NetBIOS (nmbd) perhaps. That’s deprecated these days, but modern Windows hosts can use WS-Discovery or Avahi name resolution as well, so you have other choices.