Windows 10: Computers can't see each other after upgrade to 1803 Solved

Page 2 of 7 FirstFirst 1234 ... LastLast
  1.    1 Week Ago #11

    Is everything working good now? If so please mark the thread SOLVED at the bottom.

    Glad we could help out here.
      My ComputerSystem Spec

  2.    1 Week Ago #12

    Not 100%. I can see other computers and networked items but can't access all of them. It pretty much comes and goes. So, I can't say it's completely solved but I am spending some time on it each and every day.
      My ComputerSystem Spec

  3.    1 Week Ago #13

    I would double check all the Security permissions on the shares. I created folder this morning to share and even though I shared it, I had to go back and edit the Security tab on the folder properties to allow Everyone.

    I think a full read through the Tutorial post above and then double checking all security and sharing permissions should fix it.

    I did have to rename my PC so I could network after I clean installed 1803 but I have since renamed it back to what it was prior and it works. That still baffles me.
      My ComputerSystem Spec

  4.    1 Week Ago #14

    I did rename computers which I hadn't tried before but that made no change that I can see. I'll spend more time on it tonite and see what else I can tweak.
      My ComputerSystem Spec

  5.    1 Week Ago #15

    Beerlord said: View Post
    Not 100%. I can see other computers and networked items but can't access all of them. It pretty much comes and goes. So, I can't say it's completely solved but I am spending some time on it each and every day.
    I found that flushing the DNS cache cleared up the intermittent now you see them now you don't problem.

    I've mapped all my shares anyway so it wasn't a major problem, they worked ok, just odd that a mapped share worked when the PC wasn't showing under Network.
      My ComputersSystem Spec

  6.    1 Week Ago #16

    clam1952 said: View Post
    I found that flushing the DNS cache cleared up the intermittent now you see them now you don't problem.

    I've mapped all my shares anyway so it wasn't a major problem, they worked ok, just odd that a mapped share worked when the PC wasn't showing under Network.
    Mapping will make it work. Clearing the DNS cache is a great idea if the affected computers are changing IP's.

    The Function Discovery Resource Publication service is not running on some installs/upgrades of 1803 for some reason. This causes the fail to see the networked computers in File Explorer.
      My ComputerSystem Spec

  7.    1 Week Ago #17

    Access Denied said: View Post
    The Function Discovery Resource Publication service is not running on some installs/upgrades of 1803 for some reason. This causes the fail to see the networked computers in File Explorer.
    Starting the Function Discovery Resource Publication service helps Windows to discover and see the other computers in the network. They do indeed get discovered and begin to appear in the "Network" folder.

    However, none of this has any effect on the errors that pop up when trying to see the shares or connect to shares on the remote computer. Simply trying to see the shares by clicking on a specific computer in "Network" folder results in

    Error code: 0x80070035. "Windows cannot access \\<computer name>"

    Occasionally the issue clears, but only temporarily. There's no known fix for this issue at the time, besides reinstalling SMB 1.0. The only other hope is that it is going to be fixed in future updates.
      My ComputerSystem Spec

  •    1 Week Ago #18

    AndreyT said: View Post
    Starting the Function Discovery Resource Publication service helps Windows to discover and see the other computers in the network. They do indeed get discovered and begin to appear in the "Network" folder.

    However, none of this has any effect on the errors that pop up when trying to see the shares or connect to shares on the remote computer. Simply trying to see the shares by clicking on a specific computer in "Network" folder results in

    Error code: 0x80070035. "Windows cannot access \\<computer name>"

    Occasionally the issue clears, but only temporarily. There's no known fix for this issue at the time, besides reinstalling SMB 1.0. The only other hope is that it is going to be fixed in future updates.
    I had that error on my network and it was fixed by setting all Advanced Sharing Settings, NTFS permissions and sharing permissions correctly. I have not had it since. Don't read this the wrong way, because I know Windows will run different on each computer. This just happens to be one of those things where some have that error when set correctly and some don't. Like you posted the fix with SMBv1 is the only fix for some, while others work the way it should.

    Maybe one day, when the computer is setup correctly, all things will perform as they should, but hey, this is MS we are talking about.
      My ComputerSystem Spec


  • Posts : 61
    Windows 10 Pro x64 (ver 1709) Build 16299.214
       1 Week Ago #19

    sorry to pop in, but i'd like to join the discussion

    my laptop recently updated to 1803, while my pc still remains on 1709. i tried connecting lan to transfer files using network share but to no avail. the connection on the taskbar shows yellow hazard after whatever i do. but starting "Function Discovery Resource Publication" service has finally pop up my laptop network on my pc. i couldnt see it before (but if i show all hidden files, its there).

    but the problem still remains, i could not access it. ive checked the security tab and i've set "Everyone" to have full access. i've also enabled SMB 1.0 on the windows feature. rebooted but it doesnt seem to help. is there any other way to solve this? i'd greatly appreciate any help. im in dire need of transfering large files.

    also side note, i can share from my pc to my laptop without any hiccups. it works well. my laptop seems to be the issue here. help pl0x :/
      My ComputersSystem Spec

  •    1 Week Ago #20

    Pretty much the same with me. I can see my 2 NAS and access their files and now I can see each computer in the network but just can't access them.
    My Surface Pro has no problems accessing one but not the other. All of this is due to 1803.
      My ComputerSystem Spec


  •  
    Page 2 of 7 FirstFirst 1234 ... LastLast

    Related Threads
    Hi Guys, I've had many problems with sharing since the 1709 update - was fine before that. Now I've upgraded my PCs to 1803, more issues (Thanks MS)... I've shared the "D:" data partitions on my three PCs, with full access for everyone,...
    I have a Hauppauge WintTV-HVR-2255 that was working fine before the Windows 10 1803 update. The digital ATSC tuners work fine, but the analog tuners (and the analog inputs) have stopped working. When I scan for the inputs using NextPVR I get an...
    After upgrade to 1803 my microphone is not working properly. I googeld and found many times this answer: Hit Windows key and search for "microphone privacy settings" Hit "Allow access to the microphone on this device" Switch "Allow apps to...
    After upgrade, my computer is unusable. I have the same problem as here: https://www.tenforums.com/installation-upgrade/109176-1803-upgrade-fault-c-windows-system32-config-systemprofile-destop.html#post1360304. Nothing works, just the run...
    Found problems The apple airport printer can't print Network Center can't click out 'Change adapter settings', so you can't disable a connection
    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 01:30.
    Find Us