Synology NAS missing from Windows Network or error 0x80070035? Work the split - IP test, SMB service, WS-Discovery, credentials - and never fall back to SMB1 or guest logons.
The shared folder exists, permissions are right, and Windows still says the NAS is not there. Stay calm: "not showing" is three different faults - Windows cannot find the NAS (discovery), cannot resolve its name, or cannot talk SMB to it. Each has a different fix, and trying them in the order below takes ten minutes.
Illustration - the classic 0x80070035 error. Names, discovery and SMB are three separate problems wearing one coat.
\\192.168.1.25 (your NAS IP)The Network folder in Explorer fills via discovery protocols, and Windows no longer uses the old NetBIOS browsing for this. On the NAS side, Synology provides WS-Discovery: DSM 7 → Control Panel → File Services → Advanced tab → enable Windows network discovery to allow file access via SMB. On the Windows side, make sure your network profile is Private and Network discovery is on in Advanced sharing settings. Honestly, though: appearing in Network is a convenience. The reliable habit is the IP or name path from step 1, then Map network drive so the folder gets a permanent letter.
The NAS opens but your folder is not listed? That is not a network fault at all. Either the folder is hidden - check Hide this shared folder in My Network Places and Hide folders and files from users without permissions under Shared Folder → Edit - or the account you logged in with simply has No access, and DSM is politely pretending the folder does not exist. Log in as admin in DSM and check that user's effective access before touching any network setting.
Mac users join the same party through the same protocol. In Finder choose Go → Connect to Server and enter smb://192.168.1.25/accounts (the NAS IP and folder name), then log in with the same DSM account - permissions follow the person, not the computer. Two honest Mac notes: use SMB, not the old AFP service, which Apple has been retiring for years; and expect small housekeeping files like .DS_Store to appear inside shared folders. They are harmless, and scolding Mac users about them is a tradition, not a solution.
The full shared folder setup - creating folders, users and permissions - shown live on a Synology NAS.
▶️ Watch Full VideoName lookup on a home or office network depends on discovery services and sometimes stale DNS or hosts entries. It is a naming problem, not a sharing problem. Mapping a drive to the IP address, or enabling WS-Discovery in DSM so Windows can find the name reliably, both work around it.
Usually Windows is silently offering an old saved credential or your Microsoft account first. Open Credential Manager, delete any entry for the NAS name or IP, then connect again and tick Remember my credentials only after the correct NAS password works.
No. DSM on any supported version speaks SMB2 and SMB3, which is all modern Windows needs. SMB1 has serious known security holes and is disabled by default; needing it means something else - usually a very old device - is the real problem to solve.