|
|
Network broken in Win10 again?
Networking has always seemed like voodoo on Windows. Is there another
issue lately with build 1703 and 1709 where computers just disappear from the network? I can still access them if I map the computers but they simply disappear from the Network. I have three computers, all running build 1709. I've reset the networking on all of them, rebooted one at a time and get them to work. Then after a reboot or two, they're gone again. I had this issue a couple of years ago with Windows 10 and looked high and low for a fix. There are lots and lots of forums and posts online about this issue but no one seems to have a sure-fire fix for it. It this something Microsoft broke yet again? |
Network broken in Win10 again?
|
Network broken in Win10 again?
On Sat, 13 Jan 2018 14:42:17 -0500, EGK wrote:
Networking has always seemed like voodoo on Windows. Is there another issue lately with build 1703 and 1709 where computers just disappear from the network? I can still access them if I map the computers but they simply disappear from the Network. I have three computers, all running build 1709. I've reset the networking on all of them, rebooted one at a time and get them to work. Then after a reboot or two, they're gone again. I had this issue a couple of years ago with Windows 10 and looked high and low for a fix. There are lots and lots of forums and posts online about this issue but no one seems to have a sure-fire fix for it. It this something Microsoft broke yet again? WiFi and Lan ? KenW |
Network broken in Win10 again?
EGK wrote:
Networking has always seemed like voodoo on Windows. Is there another issue lately with build 1703 and 1709 where computers just disappear from the network? I can still access them if I map the computers but they simply disappear from the Network. I have three computers, all running build 1709. I've reset the networking on all of them, rebooted one at a time and get them to work. Then after a reboot or two, they're gone again. I had this issue a couple of years ago with Windows 10 and looked high and low for a fix. There are lots and lots of forums and posts online about this issue but no one seems to have a sure-fire fix for it. It this something Microsoft broke yet again? Yep! Well not completely broken, just not displayed. If you enter the URI manually "\\COMPUTER2" the computer hostname will a appear in the Explorer's left-hand panel under network []Network []COMPUTER2 []COMPUTER3 They will appear *only* after you manually enter each. But click on Network and in the right-hand panel none of them will show under "Computer" Used to, but not after update. So to reiterate shares are accessible just not "visible"... -- Take care, Jonathan ------------------- LITTLE WORKS STUDIO http://www.LittleWorksStudio.com |
Network broken in Win10 again?
On Sat, 13 Jan 2018 14:27:52 -0700, KenW
wrote: On Sat, 13 Jan 2018 14:42:17 -0500, EGK wrote: Networking has always seemed like voodoo on Windows. Is there another issue lately with build 1703 and 1709 where computers just disappear from the network? I can still access them if I map the computers but they simply disappear from the Network. I have three computers, all running build 1709. I've reset the networking on all of them, rebooted one at a time and get them to work. Then after a reboot or two, they're gone again. I had this issue a couple of years ago with Windows 10 and looked high and low for a fix. There are lots and lots of forums and posts online about this issue but no one seems to have a sure-fire fix for it. It this something Microsoft broke yet again? WiFi and Lan ? My three PC's are all on an ethernet, wired, network. No Wifi at all. |
Network broken in Win10 again?
On Sat, 13 Jan 2018 17:19:02 -0500, "Jonathan N. Little"
wrote: EGK wrote: Networking has always seemed like voodoo on Windows. Is there another issue lately with build 1703 and 1709 where computers just disappear from the network? I can still access them if I map the computers but they simply disappear from the Network. I have three computers, all running build 1709. I've reset the networking on all of them, rebooted one at a time and get them to work. Then after a reboot or two, they're gone again. I had this issue a couple of years ago with Windows 10 and looked high and low for a fix. There are lots and lots of forums and posts online about this issue but no one seems to have a sure-fire fix for it. It this something Microsoft broke yet again? Yep! Well not completely broken, just not displayed. If you enter the URI manually "\\COMPUTER2" the computer hostname will a appear in the Explorer's left-hand panel under network []Network []COMPUTER2 []COMPUTER3 They will appear *only* after you manually enter each. But click on Network and in the right-hand panel none of them will show under "Computer" Used to, but not after update. So to reiterate shares are accessible just not "visible"... Thanks for the confirmation. :) It was driving me crazy trying to get it working again but I guess it'll just wait till Microsoft gets around to fixing it again. |
Network broken in Win10 again?
On Sat, 13 Jan 2018 14:42:17 -0500, in alt.comp.os.windows-10, EGK wrote:
Networking has always seemed like voodoo on Windows. Is there another issue lately with build 1703 and 1709 where computers just disappear from the network? I can still access them if I map the computers but they simply disappear from the Network. I have three computers, all running build 1709. I've reset the networking on all of them, rebooted one at a time and get them to work. Then after a reboot or two, they're gone again. I had this issue a couple of years ago with Windows 10 and looked high and low for a fix. There are lots and lots of forums and posts online about this issue but no one seems to have a sure-fire fix for it. It this something Microsoft broke yet again? If you don't use Homegroups, try disabling the HomeGroup Provider service. The only hang-up with that is you will also have to set the Function Discovery Resource Publication service to "automatic," because normally the HomeGroup service triggers it, and that is how computers advertise themselves on the network. So HomeGroups disabled, FDRP on automatic start. If you still get a computer that's missing, restart the Function Discovery Resource Publication service on the missing machine and it will usually show up. But I have found that HomeGroup totally screws up regular SMB shares, even when you don't have a HomeGroup. Personally, I had computers not showing on the network until I disabled it. I had a person over at 10Forums who could not see his NAS, but he disabled HomeGroup Provider at my recommendation and all of the sudden it showed up. Essentially, whatever the HomeGroup Provider service is doing screws up network discovery for LANManager/SAMBA shares, and it's best just to disable the thing if you don't use it. Microsoft turns it back on with every major version change, though, so you have to keep disabling it after a "Feature Update" (e.g.: 1703 to 1709). I hope this helps you too. -- Zag No one ever said on their deathbed, 'Gee, I wish I had spent more time alone with my computer.' ~Dan(i) Bunten |
Network broken in Win10 again?
On Sat, 13 Jan 2018 14:42:17 -0500, EGK wrote:
Networking has always seemed like voodoo on Windows. Is there another issue lately with build 1703 and 1709 where computers just disappear from the network? I can still access them if I map the computers but they simply disappear from the Network. I have three computers, all running build 1709. I've reset the networking on all of them, rebooted one at a time and get them to work. Then after a reboot or two, they're gone again. I had this issue a couple of years ago with Windows 10 and looked high and low for a fix. There are lots and lots of forums and posts online about this issue but no one seems to have a sure-fire fix for it. It this something Microsoft broke yet again? I had this issue, or something similar, and the answer given in this link worked for me: https://social.technet.microsoft.com...tpronetworking |
Network broken in Win10 again?
On Sun, 14 Jan 2018 11:32:42 +0000, Peter Johnson
wrote: On Sat, 13 Jan 2018 14:42:17 -0500, EGK wrote: Networking has always seemed like voodoo on Windows. Is there another issue lately with build 1703 and 1709 where computers just disappear from the network? I can still access them if I map the computers but they simply disappear from the Network. I have three computers, all running build 1709. I've reset the networking on all of them, rebooted one at a time and get them to work. Then after a reboot or two, they're gone again. I had this issue a couple of years ago with Windows 10 and looked high and low for a fix. There are lots and lots of forums and posts online about this issue but no one seems to have a sure-fire fix for it. It this something Microsoft broke yet again? I had this issue, or something similar, and the answer given in this link worked for me: https://social.technet.microsoft.com...tpronetworking I tried that but no joy. It's one of many, many "fixes" I found on the web in MS and other forums. |
Network broken in Win10 again?
On Sat, 13 Jan 2018 23:01:45 -0600, Zaghadka wrote:
On Sat, 13 Jan 2018 14:42:17 -0500, in alt.comp.os.windows-10, EGK wrote: Networking has always seemed like voodoo on Windows. Is there another issue lately with build 1703 and 1709 where computers just disappear from the network? I can still access them if I map the computers but they simply disappear from the Network. I have three computers, all running build 1709. I've reset the networking on all of them, rebooted one at a time and get them to work. Then after a reboot or two, they're gone again. I had this issue a couple of years ago with Windows 10 and looked high and low for a fix. There are lots and lots of forums and posts online about this issue but no one seems to have a sure-fire fix for it. It this something Microsoft broke yet again? If you don't use Homegroups, try disabling the HomeGroup Provider service. The only hang-up with that is you will also have to set the Function Discovery Resource Publication service to "automatic," because normally the HomeGroup service triggers it, and that is how computers advertise themselves on the network. So HomeGroups disabled, FDRP on automatic start. If you still get a computer that's missing, restart the Function Discovery Resource Publication service on the missing machine and it will usually show up. But I have found that HomeGroup totally screws up regular SMB shares, even when you don't have a HomeGroup. Personally, I had computers not showing on the network until I disabled it. I had a person over at 10Forums who could not see his NAS, but he disabled HomeGroup Provider at my recommendation and all of the sudden it showed up. Essentially, whatever the HomeGroup Provider service is doing screws up network discovery for LANManager/SAMBA shares, and it's best just to disable the thing if you don't use it. Microsoft turns it back on with every major version change, though, so you have to keep disabling it after a "Feature Update" (e.g.: 1703 to 1709). I hope this helps you too. Thanks. I do use Homegroups. It's the only way the other computers do show up. I tried turning homegroups off but then couldn't see anything on the network. I did not try to turn on FDRP as you suggest tho so may do that if it continues like this for long. |
Network broken in Win10 again?
Peter Johnson wrote:
On Sat, 13 Jan 2018 14:42:17 -0500, EGK wrote: Networking has always seemed like voodoo on Windows. Is there another issue lately with build 1703 and 1709 where computers just disappear from the network? I can still access them if I map the computers but they simply disappear from the Network. I have three computers, all running build 1709. I've reset the networking on all of them, rebooted one at a time and get them to work. Then after a reboot or two, they're gone again. I had this issue a couple of years ago with Windows 10 and looked high and low for a fix. There are lots and lots of forums and posts online about this issue but no one seems to have a sure-fire fix for it. It this something Microsoft broke yet again? I had this issue, or something similar, and the answer given in this link worked for me: https://social.technet.microsoft.com...tpronetworking I do not use Homegroup. This is my last and only Windows system left so I tried the above. Made no difference. Still no other systems listed in Network. I think it may be more the disabling SMBv1 protocol the cause. -- Take care, Jonathan ------------------- LITTLE WORKS STUDIO http://www.LittleWorksStudio.com |
Network broken in Win10 again?
On Sun, 14 Jan 2018 11:34:39 -0500, "Jonathan N. Little"
wrote: Peter Johnson wrote: On Sat, 13 Jan 2018 14:42:17 -0500, EGK wrote: Networking has always seemed like voodoo on Windows. Is there another issue lately with build 1703 and 1709 where computers just disappear from the network? I can still access them if I map the computers but they simply disappear from the Network. I have three computers, all running build 1709. I've reset the networking on all of them, rebooted one at a time and get them to work. Then after a reboot or two, they're gone again. I had this issue a couple of years ago with Windows 10 and looked high and low for a fix. There are lots and lots of forums and posts online about this issue but no one seems to have a sure-fire fix for it. It this something Microsoft broke yet again? I had this issue, or something similar, and the answer given in this link worked for me: https://social.technet.microsoft.com...tpronetworking I do not use Homegroup. This is my last and only Windows system left so I tried the above. Made no difference. Still no other systems listed in Network. I think it may be more the disabling SMBv1 protocol the cause. Ever think of using a Work Group ? Never had as problem with it. I have no reason to network now. KenW |
Network broken in Win10 again?
On Sun, 14 Jan 2018 09:39:53 -0700, KenW
wrote: On Sun, 14 Jan 2018 11:34:39 -0500, "Jonathan N. Little" wrote: Peter Johnson wrote: On Sat, 13 Jan 2018 14:42:17 -0500, EGK wrote: Networking has always seemed like voodoo on Windows. Is there another issue lately with build 1703 and 1709 where computers just disappear from the network? I can still access them if I map the computers but they simply disappear from the Network. I have three computers, all running build 1709. I've reset the networking on all of them, rebooted one at a time and get them to work. Then after a reboot or two, they're gone again. I had this issue a couple of years ago with Windows 10 and looked high and low for a fix. There are lots and lots of forums and posts online about this issue but no one seems to have a sure-fire fix for it. It this something Microsoft broke yet again? I had this issue, or something similar, and the answer given in this link worked for me: https://social.technet.microsoft.com...tpronetworking I do not use Homegroup. This is my last and only Windows system left so I tried the above. Made no difference. Still no other systems listed in Network. I think it may be more the disabling SMBv1 protocol the cause. Ever think of using a Work Group ? Never had as problem with it. I have no reason to network now. My 3 PC's are all connected via workgroup and homegroup. They still don't appear in the network. I can see them in homegroup but it often takes a long time to connect to the shares with multiple tries saying "not available". Then suddenly it will work. Like I said, Windows networking has always been like voodoo. You just recite a chant and pray. |
Network broken in Win10 again?
On Sat, 13 Jan 2018 23:01:45 -0600, Zaghadka wrote:
On Sat, 13 Jan 2018 14:42:17 -0500, in alt.comp.os.windows-10, EGK wrote: Networking has always seemed like voodoo on Windows. Is there another issue lately with build 1703 and 1709 where computers just disappear from the network? I can still access them if I map the computers but they simply disappear from the Network. I have three computers, all running build 1709. I've reset the networking on all of them, rebooted one at a time and get them to work. Then after a reboot or two, they're gone again. I had this issue a couple of years ago with Windows 10 and looked high and low for a fix. There are lots and lots of forums and posts online about this issue but no one seems to have a sure-fire fix for it. It this something Microsoft broke yet again? If you don't use Homegroups, try disabling the HomeGroup Provider service. The only hang-up with that is you will also have to set the Function Discovery Resource Publication service to "automatic," because normally the HomeGroup service triggers it, and that is how computers advertise themselves on the network. So HomeGroups disabled, FDRP on automatic start. If you still get a computer that's missing, restart the Function Discovery Resource Publication service on the missing machine and it will usually show up. But I have found that HomeGroup totally screws up regular SMB shares, even when you don't have a HomeGroup. Personally, I had computers not showing on the network until I disabled it. I had a person over at 10Forums who could not see his NAS, but he disabled HomeGroup Provider at my recommendation and all of the sudden it showed up. Essentially, whatever the HomeGroup Provider service is doing screws up network discovery for LANManager/SAMBA shares, and it's best just to disable the thing if you don't use it. Microsoft turns it back on with every major version change, though, so you have to keep disabling it after a "Feature Update" (e.g.: 1703 to 1709). I hope this helps you too. YOU have just won the internet for today. :) Thanks very much. I tried this when I had a few minutes and it worked great. All PC's are now showing on the net, Homegroup is disabled and File and printer sharing is all working. Just to be certain though, you only mention homegroup Provider service and FDRP. I set both Function Discovery Provider Host and Function Provider Resource Publication to automatic. Was that necessary or any reason not to set both to auto? I then disabled both Homegroup Listener and Homegroup Provider. Again, was it necessary to disable both or does it even matter? I'll save this post now and hopefully save myself some grief the next time Microsoft upgrades to make things "better" for us. :) Personally, i've never understood the point of Homegroups at all when using workgroups seems much easier and works more reliably. I assume there's security reasons behind it but I really dont know. |
Network broken in Win10 again?
On Sun, 14 Jan 2018 10:17:27 -0700, KenW kenw@
noplace.com wrote: On Sun, 14 Jan 2018 11:49:05 -0500, EGK wrote: On Sun, 14 Jan 2018 09:39:53 -0700, KenW wrote: On Sun, 14 Jan 2018 11:34:39 -0500, "Jonathan N. Little" wrote: Peter Johnson wrote: On Sat, 13 Jan 2018 14:42:17 -0500, EGK wrote: Networking has always seemed like voodoo on Windows. Is there another issue lately with build 1703 and 1709 where computers just disappear from the network? I can still access them if I map the computers but they simply disappear from the Network. I have three computers, all running build 1709. I've reset the networking on all of them, rebooted one at a time and get them to work. Then after a reboot or two, they're gone again. I had this issue a couple of years ago with Windows 10 and looked high and low for a fix. There are lots and lots of forums and posts online about this issue but no one seems to have a sure-fire fix for it. It this something Microsoft broke yet again? I had this issue, or something similar, and the answer given in this link worked for me: https://social.technet.microsoft.com...tpronetworking I do not use Homegroup. This is my last and only Windows system left so I tried the above. Made no difference. Still no other systems listed in Network. I think it may be more the disabling SMBv1 protocol the cause. Ever think of using a Work Group ? Never had as problem with it. I have no reason to network now. My 3 PC's are all connected via workgroup and homegroup. They still don't appear in the network. I can see them in homegroup but it often takes a long time to connect to the shares with multiple tries saying "not available". Then suddenly it will work. Like I said, Windows networking has always been like voodoo. You just recite a chant and pray. Both at the same time. I think that would confuse both. I've just always set the workgroup to the same network as my router out of habit. Since that didn't work to make the computers appear on the network, I set up Homegroups so I could share files and printers. I followed Zaghadka's advice from earlier in the thread to turn Homegroup services off entirely and that seems to have fixed everything. |
| All times are GMT +1. The time now is 03:00 AM. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright © 2004 - 2006 PCbanter
Comments are property of their posters