Windows 10: Turn On or Off Network Discovery in Windows 10  

Page 3 of 3 FirstFirst 123
  1.    25 Aug 2018 #20

    Ok ... on the Win10 PC can you manually access just the \\XPComputerName by going to File Explorer > Address Bar and type \\XPComputerName
      My ComputersSystem Spec

  2. phrab's Avatar
    Posts : 152
    windows 10 professional 64-bit
       25 Aug 2018 #21

    Eagle51 said: View Post
    Ok ... on the Win10 PC can you manually access just the \\XPComputerName by going to File Explorer > Address Bar and type \\XPComputerName
    Tried that too. I get the message "Windows cannot access 'xpcomputername'." Check spelling, etc..

    In Windows XP, I can easily see Win10 by doing what you just said in Windows Explorer. But I can't in Win10. It's like something is hiding my XP machine, even though both machines can use my 2 shared printers. This is really strange. I really appreciate your time and expertise. I feel like I'm still

    By the way, I went to cmd.exe & pinged my xp computer & no packets were lost.
      My ComputerSystem Spec

  3.    25 Aug 2018 #22

    Tried that too. I get the message "Windows cannot access 'xpcomputername'." Check spelling, etc..
    Ok, can you access it by \\XPIpAddress ? (i.e. \\192.168.1.x)
    In Windows XP, I can easily see Win10 by doing what you just said in Windows Explorer. But I can't in Win10. It's like something is hiding my XP machine, even though both machines can use my 2 shared printers. This is really strange. I really appreciate your time and expertise. I feel like I'm still
    Yea, I hear ya .. this is an issue with Win10 that people are having. On your Win10 PC do have SMBv1 Client & Sever installed ?

    Edit: That should have been SMBv1 Client & Server.
      My ComputersSystem Spec

  4. phrab's Avatar
    Posts : 152
    windows 10 professional 64-bit
       25 Aug 2018 #23

    Eagle51 said: View Post
    Ok, can you access it by \\XPIpAddress ? (i.e. \\192.168.1.x)

    Yea, I hear ya .. this is an issue with Win10 that people are having. On your Win10 PC do have SMBv1 Client installed ?
    I think so. But I read at https://www.windowscentral.com/how-a...bv1-windows-10 that it's not secure. Also, Shawn mentioned it atEnable or Disable SMB1 File Sharing Protocol in Windows above & I'm wondering if I should disable or uninstall it.

    I forgot how I did it, but I ran a status check in an elevated Powershell window & it came back enabled. I can't find it listed in services, but I must have it.

    I went to XP, right clicked & chose Properties & went to "Computer Name" tab. I clicked Network ID & this time I chose home use, rather than business. I rebooted.

    When I now go back to Win10/Network, I can see my XPComputerName listed...which is a step in the right direction. However, if I try to double click (or right click & choose "Open"), I get the same error message that Windows cannot access \\xpcomputername.

    Should I disable smb1?
      My ComputerSystem Spec

  5.    25 Aug 2018 #24

    Should I disable smb1?
    I wouldn't, I',m pretty sure you're gonna need it for those XP PC's. SMBv1 has been patched for Win10 (don't know about XP) against WannCry and the risk is low on a home network IMO.
    When I now go back to Win10/Network, I can see my XPComputerName listed...which is a step in the right direction. However, if I try to double click (or right click & choose "Open"), I get the same error message that Windows cannot access \\xpcomputername.
    Yea, as I mentioned before this is known issue with Win10 and accessing network shares by hostname (i.e. \\PCNAME). By having SMBv1 installed it also installed the Computer Browser Service(it's tied to SMBv1). If you're using Static IP's for all your PC's and you can access shared PC's by \\ipaddress ... you can just map them by IP and bypass all this mess.

    People have had success fixing this Win10 issue, but with varying methods.
    1. Disabling IPv6 on ALL PC's
    2. Renaming the problem PC's
    3. Editing the hosts file on ALL PC's and mapping the IP to PCNAME ... Must have static IP's and if you have more than two PC's this can be a PITA ... personally if you have static IP's, just map the network shares by ip and avoid this unless necessary.
    4. Enabling SMBv1 (which you've already done)

    Note: Since HomeGroups have been removed from Win10. You might want to consider leaving any WinXP HomeGroups you've created and disable the two HomeGroup Services .. if you haven't done so already. I really don't know if/how this affects the Win10 accessing shares by \\PCNAME.
      My ComputersSystem Spec

  6. phrab's Avatar
    Posts : 152
    windows 10 professional 64-bit
       25 Aug 2018 #25

    Solved


    Eagle51 said: View Post
    I wouldn't, I',m pretty sure you're gonna need it for those XP PC's. SMBv1 has been patched for Win10 (don't know about XP) against WannCry and the risk is low on a home network IMO.

    Yea, as I mentioned before this is known issue with Win10 and accessing network shares by hostname (i.e. \\PCNAME). By having SMBv1 installed it also installed the Computer Browser Service(it's tied to SMBv1). If you're using Static IP's for all your PC's and you can access shared PC's by \\ipaddress ... you can just map them by IP and bypass all this mess.

    People have had success fixing this Win10 issue, but with varying methods.
    1. Disabling IPv6 on ALL PC's
    2. Renaming the problem PC's
    3. Editing the hosts file on ALL PC's and mapping the IP to PCNAME ... Must have static IP's and if you have more than two PC's this can be a PITA ... personally if you have static IP's, just map the network shares by ip and avoid this unless necessary.
    4. Enabling SMBv1 (which you've already done)

    Note: Since HomeGroups have been removed from Win10. You might want to consider leaving any WinXP HomeGroups you've created and disable the two HomeGroup Services .. if you haven't done so already. I really don't know if/how this affects the Win10 accessing shares by \\PCNAME.
    THANK YOU AGAIN!

    Not quite sure what happened, but since I posted last, I disabled the smbv1 & rebooted. As you noted, I not only didn't see my XP machine in Win10, I could no longer see my Win10 machine in XP. So I re-enabled it & rebooted. For whatever reason, I can now see my Documents & my entire username folder from XP on my Win10 machine...& I can still see my shared folders from Win10 on my XP machine ! ! !

    Thank you for telling me about the patch on Win10 & the low risk. You've eased my worries.

    I really really appreciate your time & expertise!! I will mark this problem solved (if I can figure out where to do that
    Last edited by phrab; 25 Aug 2018 at 22:50.
      My ComputerSystem Spec

  7.    25 Aug 2018 #26

    Good Job ... glad you got it sorted out and your welcome :)
      My ComputersSystem Spec


 
Page 3 of 3 FirstFirst 123

Tutorial Categories

Turn On or Off Network Discovery in Windows 10 Tutorial Index Network & Sharing Instalation and Upgrade Browsers and Email General Tips Gaming Customization Apps and Features Virtualization BSOD System Security User Accounts Hardware and Drivers Updates and Activation Backup and Restore Performance and Maintenance Xbox Windows Phone


Related Threads
I have a problem that has me stumped. I have a Ubuntu Media Server (OS Version 14.04.1) running Samba 4.1.6. I have a Win 10 laptop (upgraded in August from 8.1) and Win 10 desktop (upgraded Jan 11th from Windows 7). The laptop doesn't (or very...
Network Discovery not working ? in Network and Sharing
Hi Forum :) I am facing a problem that my PC running Windows 10 cant see other PC's/Devices on my network. Idk. if it have something to do with i cant make/join a homegroup. I was told to remove a file in...
Network Discovery re-visited in Windows Insider
There is some more info on the discovery problem at the end of this thread:- Cannot connect to CIFS / SMB / Samba Network Shares Shared Folders in Windows 10 after update 1511/10586 The last post has this - From MS today: 'Bug<u1:p></u1:p>:...
I updated my gaming computer to the latest build of windows 10.. don't quite remember what the number of it was, it was about a week ago I did this. I was hoping MS would sort out the issue in a hotfix or a patch or something. It's been over a week...
I've recently upgraded to windows 10. I use Bitdefender 2015, and have installed the latest compatible version for windows 10, after uninstalling previous using their uninstall tool, and also doing a repair. In the Security and Maintenance panel...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 10:50.
Find Us