7

I have been using my home network to share files between devices in my household with no problem, but recently I had to re-install my Windows 10, after that, no devices show under Network in File Explorer. Sure I can ping the devices and I can access them with their ip like \\192.168.1.50 but I can't get a list.


net view /all returns:

Home network System error 6118 has occurred.

The list of servers for this workgroup is not currently available.

What seems to be the problem?

8
  • You've not joined the workgroup? Aug 9 '18 at 12:01
  • @djsmiley2k sorry for the confusion, was going to answer this myself.
    – Shayan
    Aug 9 '18 at 12:04
  • 1
    I have a feeling your self answer is enabling the older insecure protocol, rather than enabling either homegroups, or setting a workgroup properly... Aug 9 '18 at 12:13
  • @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
    Aug 9 '18 at 12:17
  • 1
    You are likely using SMBv2 or even SMBv3. SMBv1 is deprecated (and generally horrible).
    – Bob
    Aug 9 '18 at 13:20
2

If you really need network discovery, you can enable the (safer) WS-Discovery protocol instead, as per the Microsoft Support article.

  1. Start the "Function Discovery Provider Host" and "Function Discovery Resource Publication" services, and then set them to Automatic (Delayed Start).
  2. When you open Explorer Network, enable network discovery when you are prompted.

This needs to be done on all Windows computers.

This might not help with net view (?), but should at least enable browsing in Windows Explorer (File Explorer).

2
  • 3
    I can confirm it does not work with net view /all, I am receiving the 6118 error again, but at least I can see network devices in File Explorer :D
    – Shayan
    Aug 9 '18 at 13:53
  • same here... "net view" (without a server name) does not work on one of my pcs... looking for a reason for days now, at no avail...
    – marcolopes
    May 23 at 2:48
1

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.

1
  • QUICK UPDATEError 6118 and Net View problem - SOLVED At LAST Jul 27 '19 at 19:30
0

I searched around and it seems like a service needs to be enabled called "Computer Browser"

I couldn't find this service in Task Manager -> Services.

Neither in Win+R -> services.msc.

I kept searching and this 6118 error sounds pretty common but the answer didn't help me since I knew firewall was not the issue. But it mentioned SMB so I searched around and found this:

Make sure SMB 1.0/CIFS File Sharing Support is installed as a windows feature. Source

Seems like later versions of Windows 10 have this feature disabled by default. So I enabled it and restarted the computer and now network devices show up and net view /all returns the computer names successfully.

WARNING: SMB 1.0 is insecure and you should enable it as a last resort (See Bob's answer), Ransomwares usually spread through this protocol as pointed out by @djsmiley2k and @Bob.

6
  • 1
    This is deprecated and disabled by default for a (security) reason. You can still access devices by hostname with most typical home router DNS/DHCP servers.
    – Bob
    Aug 9 '18 at 12:15
  • @Bob DHCP is enabled on my router, but I still wasn't able to list the devices.
    – Shayan
    Aug 9 '18 at 12:18
  • 2
    You won't be able to list them, much less with net view (which uses NetBIOS). Network discovery is long deprecated. I'm saying you'll be able to access them by hostname, assuming you know the hostname (so instead of \\192.168.1.123 you can access \\Shayan-PC).
    – Bob
    Aug 9 '18 at 12:24
  • @Bob Uhm, yes I know what hostname is but I was expecting for a "how to list network devices without that insecure protocol" comment so my brain kinda mixed them up together sorry :)
    – Shayan
    Aug 9 '18 at 12:28
  • 1
    If you work with 150 Windows clients, you should be using Active Directory, which would make this a non-issue. A properly-administered network should also probably have central network shares, though that's a bit beside the point. See also, aka.ms/StopUsingSMB1, and if you really need local discovery you can enable WS-Discovery (section: "Explorer Network Browsing").
    – Bob
    Aug 9 '18 at 12:46
0

net view is deprecated. Ignore this command altogether and access your resource directly via \\Computer-Name\Folder even if you can't see it listed under net view or under "Networks" in Windows (it should work).

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.