Skip to content

Konstantinos Tsoukalas

Konstantinos is the founder and administrator of Since 1995 he works and provides IT support as a computer and network expert to individuals and large companies. He is specialized in solving problems related to Windows or other Microsoft products (Windows Server, Office, Microsoft 365, etc.).


  1. Alexa
    March 17, 2024 @ 7:40 pm

    Methode 7 war bei mir erfolgreich, nachdem ich ewig auf anderen Seiten nach Informationen gesucht hatte, die aber nie etwas gebracht hatten. Vielen Dank!


  2. cp
    February 23, 2024 @ 5:44 am

    4 worked for me


  3. OldUSAF Medic
    August 27, 2023 @ 3:31 am

    I have been working on this for 5 hours and it was the remote settings that fixed mine. I was able to access the other devices on the network but the one computer I was on did not display it under file explorer.
    thank you


  4. khisel
    August 10, 2023 @ 4:04 am

    I've literally been searching for more than three years. When I tried Method 4 it worked and I was flabbergasted. Of course after the reboot I was back where I started. Method 5 (changing the "triggerinfo" did the trick after a reboot. I'm calling The Pope right now to begin the sainthood process for this website.


    • DaveP
      August 27, 2023 @ 3:44 pm

      Thanks for all the valuable guidance. I've been fighting this issue periodically ever since a recent clean Win 10 install on a new SSD in my Desktop machine. I followed Methods 1 thru 6 (Method 7 isn't applicable to my systems), but none worked. As a last resort, I mapped network drives on both machines. That fixed the problem, at least for now. Keepin' 'em crossed that was a permanent fix.


  5. D Nair
    July 1, 2023 @ 9:06 pm

    Thanks so much for detailing all the possible solutions. I got lucky with Method 5 – Deleting the trigger for the Function Discovery Resource Publication service


  6. Ralph
    July 31, 2022 @ 12:47 am

    Thanks so much! Method 4


  7. Margaret Weir
    June 27, 2022 @ 9:13 pm

    After trying all of the above, several times, I'm giving up. Nothing works. I can see my laptop shared files on my desktop, but not vice versa. Frustrating.


  8. Odie
    May 27, 2022 @ 4:30 am

    Many, many thanks for this informative article! Deleting the trigger for the Function Discovery Resource Publication service solved my problem. I NEVER would have figured that out on my own!


  9. Rob
    December 24, 2021 @ 8:15 am

    Brilliant thank you so much for your detailed explanation – the second PC (Win10) disappears every now and then – this fixed it


  10. Greg O'Neill
    June 6, 2021 @ 2:15 pm

    have just discovered an easy fix for when my PC's disappear from the network, what I have done is when those PC's are showing, I pin each one to Quick Access and when they disappear, I just left click on them in Quick Access and they show up again


  11. Jason D
    March 22, 2021 @ 11:12 pm

    Thank You! Networks are not my strong suite and this was exactly what I needed.

    SMB 1.0/CIFS was the culprit for me as well.


    • pb
      May 15, 2021 @ 7:47 pm

      network reset has allowed me to see other PCs, so far.


  12. Michael Gorman
    January 30, 2021 @ 8:54 pm

    Additional Comment to the Michael Gorman Comment:

    All this relates to Windows 10 20H2

    My network is: 2 servers, 2 laptops, and 1 desktop. Servers are Windows Server 2012R2. The laptops are Windows 10 20H2 and the Desktop is Widows 10 20H2.

    Goal was to map all the drives across all the computers. Home Network, not "company network." Just me and my wife. Access is "king." Security among the computers is not.

    These comments ultimately resulted from about 5 sessions with Microsoft Tech Support over about 5+ hours over three days. Ultimately they are attempting to be very helpful and understanding. I can just imagine that most of these Techs are dead by age 30 from stress…. I really feel sorry for them, one and all.

    1. Do all the steps cited above.
    2. Reset the Network in your computer back to default settings… I don't remember where that was. That had to be done twice. And after each, restart
    3. Reset the Winsock
    4. There were a number of Services changes. Most if not all were identified above. I watched and noted to myself… ah, already done.
    5. On each of the Networked computers and on each of the drives to be mapped, Go the Sharing then Security then Edit then Add, and make an "Everyone." The UPPER case E is required.
    6. On the Permissions for Everyone, click the Allow All then click apply. It will wiz around for a while setting permissions. What joy….
    7. Then map the drives per normal put in the full string: //ComputerName/DriveName the press Finish.


    1. I've been in IT for 55 years (application systems and database/data management). This was an extraordinary stressful five hours. On that I will make no additional comment.
    2. I find real fault with Microsoft for NOT creating a Windows 10 20H2 installation media that took that much tuning and fiddling after it was installed.

    Anyway, it is done. Thankfully..

    I hope this is helpful and can is of benefit.


  13. Michael Gorman
    January 30, 2021 @ 6:22 pm

    I have Windows 10 20H2.

    None of the suggestions worked for me..


    • Michael Gorman
      January 30, 2021 @ 6:25 pm

      As others have said. four other computers can see the Dell 5810 and each other via mapped drives but the 5810 cannot see anybody on the network nor can it create network mapped drives.

      hope you can figure out a next set of steps.


  14. Martin
    December 25, 2020 @ 12:17 am

    Unfortunately no method worked for me. For my previous Windows 10 home PC, everything worked normally but for my new Windows 10 Pro, no method worked. I can still only see my machine in Network places and no other despite the fact that I can connect to others by typing in their address.


  15. Donald
    November 24, 2020 @ 7:00 pm

    SMB (last method no.5) worked on a 2004 version


  16. Robin
    October 21, 2020 @ 4:49 pm

    Everything was working fine until the windows 10 upgrade v2004 . The Lenovo (version 1903) computer can still see the desktop, but the desktop that got auto-updated to 2004 no longer accesses the other. And they don't have the update ready for Lenovo! I am dead in the water here.


  17. Ian Rankine
    October 21, 2020 @ 3:43 pm

    Didn't work until I checked the DEPENDENCIES in the services and made sure those services were running. Then TADA, worked great. Thanks


  18. Peter
    October 20, 2020 @ 9:38 am

    Turning off & on the Trigger (Method 4) sorted it for me.
    Truly grateful!!!


  19. JOHN
    September 14, 2020 @ 5:01 am

    I agree with Gary above. I tried all these methods except #4. I still can only see the computer I'm on in the network. I hate to say it, but this sort of thing is what drives people to Apple machines.


  20. Gary
    July 29, 2020 @ 3:07 pm

    None of the 5 steps above worked for me. FYI, method #4 errored out for me.
    It is 7/29/20 as I write this. The current version for Windows 10 Pro is OS build 19041.388 version 2004.
    Perhaps that added yet more security to not allow PC discovery. The only thing that shows up in each of my 2 Win 10 Pro machines under 'Network' is the PC that I'm on. This is such bull. There should not be issues like this trying to set up a home network.


  21. Russell D. Sellen
    February 23, 2020 @ 3:31 am

    SMB 1.0/CIFS


  22. Bob
    December 13, 2019 @ 8:09 pm

    Thank you. The Method 5 solved it for me on two computers.


  23. nikola
    October 12, 2019 @ 4:01 pm

    Only SMB )last step here= helped me finally see all computers on my workgroup network. What a pain. Thank you!!!


  24. Michael Dunkel
    September 26, 2019 @ 7:50 pm

    SMB 1.0/CIFS was the culprit for me.


Leave a Reply

Your email address will not be published. Required fields are marked *