first i will wish a save healty new year and that everbody can use any other Couches if the owner like that.
somtetimes is the world crasy
I am using a VM with 7.8 on XCP-NG 8.1 with all updates. Windows 10 is running from a SSD (SATA) on HP8300 and the Server with HDD. It is running with rouming profiles.
There are 2 Myth… First
When a Win10pro64 Client connected the AD sometimes the Net-Shares are not visibel. For the Windows terman i can ust th share with the letter (m:…) but the file Explorer say not connectet (not visibel). But its only sometimes. With a script on the desk it is fixt (the scripts reconnect them)
Secound is the Profile upload, i think …
If the User shut down the cleint PC direct, with button in left side, sometimes the Profile look damaged if the client PC will boot again. Somtime we had to restore it from the backup, but mostly some more restarts and ist running . All Clients shuting down completly
It could be because your interface is configured with the Public profile which don’t allow by default to share and use sharing devices/folders on the network
It could be because your Nethserver is not the DHCP/DNS provider and your Windows receive an IP from another DHCP service which don’t have the proper netbios options configured and the DNS don’t contain the information for your Nethserver. But usually if it is your case, you will still be able to reach it will still reachable via the Nethserver IP
It could be because you deactivate a service in your Windows, you have a virus/malware, …
Server side (Nethserver)
It happened to me in the past and mainly it was because nethserver-cups (yum install -y nethserver-cups) wasn’t installed. This package is responsible of Avahi which is a system which facilitates service discovery on a local network.
It could be suricata or threat shield blocking the traffic.