Fix 0X00000899: Workstation Not Logged On Error

You're sitting at your desk, trying to open a shared folder on the office server. You type the path like \server\sharedfolder. Windows asks for credentials. You enter them. And then – boom – 0X00000899: The workstation is not logged on to the LAN. It's infuriating, especially when you know the server is running and other people can connect fine.

This error usually happens on Windows 10 or Windows 11 machines. The trigger is almost always a failed logon session – either you entered the wrong password and Windows cached it, or the network service that handles logons stopped working. I've seen it most often right after a password change on the domain or a workgroup reset.

What causes this error?

The core problem is simple: Windows thinks your computer isn't authenticated on the network. It remembers a previous logon attempt that failed, or the Workstation service – which manages network connections – is hung up. Think of it like a door that's locked from the inside. You have the key, but the lock mechanism is jammed.

There's a common fix that works 90% of the time: clearing the stored credentials and restarting the related services. Here's how to do it.

Fix: Clear cached credentials and restart services

Follow these steps in order. Don't skip any – they build on each other.

Step 1: Open Credential Manager

Press Windows Key + R to open Run.
Type control keymgr.dll and press Enter.
In Credential Manager, click Windows Credentials (the blue link).

Step 2: Remove any credentials for the server or network

Look under Generic Credentials for entries that mention the server name or IP address (like TERMSRV/server or just \server). Click the arrow next to each one, then click Remove. You'll get a warning – confirm it. Remove any that look related to your network share.

This clears out old logon data that might be blocking a fresh connection.

Step 3: Restart the Workstation service

Press Windows Key + R, type services.msc, and press Enter.
Scroll down to Workstation (not Workstation Auto-Start).
Right-click it and choose Stop. Wait 10 seconds.
Right-click again and choose Start.

This service handles all network logon requests. Restarting it forces Windows to re-evaluate your network status.

Step 4: Flush DNS cache

Sometimes a bad DNS entry can mess up authentication. Open Command Prompt as admin (right-click Start, choose Windows Terminal (Admin) or Command Prompt (Admin) on older versions). Type:

ipconfig /flushdns

Press Enter. You should see “Successfully flushed the DNS Resolver Cache.”

Step 5: Try connecting again

Now go back to File Explorer and type the network path again. Windows should ask for credentials fresh. Enter the correct username and password for the server. If it works, great – you're done.

What if it still fails?

If the error comes back, check these things:

Time sync: Run w32tm /resync in admin CMD. If your clock is off by more than 5 minutes from the server, authentication fails.
Firewall: Make sure File and Printer Sharing is allowed in Windows Defender Firewall. Go to Control Panel > Windows Defender Firewall > Allow an app or feature through Windows Defender Firewall. Tick both Private and Public for File and Printer Sharing.
NetBIOS over TCP/IP: In your network adapter settings (Control Panel > Network and Sharing Center > Change adapter settings > right-click your connection > Properties > Internet Protocol Version 4 (TCP/IPv4) > Properties > Advanced > WINS tab), make sure Enable NetBIOS over TCP/IP is selected.

One last thing – if you're on a domain, check with your admin. The error can also pop up if the computer account in Active Directory is expired or disabled. That's less common but happens.

I've fixed this error on dozens of machines with the steps above. It's usually a credential hang-up, not a hardware problem. Give it a shot and let me know if you're still stuck.