Solution: System Error 6118 has Occurred in CMD

Updated November 2024: Stop getting error messages and slow down your system with our optimization tool. Get it now at this link

1. Download and install the repair tool here.
2. Let it scan your computer.
3. The tool will then repair your computer.

The error message “System error 6118 has occurred – The list of servers for this workgroup is not available” can occur when you try to use the net view /all command at the command line to view a complete list of network devices.

In most cases, affected users report that devices do not show up in File Explorer under Network although they can ping them directly from the CMD prompt. In this post, we will explain the reasons and provide the most appropriate solutions for the problem.

What causes System Error 6118 in CMD?

It can either be due to a third-party antivirus/firewall interfering, a blockage, a feature detection service disabling, or a computer’s browser service disabling.

However, some workarounds can help you continue to manage file-sharing or session sharing and printer sharing.

So, here’s how to troubleshoot “System error 6118 occurred” in Windows 10.

How to troubleshoot ‘System Error 6118 has occurred’ in CMD?

Turn off the Windows Defender firewall

1. Click on Start and select Settings.
2. Go to Update and Security.
3. Click on Windows Security.
4. Open Windows Firewall and Network Security.
5. Open the currently active network.
6. Scroll down to the Windows Firewall Defender section.
7. Flip the switch to disable the Windows Defender firewall.
8. When prompted to confirm the action, click Yes.
9. Do the same with the other currently active networks.

Disable third-party firewall

If you have third-party antivirus software with a firewall installed, you may also need to disable it.

1. Run your antivirus program.
2. Check to see if it has firewall protection built-in.
3. Disable the firewall protection.
4. You can also temporarily disable the antivirus program to completely disable anything that might be blocking the connection.
5. Close the antivirus settings window and check if you can access the server using the Net View command.

Restarting the Discovery Provider node

1. Press Windows + R to open Run.
2. Type services.MSC and click OK to open Services.
3. In the Services window, find the Function Discovery Provider service.
4. Right-click Function Discovery Provider and select Properties.
5. Click the Stop button.
6. The Stop Other Services window opens.
7. Stopping the Function Discovery Provider service automatically stops the Function Discovery Resource Publication service.
8. Click Yes to confirm and stop the service.
9. Click the Start button.
10. Click OK to save your changes.
11. Close the Services window and try using the Net View command to see if this fixes the error.

If the problem persists, make sure that the Computer Browser service is running on all machines and that NetBIOS over TCP/IP is enabled in your network card settings.

Also, make sure that network discovery is enabled. This can be done by checking the Advanced Sharing option in the Network and Sharing Center.

Expert Tip: This repair tool scans the repositories and replaces corrupt or missing files if none of these methods have worked. It works well in most cases where the problem is due to system corruption. This tool will also optimize your system to maximize performance. It can be downloaded by Clicking Here

Frequently Asked Questions

Carter Blakefield