A Referral Was Returned From The Server Powershell 💯

So next time you see that message, imagine the server shrugging: “Not my department, but here’s a note.” And then PowerShell, ever literal, prints the note instead of acting on it.

You run a simple PowerShell command — maybe Get-ChildItem \\fileserver\share — expecting a list of folders. Instead, PowerShell hisses back: “A referral was returned from the server.” It’s cryptic. Not quite an error, not quite success. A referral? Did the server just hand you a business card? a referral was returned from the server powershell

Here’s a short, interesting piece based on that scenario — part tech mystery, part sysadmin humor. So next time you see that message, imagine

PowerShell, unlike the old File Explorer, doesn’t automatically follow that referral. It just reports the server’s note verbatim — like a postal worker handing back a letter saying, “Try the other post office.” Not quite an error, not quite success

The fix? Use the target path directly, or force the referral with net use or New-PSDrive -Persist . Some admins jokingly call it “PowerShell playing hard to get.”

In PowerShell’s world, this happens with DFS (Distributed File System). You asked for \\domain\namespace\share , but the server says: “Oh, that’s not really here. Talk to \\fileserver02\share instead.”