One of the computers in my office recently lost the ability to connect to a network share running on one of our servers. "Nothing changed" (don't we all just love that phrase) as far as I can tell; the secretary using it powered it off before going on vacation and powered it on upon returning. Here is the setup:
- Server: Windows Server 2000
- Client: Windows 8.1 (Personal/Home edition)
- Client and Server are both in the same Workgroup, on the same network, and subnet.
- Client is trying to access a shared folder on the Server but cannot.
- Server can access shared folders on the Client.
- Client can ping the Server and RDP successfully.
- Client's credentials are valid and exist on both it and the Server.
- Client's account has permissions to the shared folder on the Server.
- There are other computers on the network that are set up the same way and can access the shared folder on the Server without issue.
Basically, when the Client attempts to access the shared folder on the Server, I am prompted for credentials. No credential combination works, even ones which I know work (by trying them in RDP). The best error message I receive is "The specified Network Credential is invalid."
Things I've tried:
- Clear the Windows Credential cache.
- Leave and re-enter the Workgroup.
- Use different shared folders.
- Authenticate with different user accounts.
- Reboot both machines.
Questions I've read:
- Windows7 - “The specified network password is not correct.” when the password is in fact correct
- https://superuser.com/questions/384030/cannot-connect-to-a-shared-network-drive
- https://superuser.com/questions/929436/windows-7-cant-access-unc-shares-but-can-ping-and-rdp
- Windows 2008 Server cannot access any network share
- https://superuser.com/questions/242174/windows-cannot-access-servername-from-windows-server-2008-r2
Things I would love to do, but aren't options right now:
- Setup a domain.
- Upgrade from Server 2000.
- Upgrade to Business/Enterprise Windows for the Client.
Any thoughts? I've dealt with weird issues like this before which always turn out to be some cryptic setting in Windows that unexpectedly flipped one way or the other. My searches thus far haven't turned anything up that seems to fit my situation.