What’s causing the ‘Net View Error 6118’ and How to Fix it?
1. Disable 3rd party Firewall / AV (if applicable)
As it turns out, one of the most common causes that might end up spawning the ‘Net View Error 6118’ error is overprotective firewall protection that blocks the SMB (Server Message Block) from communicating with other network devices. Note: If you’re not using an external firewall/security suite that might cause this issue, move down directly to the next method below. Quite a lot of affected users have reported that in their case, the issue ended up being caused by an overprotective security suite that ended up interrupting the connection between the SMB and other devices connected to the same network due to a false positive. If this scenario is applicable, you should start your troubleshooting guide by investigating if the 3rd party virus protection tool that you’re using is not actually causing the ‘Net View Error 6118′ issue. If you’re using a 3rd party AV, the ideal way to start is to disable the real-time protection, restart your computer and see if the issue goes away for good. However, if you’re using an external firewall, disabling the Shields / Real-Time protection will not do you any good since the same security rules will remain firmly in place. If the latter scenario is applicable, the only way you will be able to confirm your suspicion is by temporarily uninstalling the 3rd party suite and seeing if the ‘Net View Error 6118′ error stops occurring. Here’s a quick guide on uninstalling your 3rd party firewall in order to eliminate the potential interference: In case the same issue is still occurring, reinstall the 3rd party you previously uninstalled and move down to the next potential fix below for a different repair strategy.
2. Enabling the Function Discovery Provider Host
Another potential cause that might make the other network-connected devices inaccessible is a disabled Function Discovery Provided Host service. Some users that we’re struggling to resolve the same issue have reported that they were finally able to fix the issue after they accessed the Services menu and enabled this service. After doing this and opening File Explorer again, affected users were prompted to enable Network Discovery, which made the network-connected devices accessible again. Note: While this method will not fix the ‘Net View Error 6118′ error, it will provide you with a safer protocol for accessing network-connected devices directly from File Explorer. Here’s a quick guide on enabling the Function Discovery Provider Host in order to force the other connected network devices to appear inside File Explorer: In case you want to go for a different fix that will actually treat the symptoms of the ‘Net View Error 6118’ error and make the network devices visible inside the terminal, move down to the next method below.
3. Enabling the Computer Browser service
As it turns out, the number one reason that is known to cause the ‘Net View Error 6118′ error is a disabled service called Computer Browser. But the problem is, this service was deprecated in the latest versions of Windows 10 for security reasons. However, if you do want to leverage this fix, you will need to start by enabling SMBv1 via Windows Feature – this technology was since deprecated. After you do this and restarting your computer, the Computer Browser service should become available inside the Services screen. Here’s a quick guide on enabling SMBv1 via Windows Feature and then starting the Computer Browser service to fix the ‘Net View Error 6118′ error:
How to Fix ‘System 53 Error has Occured’ Error on Windows?How to Fix PS4 Error NP-40831-6 ’error occured’[FIX] ‘An Error Occured while Trying To Copy a File’ Filmora Installation Error…Fix: Google Chrome Profile Error Occured
