Right click and open the sub-folder's Preferences and open the Security tab and click "Advanced",. You may need to also do this for the particular user you intend to access the QB company file depending on your set up. After hours of web searching and trying multiple different setting options i came across this website. I followed the 11 steps and created an limited user account in windows Signed into the new account, then immediately signed back into my account and wallah all my network computers plus my 2 synology servers reappeared.
Thanks, Steve. Then why isn't there an approved authoritative fix from the Microsoft Staff, Microsoft Programmers, whatever? Who are we talking to with all these questions and answers?
Just each other? Blind leading the blind? Where there's no distinction between replying to the thread and replying to a particular post? Looks to me like the whole thing is an orphan.
Stuck out here by Microsoft as a red herring to distract us and lead us away from troubling them, and then abandoned. There should be a 'checklist', surely, at the very least, for initial setup? After the style of 'If you have this set this way and that set that way and the other set the other way and running this tool says this and running that says that then it should work.
That's the way we work when we troubleshoot issues. Go through our checklist. And if we really know the prog or even wrote it ourselves then we have a checklist that solves the problem every time or discovers a previously unknown bug.
And then we turn to checkpoints, debugging - and MS could give us directions to do that, too, or could even have a tool online that does it.
I've got five computers on our home LAN. At the moment. And a couple of wifi routers. And an NVR. And a smartphone gets in there too. Found a great work-around for a workgroup in windows When it is open, pin it to the quick access menu. Repeat the process for all computers in your workgroup and on all of your network computers.
Works like a charm. Whilst searching for a solution to my Win10 networking problem, I came across this post and the various replies. Obviously many people are having exactly the same issue and I find it difficult to understand why Microsoft have not provided an "official" fix after a period of almost 2 years.
There appear to be many technical people on here who have devised various workarounds which work for some people but not for others. It should not be necessary to be a technical expert to achieve a fix. Microsoft should "own" the problem and urgently issue a fix - which is clearly a Win10 problem. I have a small office network with one laptop running Win10 and another running Win7.
On the Win7 laptop I can see everything on the lan with no problems and all drives are accessible no matter where they are on the network. I have tried various fixes suggested in the many replies to this post, but cannot get anything to work.
I have not tried some of the more technical fixes suggested as I don't want to get in too deep, beyond my level of knowledge. If this forum is owned by Microsoft or has Microsoft staff contributing, it would be useful if any replies made by those people are identified as a Microsoft answer, rather than a reply by a contributor who may be trying various workarounds themselves.
This problem with Win10 seems to have been open for a long time without Microsoft proposing a permanent, acceptable solution. Many workarounds have been offered and they seem to work for some people, but not others. I tried a number of them without success, but now I have found one that works for me. Someone suggested that we should ensure that SMB 1. Others suggested that was not a good solution as it has security issues.
However, I decided to try it. This appears to have 3 sub-features The 1st and 3rd option were checked on and the 2nd option client was unchecked off.
I changed the 2nd client to checked on and rebooted and it immediately fixed the problem. I can now see all network computers and network-attached storage.
So, this suggests to me that the problem was caused by this option being unchecked. Now, I know that I have not switched this option off, so something else has switched it off. As far as I can see, this must either be caused by changes made by Windows Update or by Virus Protection software attempting to eliminate the potential security problem which many people have mentioned.
Therefore, it seems that this feature could be switched off again by a future update Either way, it looks like this is something for which Microsoft need to offer a permanent fix. I assume that there are Microsoft staff reading this forum, so There are many people waiting for your answer.
Both Nas are from Qnap, I believe they run at custom Linux system. My Desktop has no problem finding both Nas as Computers, as Media devices and finds the laptop as a Computer, Alongside showing itself in the Network.
The Laptop though, sees both Nas as media servers, does not show them as Computer, and does not see my Desktop nor itself. It just doesn't see them. I followed these instructions and I can now see all of my network computers, printers and storage devices Thank you so much for supplying an answer I did have connections between them by mapping but could not find by browsing. From all of the machines I can see both W7 machines, and one of the W10 ones, but none of the other two W10 ones.
This started to happen about two weeks ago. I have tried to look up some of the answers in this thread, but I am not so technical so I dare to try some of the solutions.
Anyway, I think this is an issue that should be solved by Microsoft, not by some devoted users. Checked their settings and they have SMB enabled. Found a 1min youtube video which showed me how to apply fix.
Not sure what can of worms I have opened but system is now working, thank you for help. Caveat - Office politics and exec ego ie they have newer sexier toys than we do will trump KISS sooner or later though so watch your back But being in IT we have many ways to watch - everything - and still hold the moral high ground by strictly limiting the use of our expanded consciousness, well until you get canned, then remember the old saying, revenge is a dish best served cold and with plausible deniability.
If they are not running, right click on them and select start. I am running Windows 10 Spring feature update or whatever it is called on my main PC and on a machine I use as a server. After updating the these 2 PCs to the Spring update all my network shared folders were gone. Well, not gone, just inaccessible. Same difference! I do not know if I needed to start the second one but someone in a later post referenced 2 services starting with the word "Function" so I figured what the heck and started both.
I set them to automatic and then had to start them manually. Double-click on Services. Scroll down until you see the "Function" services. Right-click on the first one and select Properties from the menu. Set Startup type to Automatic.
Then Left-click the Start button under Service status. Do the same thing for the other "Function" Service. Do this on every PC on your network if these services are not running. No promises this will work for you but after fighting with this for more time than I can estimate I was willing to give it a try and it did work for me.
A Windows update should NOT stop critical sharing services that were clearly working before!!!!!! One other annoyance, this update set my server PCs login credentials to my MS account not the local username and password I had it set to. I can't believe this issue is almost 1 full year old and yet, no official solutions, just tricks and work arounds.
Thanks to. This problem arrived on my laptop after the Spring upgrade to Windows 10 suddenly the laptop could not recognize the other computers on my network by name, though it could access them by IP. The desktop was continuing to access the NAS by name successfully, as it always had.
After trying most of the suggestions in this and other forums without success, I have solved it as follows:. It must have been like that for years. Presumably facilities that were removed in the recent Windows upgrades had been bypassing that problem somehow, but now it mattered.
So this is something to check even if everything has been working in the past. Correcting this enabled the laptop to see the names of the other two machines in PC Explorer - Network. However, it still couldn't access them by name. Once that was set to start Automatic Delayed , that machine was detected correctly by the laptop and everything functioned ok between those two machines.
The file turned out to have no mappings in it at all, just a few instructions about how to set them up. Now everything worked correctly. I went back and disabled the SMB1. I still don't fully understand what had happened. It is possible that I used to have a mapping for the NAS in the laptop's hosts file it's a long time since I set the system up, and I may have done that and forgotten about it , and that got overwritten in the upgrade; but then why didn't the desktop have the same problem?
I have checked, and that also has a recent, and null, hosts file. I concur in the general opinion that there's something deeply unsatisfactory about the Windows name discovery process; it just doesn't seem reliable or consistent. I'm posting this here for two reasons: First, to suggest to others who are struggling with this issue that you try putting a mapping in your client machine's hosts file, if the critical thing is for those machines to be able to access a server that has a fixed IP.
Secondly, in the hope that someone can explain why the laptop's behaviour is so different from the desktop's - because I like to understand things. Both machines are running fully updated Windows 10, but the laptop has Home whereas the desktop has Pro. The desktop was originally supplied with Windows 7 and was upgraded directly to Windows 10; the laptop was originally supplied with Windows 8 and upgraded from there. Any thoughts would be welcome. This helped me in my case: seven Win 10 computers on LAN.
Function Discovery Resource Host. Function Discovery Resource Publication. SSDP Discovery. UPnP Device Host. He says mapping is easier and more secure. The following how-to proves it's easier Network broken? What I am wondering is why don't the official help resources simply refer users to how to map network drives in Windows 10 as an easier, safer, superior solution to replace the complicated, less-secure methods that have been discontinued in Windows 10?
Sure would save a lot of headaches and wasted time, if that is indeed the best practice to follow in W All was Ok with my other computer, running Windows 10 Home. The computer running Windows 10 Pro, was the one with all the issues, I tried everything, then a complete new install, same issues. Then this wonderful solution. Thanks again. For me, it was the one under it: Function Discovery Resource Publication.
It was stopped. I started it and set it to auto. We'll see if it lasts through updates and restarts, but at least all pc's became immediately visible! I too have the same problem with mixed systems, some windows 10, some windows 7. Not all systems have SMB as a windows option, but I know if enabled, works for most. Yes, this is a MS issue. They have no problems waking up my system in the middle of the night to install updates, but can't fix a simple folder share on a basic network.
By assigning each Win7 a password in Managing Credentials section, taking another step of using run: netcfg -d to clear the current network settings with reboot of all machines sharing network drives across my lan worked. For each machine it is easy to use RUN control userpasswords2 to fine tune password and login. You are so Absolutely Correct. And yes!!! This is a ridiculous issue for so long for so many Same thing for me, After doing battle and searching forums for about a day and a half trying to hook up my network I killed the power to everything, PC's Modem the lot, and went to work.
That evening when I came home I powered up and it just worked. And I have no Idea why. Right Away. Thank You. I am grateful. I changed my dns server to my routers IP address with the same static IP address and it worked. I dunno if this might help some of you, but I've wasted a LOT of time on this problem so its worth a shot. No more updates for me.
I have this common problem. I have tried most everything mentioned in this thread without success. But the XP could not get the Win10 Home files. Now with two Win 10 Home and Pro files cannot be shared between either.
Computer 1 — Win 10 Home. Connects to internet successfully. Computer 2 — Win 10 Pro. Adapter Setting — WiFi. Advanced Sharing Settings.
Guest or Public. All Networks. Volume Properties. Results — Windows 10 Home. Results — Win 10 Pro. Services — Win 10 Home and Win 10 Pro. On a newly installed Windows 10 Enterprise now at Build My 'upgrade' CD was the Build so I let it do all the updates up and including the April update as well as the Oct update to Build ? This errant PC can browse itself. Have tried to enable Workgroups on all machines duplicating the unique workgroup pwd and then tried removing the Workgroups.
Nothing so far will allow Win 10 to browse this one machine. No success there either. Don't like MS? Then erase your Win and install your favourite version of Linux. Finally I started Peer Networking Grouping service on Win10 machine and voila all of a sudden all my Win7 machines show up under Network.
After disabling IPv6 and setting up private networking, enabling SMB in windows programs and features in Win 10 fixed everything for me. I've been battling this Credentials issue all day on one of my home computers that's been on loan to my nephew-in-law. I brought it home yesterday to install the latest Win10Pro Feature Update, version last night. Once I added new Windows Credentials for each of the other computers, all is well. I'm thinking the older hardware doesn't have the ability to handle the task by itself.
Office Office Exchange Server. Not an IT pro? Resources for IT Professionals. Sign in. United States English. Ask a question. Quick access. Search related threads. Remove From My Forums. Answered by:. Archived Forums. Windows 10 Networking. Sign in to vote. Private current profile "Turn on network discovery" is checked "Turn on automatic setup of network-connected devices" is checked "Turn on file and printer sharing" is checked Password protected sharing is off and so i windows firewall for private networks.
Im out of ideas and in need of some help. Any that could be given would be great. Thanks for your time Harry. Sunday, July 10, AM. I was seriously looking for a hidden camera it was that much of an IT guys moment "Have you tried turning it off then on again" SO in short Homegroup is working a treat, file sharing is going great and everything seems to be working to make me look like a n00b on this forum.
Thanks for the help. Monday, July 11, AM. Sunday, July 10, PM. Hi M8Harry, Good to hear that you have resolved it. Best regards Please mark the reply as an answer if you find it is helpful.
If you have feedback for TechNet Support, contact tnmff microsoft. Tuesday, July 12, AM. Thanks for your time Harry tried all of above but problems persisted. Saturday, September 17, AM. Millions of us are experiencing the same random results with Windows 10 networking.
Fix the damned problem. Monday, July 17, AM. A normal join of a work group plus the usual sharing adjustments just don't work. It is something in the guts of the shared elements of 10 and Server and frankly I have a hard time believing MS has made such a mistake, heard so many complaints, and still refuses to fix it. After all, they have no problems maintaining a persistent connection to most Windows 10 machines from Redmond, so i think they know a bit about networking.
Sunday, July 30, AM. Friday, August 4, PM. Have to agree. Trying to bail out a small office that's as plain jane as it gets and as stated by others am seeing the same thing with homegroup sometimes working then if left unattended for 10 minutes symptoms change. All workstations are Windows 10 Pro. Workstations sometimes see a home group to join but sometimes do and sometimes don't after timing out and then stating there are no homegroups to join. They then will try to create one which may or may not fail as well.
This while other workstations are able to join and even share. Wait 10 minutes and the situation may change. All are able to access INET and local apps are working except ones that need sharing of files.
Worst networking sw I've run into from MS ever. Monday, August 7, PM. Not closed at all. Still having the same issues. Ghost homegroups, can't see computers on the network and the advanced sharing settings change themselves with every other Windows update. So I get call after call saying "My scan to folder stopped working.
I spend days of every week setting the sharing options back to my preferred settings on dozens of PCs. Thursday, August 10, PM. We have a small office network which I manage for the company 4 identical computers, 3 printers, 1 hub and a cloud drive backup unit, all was working well until the last update, now 1 computer can see the other 3 and all the printers etc , but the other 3 cannot see anything at all apart from each others media folders Watching this thread with interest.
Thanks for keeping this thread alive. Sunday, August 20, PM. I chose not to reload Operating sys. Friday, September 1, PM. Mine stopped working after the big spring update. Old win7 updated to win 10 and new computers with win 10 installed. Keep hoping the next update will fix it. The other way I get around this is map a drive. I agree with all, MS really screwed us up.
Based on searching this has been going on for some time. This thread is the newest I have found. Hopefully we get an answer soon. Causes me much grief.
Saturday, September 2, AM. When this setting is disabled, your PC is hidden from the local network, and other PCs are hidden from you.
Once network discovery has been enabled, you should be able to see other computers in the Networks tab—but only if those devices have network discovery enabled, too. You can also access devices directly by typing their IP address or hostname in the address bar at the top of the File Explorer window.
The Windows Firewall is designed to block unnecessary traffic to and from your PC. One way to check this is to use the ping command from a PowerShell or command line. This would likely suggest a software or network configuration issue elsewhere. If Windows detects any problems with your network configuration, it will automatically attempt to fix them.
For instance, a feature called wireless isolation sometimes called client isolation or AP isolation on some routers will hide wireless devices from each other on a local network, preventing you from connecting to them from your PC.
Apple devices are usually very good at detecting other Apple devices, thanks to the Apple Bonjour networking service, and it can usually detect other Windows and Linux PCs, too. If you want to see other computers on macOS, you can do this by clicking the Network tab in the core macOS Finder app. Once checked, you should be able to see a Connected servers tab in Finder, where your connected PC will be shown for you to access. In the Network settings menu, check your connection type in the left-hand menu—the icon next to your connection should be green.
Can anyone help explain what is going on here? This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread. I have the same question 7. Report abuse. Details required :. Cancel Submit. Andre for Directly Independent Advisor. Hi Trippap Which version of Windows 10 is currently installed?
0コメント