Yeah, that error's a pain—especially when you're in the middle of something and Windows just shuts you down with a cryptic hex code. Don't worry, I've seen this exact thing bite a client's accounting team last month. Here's the fix.
The Quick Fix
The error 0X0000083A maps to NERR_RemoteOnly, which literally means "This operation is not supported on workstations." You're trying to run a command that's only allowed on a server. The fix is simple: run it on the server, or use a command that works from your workstation.
First, check what you're running. Common culprits are net send, net file, or certain sc commands that require server-side privileges. If you're using net use to map a drive and hit this, stop—that's not the issue. This error typically pops up when you try to manage shared resources or sessions from a non-server machine.
Here's what to do:
- Identify the command that triggered the error. Look at your command prompt or script—what did you type right before it failed?
- Run that command on the server. If you have remote desktop access to the server, log in and execute it there. For example,
net sessionworks on Windows Server but not on Windows 10 Pro. - If you can't get to the server, use PowerShell with a remote session, like this:
Invoke-Command -ComputerName SERVER01 -ScriptBlock { net session }That runs the command on SERVER01 and returns the output to you. Same result, no error.
Why This Happens
Windows has different feature sets for client and server editions. Commands that manage network-wide resources—like open files, shared folders, or user sessions—are designed to run on the server where those resources actually live. A workstation doesn't have the service layer to handle them. The OS gives you NERR_RemoteOnly to say, "Hey, this isn't supposed to run here." It's not a bug; it's a guardrail.
I had a client whose backup script failed every night with this error. Turns out they had a batch file that used net file to close open files—something that only works on the file server itself. We moved that script to the server's Task Scheduler, and it's been running clean since.
Less Common Variations
Sometimes you'll see this error pop up in weird places:
1. PowerShell Remoting
If you use Enter-PSSession to connect to a server and then try a server-only cmdlet, you might get 0X0000083A. That's because the session might not have admin rights. Fix: run Enter-PSSession -ComputerName SERVER -Credential (Get-Credential) and use an admin account.
2. Scheduled Tasks
Like my backup story, a scheduled task running as a regular user can hit this when it tries a server command. Change the task to run as the SYSTEM account or a domain admin, and you're good.
3. Third-Party Tools
Some network management tools try to impersonate server operations from a workstation. If you see this error in a tool like a printer management app, check its settings for a "server mode" or point it to the server's IP directly.
How to Prevent It Next Time
The best way to avoid this error is to know which commands are server-only before you run them. Here's a quick list of common ones:
| Command | Works on |
|---|---|
net session | Server only |
net file | Server only |
net send | Server only (deprecated) |
sc config for services | Both, but some need admin |
When you write scripts, always test them on the target machine type. If you're automating something, use Invoke-Command to run remote tasks against the server. That way you never get blocked by this error again.
And if you're ever unsure, just run net helpmsg 2122—that gives you the English text for this error code, which is "This operation is not supported on workstations." Save yourself the head-scratching.