I've been using a TrueNAS storage server without problems, but after dealing with a convincing malware infection I disabled all of my network adapters while checking for suspicious connections. I removed the malware and restored internet access, although I may also have changed some browser DNS settings. Since then, I can't reconnect to my network share. I've reconfigured the share, disconnected and remapped it, removed saved credentials, and tried logging in again, but Windows either rejects the credentials, repeatedly prompts for them, or reports that network logon failed. From Command Prompt I receive error 59, while accessing the mapped location reports that a device attached to the system is not functioning. I've also tried the Windows network reset without success. The problem appears limited to this computer, so I'm looking for suggestions on what settings or services I should check next.
3 Answers
First confirm whether the share works from another device on the same network. If other devices can access it, the NAS and its credentials are probably fine and the problem is local to this computer. Check that the computer is on the correct network profile, can resolve or ping the NAS by hostname and IP address, and try connecting directly with its IP instead of its name. That can help separate a DNS or name-resolution issue from an SMB authentication problem.
Because the machine was infected, avoid treating this as only a credential problem. Run a thorough offline or reputable antivirus scan, install current Windows updates, and make sure the NAS is not exposed directly to the internet. Once the system is known to be clean, remove old entries from Credential Manager and disconnect existing mappings before creating a new one. If the issue began immediately after the infection and survives the network checks, restoring Windows from a known-good backup or performing a clean reinstall may be safer than continuing to trust the installation.
Error 59 can indicate a general network or name-resolution problem. Try opening the share using an address such as \NAS-IPshare rather than \server-nameshare. Also verify that the network adapter has normal DNS settings, that the required adapter and file-sharing services are enabled, and that the Windows Firewall hasn’t started blocking file and printer sharing. Since a network reset did not fix it, manually checking the adapter configuration may be necessary.
I checked with another device and the share works there, so it does seem to be isolated to this computer.