New
#11
Is everything working good now? If so please mark the thread SOLVED at the bottom.
Glad we could help out here. :)
Is everything working good now? If so please mark the thread SOLVED at the bottom.
Glad we could help out here. :)
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 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.
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.
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.
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. :)
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 :/
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.