Windows 11 Error 58: “The Specified Server Cannot Perform the Requested Operation”
Why This Error Happens
Error 58 typically occurs when attempting to access shared resources (files, printers, or network drives) over SMB/CIFS protocols, and stems from a mismatch in SMB protocol versions, disabled network services, or corrupted network configurations. This commonly happens when connecting to older NAS devices, legacy servers, or third-party SMB implementations that don’t support the SMB version Windows 11 defaults to. Additionally, insufficient permissions on the target server or a disabled “Server” service on the host machine can trigger this same error code.
Step-by-Step Resolution Guide
- Enable SMB 1.0/CIFS Support (if connecting to legacy devices)
- Open Control Panel → Programs → Turn Windows features on or off
- Scroll down and check SMB 1.0/CIFS File Sharing Support
- Click OK and restart your PC
- Verify the Server Service is Running
- Press
Win + R, typeservices.msc, and press Enter - Locate Server in the list, ensure Status shows “Running”
- Right-click → Properties → set Startup type to Automatic
- Click Start if not already running
- Reset Network Configuration via Command Prompt
- Open Windows Terminal or Command Prompt as Administrator
- Run the following commands sequentially:
netsh winsock reset
netsh int ip reset
ipconfig /release
ipconfig /renew
ipconfig /flushdns
- Restart your computer after completion
- Check and Repair File and Printer Sharing Settings
- Go to Settings → Network & Internet → Advanced network settings
- Select Advanced sharing settings
- Ensure File and printer sharing is turned On for your active network profile
- Verify Permissions on the Target Server
- On the server/host machine, right-click the shared folder → Properties → Sharing tab → Advanced Sharing → Permissions
- Ensure your user account or “Everyone” group has at least Read access
- Also check the Security tab for matching NTFS permissions
Alternative or Verification Steps
- To verify the fix: Try accessing the shared resource again via
\\servername\sharenamein File Explorer’s address bar. If successful, the connection should establish without the Error 58 prompt. - Alternative solution: If the issue persists, try mapping the network drive using the server’s IP address instead of its hostname (
\\192.168.x.x\sharename), as this can bypass DNS or NetBIOS resolution issues that sometimes trigger this error.