locked
System error 6118 has occurred. The list of servers for this workgroup is not currently available. RRS feed

  • Question

  •  when I enter net view

    It takes a couple minutes then it returns:

    System error 6118 has occurred.
    The list of servers for this workgroup is not currently available.

    When I am in file explorer if I enter: \\Remotecomputer

    If I click on NETWORK it shows up in the right pane as a Computer. The local host computer used to populate that pane too. Now it doesn't. Eve If I type \\Localcomputer it will show in the left pane under NETWORK but it doesn't show under the right pane in Computers

    it will shows the shares from that computer.

    It appears that by doing a nbtstat -a Remotecomputer it returns a : __MSBROWSE__ indicating to me that the remote computer thinks it is the master browser? How do I make the localcomputer host the master browser? 

    all other NET commands seem to work fine.

    I can also ping and ping -a between the host and remote computers

    Both Computers are in the same workgroup, both have Network Discovery and file and printer sharing enabled on both the private and public networks.

    I turned off the antivirus and turned off the windows defender firewall to see if SMB was being interfered with and it makes no difference as far as the Net View command is concerned.

    TIA

    EDIT:

    I did a complete reset of my network stack:

    ipconfig /release
    ipconfig /flushdns
    ipconfig /renew
    netsh winsock reset
    netsh interface ipv4 reset
    netsh interface ipv6 reset
    netsh winsock reset catalog
    netsh int ipv4 reset reset.log
    netsh int ipv6 reset reset.log
    netsh advfirewall reset

    Both Function Discovery Provider Host and Function Discovery Resource Publication have been stopped and or restarted, and are currently running

    • Edited by rocketjetz Saturday, May 4, 2019 10:58 PM
    Saturday, May 4, 2019 10:40 PM

Answers

  • by default smb v2 and v3 are the default on win10.  I have used powershell to verify this. 

     get-smbclientconfiguration


    ConnectionCountPerRssNetworkInterface : 4
    DirectoryCacheEntriesMax              : 16
    DirectoryCacheEntrySizeMax            : 65536
    DirectoryCacheLifetime                : 10
    DormantFileLimit                      : 1023
    EnableBandwidthThrottling             : True
    EnableByteRangeLockingOnReadOnlyFiles : True
    EnableInsecureGuestLogons             : True
    EnableLargeMtu                        : True
    EnableLoadBalanceScaleOut             : True
    EnableMultiChannel                    : True
    EnableSecuritySignature               : True
    ExtendedSessionTimeout                : 1000
    FileInfoCacheEntriesMax               : 64
    FileInfoCacheLifetime                 : 10
    FileNotFoundCacheEntriesMax           : 128
    FileNotFoundCacheLifetime             : 5
    KeepConn                              : 600
    MaxCmds                               : 50
    MaximumConnectionCountPerServer       : 32
    OplocksDisabled                       : False
    RequireSecuritySignature              : False
    SessionTimeout                        : 60
    UseOpportunisticLocking               : True
    WindowSizeThreshold                   : 8

    Get-SmbClientNetworkInterface

    Interface Index RSS Capable RDMA Capable Speed            IpAddresses
    --------------- ----------- ------------ -----            -----------
    23              False       False        0  bps           {fe80::3dee:6f00:8c9c:c2e8}
    22              True        False        1 Gbps           {2605:a000:160e:8355:5478:96d7:1d37:3390, 2605:a000:160e:8...
    13              False       False        1 Gbps           {fd00::1, fe80::d166:9ca6:a9f:95c8, 10.8.8.25}
    12              False       False        1.215752192 Gbps {fe80::e1ab:cb49:e5d5:d7a4, 169.254.215.164}
    6               False       False        0  bps           {fe80::88ea:e7a6:6d3:fcf7}
    9               False       False        0  bps           {fe80::2582:d2ab:c7f3:2ee9}
    18              False       False        0  bps           {fe80::c4f7:ca77:784b:4e5b}
    25              False       False        100 Mbps         {fe80::2074:8539:e56:2233, 192.168.137.1}
    16              False       False        100 Mbps         {fe80::5434:a9d1:5ea4:a19d, 192.168.24.1}
    20              False       False        3 Mbps           {fe80::6565:6ce0:3341:4c8f}

    Get-SmbShare

    Name   ScopeName Path                              Description
    ----   --------- ----                              -----------
    ADMIN$ *         C:\WINDOWS                        Remote Admin
    C      *         C:\
    C$     *         C:\                               Default share
    D$     *         D:\                               Default share
    F$     *         F:\                               Default share
    I$     *         I:\                               Default share
    IPC$   *                                           Remote IPC
    print$ *         C:\WINDOWS\system32\spool\drivers Printer Drivers
    R$     *         R:\                               Default share
    Users  *         C:\Users

    As you can see from the above output, smb is indeed alive and well and working on this machine. Without smbv1 being installed. 

    Instead of using net view I would suggest using Get-SmbShare  as it obviously works. You can point it to another pc on the network:

    Get-SmbShare -Name "computername"

    Get-SmbShare -Name "computername" | Format-List

    Get-SmbShare -Name "computername" | Format-List -Property *




    • Edited by rocketjetz Monday, May 27, 2019 3:39 PM
    • Marked as answer by rocketjetz Wednesday, May 29, 2019 8:02 PM
    Monday, May 27, 2019 3:30 PM

All replies

  • Hello rocketjetz,

    Thank you for posting in this forum.

    Please try to enable this service (Computer Browser) on this computer to see if it works.

    And please enable SMBv1 if you don't find this service under the service console.

    Best Regards,

    Leon


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, May 6, 2019 2:49 AM
  • Microsoft deprecated SMBv1 in 2014 because of security issues. I think I will pass on that suggestion. 
    Monday, May 6, 2019 2:19 PM
  • Hello rocketjetz,

    I know there may be a security risk with SMBv1.

    Is the operating system of these two computers Windows 10?

    If so, you can enable SMBv1. Enabling it does not mean using it. The SMB version used will be negotiated before the client establishes a connection with the server. In the end, they will choose the latest version of SMB that both parties have, so SMBv1 will not be used.

    Best Regards,

    Leon


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, May 7, 2019 1:24 AM
  • Hello rocketjetz,

    Just checking in to see if the information provided was helpful. 
    Please let us know if you would like further assistance.

    Best Regards,
    Leon


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, May 8, 2019 8:55 AM
  • No it wasn't helpful. I had already researched the issue before posting the question here. And I read the SMBv1 purported fix but I will not be doing that because of security issues. I will just do without Net View for the time being. TIA 
    Wednesday, May 8, 2019 11:27 PM
  • Hello rocketjetz,

    What's the result if you use "net start browser" in the CMD with elevated privileges?

    Best Regards,

    Leon


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, May 9, 2019 2:32 AM
  • C:\WINDOWS\system32>net start browser
    The requested service has already been started.

    More help is available by typing NET HELPMSG 2182.

    when I do a net view \\xxx.xxx.xxx.xxx  on a local or remote IP address it works.

    when I do a net view \\computername on a local or remote computer name it works

    net view or net view /ALL doesn't work

    funny huh?

    Tuesday, May 21, 2019 6:05 PM
  • There are too many such issues. To be honest, I think it's better to use other methods to implement what this command can do.

    net view returns the computers in the current domain or network. This list will only show computers that have file and printer sharing enabled.
    net view /all shows all shares available, including administrative shares like C$ and admin$.

    Enable network discovery in the Advanced Sharing Center and enable the Function Discovery Resourse Publication service. Then we can see other machines under the network folder in the File Explorer. Click on the machine to enter the credentials and we will see the shared resources on it.

    Best Regards,

    Leon



    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, May 22, 2019 9:18 AM
  • Hi All ....  We started having this issue about 2 weeks ago.  The funny thing is that sometime it works and at times it does not.  We need to able to browse the Windows Network because of an application.  This the error that we are getting:  The service has not been started.   Any feedback and/or suggestions are welcomed.
    • Edited by user_feo123 Wednesday, May 22, 2019 8:31 PM
    Wednesday, May 22, 2019 8:21 PM
  • network discovery and the FDRP are both enabled started on the machine in question. What's funny is, that on 3 other win10home pc's net view or net view /all  work fine. It's only on this win10pro that it doesn't work. All 4 pc's are at 1809.503
    Monday, May 27, 2019 3:22 PM
  • by default smb v2 and v3 are the default on win10.  I have used powershell to verify this. 

     get-smbclientconfiguration


    ConnectionCountPerRssNetworkInterface : 4
    DirectoryCacheEntriesMax              : 16
    DirectoryCacheEntrySizeMax            : 65536
    DirectoryCacheLifetime                : 10
    DormantFileLimit                      : 1023
    EnableBandwidthThrottling             : True
    EnableByteRangeLockingOnReadOnlyFiles : True
    EnableInsecureGuestLogons             : True
    EnableLargeMtu                        : True
    EnableLoadBalanceScaleOut             : True
    EnableMultiChannel                    : True
    EnableSecuritySignature               : True
    ExtendedSessionTimeout                : 1000
    FileInfoCacheEntriesMax               : 64
    FileInfoCacheLifetime                 : 10
    FileNotFoundCacheEntriesMax           : 128
    FileNotFoundCacheLifetime             : 5
    KeepConn                              : 600
    MaxCmds                               : 50
    MaximumConnectionCountPerServer       : 32
    OplocksDisabled                       : False
    RequireSecuritySignature              : False
    SessionTimeout                        : 60
    UseOpportunisticLocking               : True
    WindowSizeThreshold                   : 8

    Get-SmbClientNetworkInterface

    Interface Index RSS Capable RDMA Capable Speed            IpAddresses
    --------------- ----------- ------------ -----            -----------
    23              False       False        0  bps           {fe80::3dee:6f00:8c9c:c2e8}
    22              True        False        1 Gbps           {2605:a000:160e:8355:5478:96d7:1d37:3390, 2605:a000:160e:8...
    13              False       False        1 Gbps           {fd00::1, fe80::d166:9ca6:a9f:95c8, 10.8.8.25}
    12              False       False        1.215752192 Gbps {fe80::e1ab:cb49:e5d5:d7a4, 169.254.215.164}
    6               False       False        0  bps           {fe80::88ea:e7a6:6d3:fcf7}
    9               False       False        0  bps           {fe80::2582:d2ab:c7f3:2ee9}
    18              False       False        0  bps           {fe80::c4f7:ca77:784b:4e5b}
    25              False       False        100 Mbps         {fe80::2074:8539:e56:2233, 192.168.137.1}
    16              False       False        100 Mbps         {fe80::5434:a9d1:5ea4:a19d, 192.168.24.1}
    20              False       False        3 Mbps           {fe80::6565:6ce0:3341:4c8f}

    Get-SmbShare

    Name   ScopeName Path                              Description
    ----   --------- ----                              -----------
    ADMIN$ *         C:\WINDOWS                        Remote Admin
    C      *         C:\
    C$     *         C:\                               Default share
    D$     *         D:\                               Default share
    F$     *         F:\                               Default share
    I$     *         I:\                               Default share
    IPC$   *                                           Remote IPC
    print$ *         C:\WINDOWS\system32\spool\drivers Printer Drivers
    R$     *         R:\                               Default share
    Users  *         C:\Users

    As you can see from the above output, smb is indeed alive and well and working on this machine. Without smbv1 being installed. 

    Instead of using net view I would suggest using Get-SmbShare  as it obviously works. You can point it to another pc on the network:

    Get-SmbShare -Name "computername"

    Get-SmbShare -Name "computername" | Format-List

    Get-SmbShare -Name "computername" | Format-List -Property *




    • Edited by rocketjetz Monday, May 27, 2019 3:39 PM
    • Marked as answer by rocketjetz Wednesday, May 29, 2019 8:02 PM
    Monday, May 27, 2019 3:30 PM
  • I do not have a computer browser service installed not smbv1. 

    IN windows nt4,win2k and winxp we used to be able to set the master browser with the registry editor. But those entries are no longer used as far as i can tell on win10.  They might return if I installed smbv1 but that isn't going to happen. It's time for me to transition more from the command prompt cli to powershell cli, and since powershell will provide me with the information I need, I will just use it instead. Can't wait for the new Windows terminal to become available.  You can close this as answered.

    Monday, May 27, 2019 10:14 PM