none
Net view only working on name RRS feed

  • Question

  • Hello,

    My Windows 10 fall creator is having a strange network issue, no other computer can access it, and itself can only access the shares through its name :

    IPConfig :

        IPv6 Address. . . . . . . . . . . . . .: 2001:470:1d:5dd::614
        IPv6 Address. . . . . . . . . . . . . .: 2001:470:1d:5dd:acd9:1a50:72e6:300c
        Temporary IPv6 Address . . . . . . . .: 2001:470:1d:5dd:c49e:adcc:e7ce:c434
        Link-local IPv6 Address. . . . .: fe80::acd9:1a50:72e6:300c%6
        IPv4 Address. . . . . . . . . . . . . .: 10.0.0.43

    Net view \\pc10 :

       Shared resources at \\pc10

       Share name  Type   Used as  Comment

       -------------------------------------------------------------------------------
       Users       Disk
       The command completed successfully.


    Net view \\10.0.0.43 :

       System error 53 has occurred.

       The network path was not found.

    And net view on any of the IPv6 returns also the error, as of 127.0.0.1 and localhost.

    nslookup pc10 :

       Server :   Srv-2016.domain.test.com
       Address:  2001:470:1d:5dd::45b

       Name :    pc10.domain.test.com
       Address:  2001:470:1d:5dd:acd9:1a50:72e6:300c
              2001:470:1d:5dd::614
              10.0.0.43

    How can this be explained, and how to resolve?  It makes no sense that it can view the shares on the name but not on the ip of the computer.


    Thanks, Dominic


    • Edited by GTA_doum Tuesday, January 23, 2018 4:54 AM
    Tuesday, January 23, 2018 4:51 AM

Answers

  • This post fixed my issue : https://answers.microsoft.com/en-us/windows/forum/windows_10-networking/netbios-over-tcpip-broken-since-upgrade-to/fd141dd9-8500-419d-b8e7-ac7255f44ec0?rtAction=1516944870981.

    It is a bug in Fall Creator update.  the issue is with NetBios being deactivated.  The answer is an easy fix if you are at ease with RegEdit.


    Thanks, Dominic

    • Marked as answer by GTA_doum Friday, January 26, 2018 5:41 AM
    Friday, January 26, 2018 5:40 AM

All replies

  • Hi,

    I want to check if my understanding about the issue is correct at first. You create a share folder on this Windows 10 1709 device. But other computers can't access the share folder with neither IP address or computer name with error code 53. The device itself can access the share folder through computer name. right?

    What's the windows version of other computers?

    Please try to ping the IP address to check the result.

    Try to run the build-in troubleshooting tool through Control Panel\All Control Panel Items\Troubleshooting\View all\Internet connection.

    Try to download and install the latest Network card driver to check again.

    Please run the following command line as administrator to purge remained caches and reset congifuration. Then reboot computer.

    ipconfig /flushdns 
    nbtstat -RR
    netsh int ip reset
    netsh winsock reset 

    If I misunderstood your issue, please tell me directly.

    Bests,


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

    • Proposed as answer by Joy-QiaoModerator Thursday, January 25, 2018 4:38 AM
    • Unproposed as answer by GTA_doum Thursday, January 25, 2018 4:49 AM
    Thursday, January 25, 2018 4:38 AM
    Moderator
  • Hello,

    You understood right.  Resetting and rebooting the computer do not change anything.

    The other computers are Windows 10, 7 and 2016, so any computers on the network.

    Marking this answer already as an answer is prematurate, don't you think?  We're here to troubleshoot and understand Windows errors, not to give points away at the speed of light!  I take this forum as being professional and filled with people that like computers and helping others.  I am sorry, but I will unmark this answer until a resolution is proved to be working.

    Pinging anywhere works fine, there is no firewall activated in any profile, on any computer on the network.

    The network card is using default Microsoft certified drivers.  The nic is a Broadcom NetXtreme 5761.  Since all other services are working fine, I would more start the troubleshooting on the sharing engine of Windows instead of the network card itself.

    Under Network in Windows Explorer, it only shows two, sometimes three, computers, whereas other computers show about 12 computers.  I can reach any computers by their name and IP.

    Sharing on my computer was working fine before the update, I noticed because my computer is the QuickBooks file server, which is under Public\Documents.

    Under Network shares parameters, the one for not using any password on shares is not there anymore, I guessed Microsoft removed it in some Windows 10 patch.  All computers are part of the domain so they should be able to access my computer shares anyway.


    Best regards, Dominic


    • Edited by GTA_doum Thursday, January 25, 2018 5:03 AM
    Thursday, January 25, 2018 4:49 AM
  •   The problem is probably SMB 1.0 . By default this is disabled in Windows 10 version 1709 (and I suspect all future releases) because of the security risks. Have you enabled SMB 1.0 in the version 1709 Windows 10 machines?  This would get your Windows 10 machine back in the browse list for now, but only by using an unsupported and unsafe protocol. (The wanna cry ransomware outbreak exploited a weakness in SMB 1.0).

      I am surprised that you are still using net view in a domain. Microsoft has been trying to discourage that (and the use of the computer browser service) since the release of Windows Server 2000, when Active Directory switched to using DNS instead on Netbios names. 

     Net view is a legacy command and depends on the computer browser service, which in turn depends on SMB 1.0 . Microsoft no longer supports it and advises users not to use it.

      The statement by Microsoft on SMB 1.0 can be found here.

    https://support.microsoft.com/en-sg/help/2696547/how-to-detect-enable-and-disable-smbv1-smbv2-and-smbv3-in-windows-and

     Unless you still have Windows XP machines or Devices that need SMB 1.0 (such as Samba shares or NAS devices) you should be able to use the newer network discovery method (introduced in Vista) which can handle IPv6 addresses.

     Apart from a few devices which I keep for testing, all of my machines have SMB 1.0 and Netbios over TCP/IP disabled. They all show up in the Network display (with IPv6 addresses). Net view simply shows "there are no entries in this list".

      The test machines with SMB 1.0 and Netbios enabled show in Net View but no other machines do. 


    Bill

    Thursday, January 25, 2018 6:45 AM
  • Here are some screenshots of Network and net view.

      Two machines (Windows10onBob and Lottie) are in both groups because they are machines which still have SMB 1.0 and Netbios over TCP/IP enabled.


    Bill

    Thursday, January 25, 2018 6:56 AM
  • I was not aware about SMB 1.0.  My computer has a new installation of Windows 10, that is upgrading to 10 patches since then.  I did not modify SMB settings, they are at their defaults.

    I was only using Net view to troubleshoot the connection issue from other computers.

    IPv6 is enabled on my network and working.

    Net view from my computer returns error 6118.

    The Netbios is set at its default, and in IPConfig it shows that it is deactivated.  I tried to enabled it, but IPConfig still shows as deactivated.

    I checked on another fresh Windows 10 fall creator computer (which is on another network I manage), and Netbios over tcp/ip is enabled!  So I guess the problem starts there, no Netbios!  Net view on that computer returns a list like yours.

    I compared the feature of SMB 1.0 on both computer, the only difference is that on mine, the Server is enabled.  So it seems that by default, SMB 1.0 is activated on Windows 10, even with Fall creator.


    Thanks, Dominic





    • Edited by GTA_doum Thursday, January 25, 2018 10:01 PM
    Thursday, January 25, 2018 9:24 PM
  •   First of all, an apology. If you found the article in the link I posted a bit confusing, I am not surprised. Here is the one I meant to send.

    https://support.microsoft.com/en-nz/help/4034314/smbv1-is-not-installed-windows-10-and-windows-server-version-1709

     If you do have version 1709, look closely at the SMB 1.0 settings. They have changed. There are now three options. Click the + sign to expand the view. If you elect to continue using SMB 1.0, leave the top one blank and select both client and server.

      How did you try to enable NetBIOS over TCP/IP? From Change adapter options right-click the NIC and select Properties. Select IPv4 and then its Properties. Click Advanced and then the WINS tab. Now select Enable NetBIOS over TCP/IP. 


    Bill

    Thursday, January 25, 2018 11:09 PM
  • This post fixed my issue : https://answers.microsoft.com/en-us/windows/forum/windows_10-networking/netbios-over-tcpip-broken-since-upgrade-to/fd141dd9-8500-419d-b8e7-ac7255f44ec0?rtAction=1516944870981.

    It is a bug in Fall Creator update.  the issue is with NetBios being deactivated.  The answer is an easy fix if you are at ease with RegEdit.


    Thanks, Dominic

    • Marked as answer by GTA_doum Friday, January 26, 2018 5:41 AM
    Friday, January 26, 2018 5:40 AM
  •   Glad you sorted it out. I must admit I have never seen the problem noted it the answers thread even though my system meets the conditions (Windows 10 version 1709 and Hyper-V installed).

     

    Bill

    Saturday, January 27, 2018 1:15 AM
  • It is not implied that every computer upgraded to 1709 will have the issue!

    I had a friend that had a similar issue, but in his case I found that the SMB 1.0 client was not activated in Windows features, but it was working before the update.

    So my conclusion is that some configuration triggers a bug in the 1709 patch installation, which removes some SMB 1.0 configuration.


    Thanks, Dominic

    Saturday, January 27, 2018 7:09 AM