As some may know the latest windows version removes SMB1 networking due to a exploit. https://support.microsoft.com/en-au/help/4034314/smbv1-is-not-installed-by-default-in-windows This effectively breaks all network exploring and access of linux pc's in my own testing. Windows network systems also get broken but that has a workaround to use WS-Discovery one can manually enable, (Microsoft has stated network exploring is now being depreciated in the article above (I think that will be backflipped with backlash)) but for linux that WS-Discovery protocol isn't fully implemented yet, NAS boxes like Synology have the protocol one can enable to get them back able to be explored and accessed. For linux however the systems won't show up on windows without the SMB1 client enabled and you still cant even access them via direct \\servername mapping no matter the setting. When you check the SMB version in admin command linux systems show as as SMB 1.5 even if you have SMB 3 installed like Centos etc. I run a Centos 6.9 server and a test of Centos 7 (yet to test SMB but I will presume the same) I have tested this on multiple PC's here at home and my server I cannot access unless I re-enable SMB1 in windows. My kinda current workaround is to log into my NAS gui and transfer from my server to the PC with both mapped in the NAS my HTPC and Server for example, or like my main system I have SMB1 enabled still same as my 2 in 1 as I frequently access my server. Does anyone know how this can be properly fixed without having SMB1 enabled or is the system just royally screwed up at the moment thanks to microsoft completely breaking SMB and network discovery to windows because of the security change.