Error 6118 and Net View problem - SOLVED At LAST
My solution involved no changing of P.C. settings, however will only be relevant if you have one or more WiFi Range Extenders in your system.
I have several network wired P.C.'s. They all started to have this problem. Using a Command Prompt window, entering Net View / ALL produced the error, however entering Net View with an individual computer name or IP address worked.
Selecting NETWORK in Explorer resulted in most connected devices not showing under 'Computers', although they did show under 'Media Devices' and 'Storage'.
The contents could be accessed in other ways, but the problem really aggravated me.
I researched the matter for weeks, and tried dozens of offered solutions, all without result. Most revolved around changing P.C. settings, but I soon realised that since the problem was universal to all connected computers, my solution lay somewhere in one or other connected devices.
Making sure DHCP was only enabled in one Router, and rebooting them did not resolve the issue. I then realised I had other Networked items I had not considered.
I have 3 TP-LINK Range Extenders (RE305) in my system, which work very well. More research indicated they may have DHCP options, however try as I may I could not access them.
So I removed all 3 from the system. Went to the P.C., and all my devices had appeared again using Net View and Explorer.
I was concerned that I would not be able to use the Extenders, but decided to continue slowly. I plugged in the first, then the second as well, no Network problems. All devices showing on P.C.
I plugged in the last Range Extender, and Error 6118 was back. The solution was to just Setup the device again. I used all the same settings. Network devices showing and accessible on all my P.C.'s again.
So there we are. I would still turn of DHCP on all but one Router if there are several, but in this case the culprit was definitely a WiFi Range Extender.
QUICK UPDATE
Yesterday the 6118 problem was back, all P.C's on the Network. I discovered I could not log on to one of the Range Extenders. Unplugged it (powered down) and plugged it back again. Re-booted Computers and all Network Devices showing again. I could also log on to it. I did nothing else.
The networked devices may not all appear immediately, and can take up to 10 minutes for all of them to get 'registered'.
Nearly all the solutions tend to point to things that need to be done to an individual P.C.. Sometimes that might be the cure, HOWEVER if you find that more than one P.C. on your system develops the problem, do not be immediately tempted to change the Computer's settings.
This anomaly with my range extender is a pretty good indication that the 6118 error is being caused by some other unit on the LAN. Investigate those first.
You've not joined the workgroup? – djsmiley2k TMW – 2018-08-09T12:01:09.237
@djsmiley2k sorry for the confusion, was going to answer this myself. – Shayan – 2018-08-09T12:04:10.930
1I have a feeling your self answer is enabling the older insecure protocol, rather than enabling either homegroups, or setting a workgroup properly... – djsmiley2k TMW – 2018-08-09T12:13:37.377
@djsmiley2k I don't want to set a workgroup because I have apple devices in here and Windows and Apple can't connect this way. I'm not sure if there's a difference between homegroup and workgroup, in fact this is how I always connect devices with each other and I've never set one, I'll disable the protocol, and learn on how to create homegroups and I will report back. – Shayan – 2018-08-09T12:17:48.543
@djsmiley2k Sounds like homegroups and workgoups are also deprecated (for security?) https://support.microsoft.com/en-us/help/4091368/windows-10-homegroup-removed I'm out of luck.
– Shayan – 2018-08-09T12:29:52.823If you are not on a AD domain, you are on a "workgroup" by default. Not that that would help any, in this case. If you really need discovery in a non-AD environment, enable WS-Discovery. – Bob – 2018-08-09T12:48:41.403
@Bob Macbooks use SMB to share files with Windows, and SMB is disabled on my Windows and only enabled on Macbook Pro yet I am sharing files, I don't understand. I thought AD uses SMB but turns out it uses LDAP protocol, thanks for all the info you have given me. – Shayan – 2018-08-09T13:18:52.027
1You are likely using SMBv2 or even SMBv3. SMBv1 is deprecated (and generally horrible). – Bob – 2018-08-09T13:20:45.577