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. Viewed 5k times. Improve this question. Have you scanned for internet devices? Add a comment. Active Oldest Votes.
Improve this answer. Tetsujin Tetsujin BTW You should intensify the scrambler. I can decypher Tetsujin and Well… one right, one wrong, but I take your point ;- Will tweak — Tetsujin. I've always found that Windows doesn't see the Mac as 'advertised' on a Workgroup share if Windows-specific sharing isn;t enabled.
Took me ages to get all the machines here speaking nicely to each other, but they do with that setup. Ask Different is a question and answer site for power users of Apple hardware and software. It only takes a minute to sign up. Connect and share knowledge within a single location that is structured and easy to search. I've encountered a somewhat strange problem on my Mac. Recently, all the devices listed in the 'Shared' section of the Finder sidebar have all disappeared and has been replaced an 'All Strangely within this option the shared servers don't even appear there.
Instead there is a folder called 'Servers' and within that are two shortcuts that lead to the root drive of my Mac which is named "glados" on the network. However, on another mac on my network, things seem all fine and dandy there. It even picks up the troubled Mac which appears as 'Javan's MacBook Pro' thanks to bonjour and appear in both the sidebar and the Network folder.
Before shots get fired, Yosemite has nothing to do with this. I've troubleshooted for hours and hours and have come to the conclusion that it is not the cause. I've verified that the network settings are the same on both Macs and they are and I've even used a program called 'Bonjour Browser' to scan the network for the AFP share service on both Macs and both can detect each other and themselves on the network.
Also, if I manually connect to a shared drive on one of the PC's or the iMac via 'Connect to Server' the connection is fine and appears on the sidebar however its named as the IP address of the shared drive and is only temporary as it disappears as I disconnect, which is totally useless.
I've reverted back using Time Machine to when the MacBook was running Mavericks and the problem still existed. So it leads me to believe somethings gone wrong with some sort of preferences file perhaps? I've tried deleting com.
I'm fresh out of ideas, and other existing forums on the rest of the internet haven't seemed to fix it. If anyone has a remote idea any help would be appreciated! Thanks internet! In the dropdown list on the right side to the right of the server address there's a drop-down icon. I clicked on it and it showed a "Recent Servers" list.
I figured I'd see if an old connection would work. I clicked on one of the "Recent Servers" and it worked. All of them. Don't ask me why, but I don't feel like wasting any more time on it and it was super easy. Perhaps it forced a refresh of the plist or something A much simpler way is to delete the plist, reboot and reconfigure.
After tried out all the above suggested, none of it work. Found a solution That Works!! Nothing worked for me either. Windows10 Pro has this missing network PCs problem despite correct settings in network discovery, etc.
Try the following steps to resolve this missing network PCs problem. You should see a list of settings with leading check boxes. Pull slider bar on right side to scroll down to SMB 1. Click to check SMB 1. Click OK to complete and restart. I noticed that step 3, 1st 2 settings were already checked for Windows10 Home, but not for Windows10 Pro. The reason I needed this was that some legacy application I had to install could only map the network location by browsing via the Network location window and mapping my location.
Please take note that in enabling SMB 1. Micosoft deliberately disabled this feature to prevent cyberattacks by malicious hackers. Use SMB1.
I understand that SMB2. Thank you! RE: After Windows 10 v or v Upgrade 1. Open the Windows Services Management Console services. Click on the Windows Start icon then type services. In the list of services, look for the Function Discovery Resource Publication service. It will show as manual. Change the service startup type from Manual to Automatic I changed this setting to Automatic rather than delayed.
Click on Apply, then OK. Restart the computer and re-enter services. If the services do not show as running, right click, select Restart. And going through all this will work until one of the computers updates again. I found a workaround. I place a shortcut to each of the other computers on my desktop. I have long believed that Windows is junk software and Microsoft could care less if it works.
Wow, I finally have both computers listed. Much obliged! Make sure this is turned Off. Took me quite some while to realize this was also in effect when not connected to a vpn network. This was my problem. Thank you very very very much JS!!!!!!!!!!!!!!!!! Probably many people are suffering from this issue. I have the freedom to modify it as I see fit.
I have only one and one Alienware R7 with this crappy Windows 10 — After so many frustrations with it. I installed Linux, out the door W10 no more issues for me. Oh there are plenty issues with Linux, believe me! Having tried numerous times over the years to install it on ex Windows laptops, Linux always makes those laptops run on high CPU and high fan speeds due to its lack of proper control over these.
Unlike Windows, Linux is often a pain on laptops for this reason. Look it up. Which makes sense, I havec made the appropriate settings with my Samba server to make it the master.
And, no, it isn't just me, it's everyone on my network. After changing all of the settings as recommended and rebooting, I was able to see all of the computers from all of the other computers. But the laptop keeps randomly disappearing from the other two, and the other two keep losing visibility of the laptop. Today, all of them were visible and I could share files fine.
Then I closed my laptop, sleep mode. I restarted the laptop, and then I could see the Win 7 PC again. Thanks in advance. I had window 8 and 7 and worked perfectly. I now upgraded all three office computers to window I just cannot get the network done even though I seem to have done all the above article suggested. This is a nightmare.
Why can Microsoft get away with this? They really need to fix this!!! I had to use the services management console which resolved the issue about network discovery. It worked.. Tons of work in this article and informative. But, when I see a screenshot that is from an old build like the one that shows homegroup you have, it makes me believe the information may not be up to date on the other examples and fix suggestions. Just a friendly FYI. Hi, in my company used work group computers.
I think new user Id create is not a easy way no possiablity. I need to smart way any run script file this issue resolved thankful. I have been dealing with this problem for years. My home office Windows network sharing has always been intermittently reliable with some devices showing up and others not showing.
I almost never know what changed between times working and not working times. From my perspective, MS shared networking is pretty much a black box. This time, I was really stuck with absolutely no luck for a few weeks.
By chance, I was looking at my 3 month old Comcast XB7 wireless router. I was surprised to see that even though all of my wireless devices were working perfectly, the Comcast router said they were all offline.
0コメント