Page 11 of 29 FirstFirst ... 91011121321 ... LastLast

  1. Join Date : Jan 2016
    Posts : 1
    windows 10
       11 Jan 2016 #101

    It works


    KRL said: View Post
    Open the services menu by clicking start and then clicking RUN and typing 'services.msc' and pressing enter.


    Look for the following services in the list:

    · DNS Client
    · Function Discovery Provider Host
    · Function Discovery Resource Publication
    · Peer Networking Grouping
    · HomeGroup Provider
    · HomeGroup Listener
    · SSDP Discovery
    · UPnP Device Host

    Make sure they are set to AUTOMATIC START instead of MANUAL.

    Go down the list one by one and even if they are running do a mouse right click and SELECT "RESTART".

    On the ones that are showing a blank and not running right click and SELECT "START".

    That's all I did and all 3 Laptops are back in the Networking Panel and in the Homegroup WORKGROUP.
    -----------------------------
    Thanks a lot. It works, by changing only first and third item.
      My System SpecsSystem Spec


  2. Join Date : Nov 2015
    Posts : 64
    Windows 10
       11 Jan 2016 #102

    PCknow said: View Post
    -----------------------------
    Thanks a lot. It works, by changing only first and third item.
    Good to hear. Glad to be of service. Hope they get this worked out soon. Shame we have to go through this much searching and trying to find only short term solutions.
      My System SpecsSystem Spec


  3. Join Date : Dec 2015
    Posts : 2
    windows 10 Pro
       13 Jan 2016 #103

    bearnet said: View Post
    I have gone through this thread and applied some of the suggestions. I have four PCs on a home network (DBNET). They are:
    1) NB, winver 1511 Build 10586.29, Windows 10 Pro 64 bit, cabled to router.
    2) B, winver 6.1 Build 7601, Windows 7 32bit, wireless connection
    3) BG, winver 1511 build 10568.36, Windows 10 64 bit, wireless connection.
    4) DP, winver 6.1 Build 7601, Windows 7 32bit, wireless connection.

    The NB PC cannot see itself on the Network dialog; hence, none of the other three cannot see it either. The other three can see each other and can share files and folders without any problems. Therefore my perceived issue is with PC NB. By the way it did work at one time after updating NB from Windows 7 Ultimate to Windows 10 Pro. I do not recall when this issue started.
    In command mode, NET SHARE reports all shared objects. Pinging ip addresses is no problem between all connections. Pinging NB (192.168.1.11 which is outside DHCP range) response as well as 127.0.0.1. PC NB has no problems with the Internet or the ISP mail servers. It is just missing from the DBNET Home network. I am tending to agree with some of the contributors to this thread that this is an issue with Windows 10 Pro or there is some clandestine setting that we have not yet found. Services such as "Function Discovery Resource Publications" and "Function Discovery Provider Host" are running. Network discovery settings are correct on all PCs and incoming data is not blocked for home network. If there is a setting that I have missed I would appreciate a hint. http://www.tenforums.com/images/smilies/089.gif
    Allow me to update my previous submission which might answer some remaining questions. I have been fooling with this for several weeks and have come up with a plausible answer. Keep in mind that the NB and the BG machines are both on Windows 10 64bit and the others on Windows 7. The state is as follows. PC NB still can NOT see itself on the Network explorer but the Windows 7 machines can. The laptop (BG) cannot see NB in the network explorer either. When I enter \\NB in the URL window; all shares are shown and NB is then listed under Network in the left window. Also, net view in command mode works on all machines. I should also mention that all network settings suggested by GIOBRICK have been set plus all services are running. The only difference that I found, that may explain this, is the fact the PC NB is connected via Ethernet and the others on WiFi. (The router is working as it should). Perhaps Windows 10 has an issue with PCs connected via Ethernet for Home network to operate properly. Does this resonate with other forum members? Hope this helps.
      My System SpecsSystem Spec


  4. Join Date : Jan 2016
    Posts : 1
    Win 10 build 1511
       14 Jan 2016 #104

    Resonates Here...


    bearnet said: View Post
    Allow me to update my previous submission which might answer some remaining questions. I have been fooling with this for several weeks and have come up with a plausible answer. Keep in mind that the NB and the BG machines are both on Windows 10 64bit and the others on Windows 7. The state is as follows. PC NB still can NOT see itself on the Network explorer but the Windows 7 machines can. The laptop (BG) cannot see NB in the network explorer either. When I enter \\NB in the URL window; all shares are shown and NB is then listed under Network in the left window. Also, net view in command mode works on all machines. I should also mention that all network settings suggested by GIOBRICK have been set plus all services are running. The only difference that I found, that may explain this, is the fact the PC NB is connected via Ethernet and the others on WiFi. (The router is working as it should). Perhaps Windows 10 has an issue with PCs connected via Ethernet for Home network to operate properly. Does this resonate with other forum members? Hope this helps.
    I am trying to establish my network. I'm using all Ethernet connections. I have went through all of the various suggestions without any luck. I am using build 1511. Three of my boxes are 10586.63. One of them is a very small notebook that has some different build (did not say - just a product id. The Video Box mentioned below is actually a NUC box and is running 1511 10586.36

    My main box can see a Win 7 box. The Win 7 box can see and connect to the drives on the main Win 10 box. The Win 10 box can see 2 of the other Win 10 boxes and the Win 7 box but it will not allow it to connect. To really stir it up. The Video Box that is Win 10 can see and share with the Win 7 box.... The only difference on it that I can even see is that I do not require a Sign on Password on the Video Box. ( I tried setting one of the other Win 10 boxes this way but it still could not connect to the Win 7 box) I have also went through and matched the local policy items. The GPO items are all "not selected".

    After having tried all of the suggested fixes, I'm at a loss and can only think that MS has something that is killing me. I have turned off all of the spyware reporting back to them but I guess I can turn on the updates again if they ever solve it.

    Any ideas would be appreciated.
      My System SpecsSystem Spec


  5. Join Date : Jul 2015
    Land of Enchantment
    Posts : 115
    Win 10 Rel 10586
       14 Jan 2016 #105

    It is a Microsoft network issue and a fix is supposedly being worked on. Problem apparently is that Win 10 does not broadcast NetBT request over a LAN when searching for devices thus all devices are not being discovered.
      My System SpecsSystem Spec


  6. Join Date : Jan 2016
    Langhorne
    Posts : 1
    Windows 10
       15 Jan 2016 #106

    Brilliant - Worked Great - many tnaks for taking the time to help


    Many thanks for the advice which worked perfectly. I am always appreciative of really smart folks like yourself who also take the time to help other less gifted users but still passionate users like myself.

    Your wrote:
    If you want to check it out, open SERVICES on EACH PC or server on your workgroup or domain, scroll to "Function Discovery Resource Publication", and start it. Then check to see if all your pc's show up in explorer. There is also a "Function discovery Provider Host" that may play into it. There are a few other settings that may play into other device discovery that I'll have to look into. All my devices actually show up though.
    If this works for you, change the start up for the service to automatic and it should stay on. I don't know the ramifications of changing this setting so Ill be monitoring to see if there are any obvious ones.

    My guess is that some change that was implemented in the latest insider builds has affected network discovery. I know that my servers all had this ("Function Discovery Resource Publication") turned off for as long as they've been in service, which is a matter of years, and it always worked, so it isn't the other pc's, it's the Win10 boxes.[/QUOTE]
      My System SpecsSystem Spec


  7. Join Date : Jan 2016
    Posts : 3
    Windows 10 10586.63
       16 Jan 2016 #107

    Disabled Samba 3 on the PC not showing in the network list, rebooted it and now it's showing. Thanks.
      My System SpecsSystem Spec


  8. Join Date : Jan 2016
    Posts : 2
    Windows 10 Pro
       18 Jan 2016 #108

    Solved - Master browser conflict


    I too had network devices no longer visible in the Network folder of a Windows 10 desktop PC, although I could navigate to them by typing \\devicename in the address bar. Strangely though my Windows 10 laptop showed part of my network in its Network folder, but not the other part. A Windows 7 laptop could see everything without a problem. This strange behaviour began around the time of the 1511 update last year. I managed to solve it after some digging.

    My network was configured as 2 workgroups; one Windows 10 laptop and a NAS running in a workgroup called MSHOME, and a Window 10 PC, a Windows 7 laptop and 2 further NASs in another workgroup called WORKGROUP.

    The MSHOME Windows 10 laptop didn’t show the WORKGROUP devices in its Network folder, but did show the MSHOME NAS.

    The WORKGROUP Windows 10 PC only showed itself in the Network folder, although I could navigate to both of the MSHOME devices and to one of the WORKGROUP NASs without a problem. However, when I tried to navigate to the second WORKGROUP NAS, which ran under NAS4Free, I got an error saying that the PC did not have the necessary protocol to do so.

    Following advice elsewhere, I moved all my devices into WORKGROUP. And guess what? Now the Windows 10 laptop only showed itself in its Network folder. Things had got worse. At least the Windows 7 laptop still showed everything.

    I tried most of the solutions suggested in this thread and elsewhere, but nothing seemed to work. Then I stumbled upon a post that talked about Master browsers, something I had not heard of before. Basically, the devices on a TCP/IP network get together and choose one of them to hold a map of the addresses of all the devices, and what workgroups they belong to. This speeds up network discovery. Windows 10 seems to depend on it much more than Windows 7.

    I came across a very handy description here:

    http://scottiestech.info/2009/02/14/...ows-workgroup/

    It also provides a simple tool to help you determine what you have on your network, and which device has the Master browser. I ran this tool and discovered that my workgroup had TWO devices claiming to be the Master: one was the NAS4Free NAS and the other was my Belkin router. Although one of the devices should have backed off, neither would. NAS4Free gives you the option in its CIFS settings to stop it becoming a Master. I did this, rebooted the PC and laptops, and everything worked. The Network folders of both Windows 10 machines showed all devices, whether in WORKGROUP or MSHOME. The protocol error disappeared as well. So if you are still having problems, give this solution a go.
      My System SpecsSystem Spec

  9.    18 Jan 2016 #109

    steveinlondon said: View Post
    I too had network devices no longer visible in the Network folder of a Windows 10 desktop PC, although I could navigate to them by typing \\devicename in the address bar. Strangely though my Windows 10 laptop showed part of my network in its Network folder, but not the other part. A Windows 7 laptop could see everything without a problem. This strange behaviour began around the time of the 1511 update last year. I managed to solve it after some digging.

    My network was configured as 2 workgroups; one Windows 10 laptop and a NAS running in a workgroup called MSHOME, and a Window 10 PC, a Windows 7 laptop and 2 further NASs in another workgroup called WORKGROUP.

    The MSHOME Windows 10 laptop didn’t show the WORKGROUP devices in its Network folder, but did show the MSHOME NAS.

    The WORKGROUP Windows 10 PC only showed itself in the Network folder, although I could navigate to both of the MSHOME devices and to one of the WORKGROUP NASs without a problem. However, when I tried to navigate to the second WORKGROUP NAS, which ran under NAS4Free, I got an error saying that the PC did not have the necessary protocol to do so.

    Following advice elsewhere, I moved all my devices into WORKGROUP. And guess what? Now the Windows 10 laptop only showed itself in its Network folder. Things had got worse. At least the Windows 7 laptop still showed everything.

    I tried most of the solutions suggested in this thread and elsewhere, but nothing seemed to work. Then I stumbled upon a post that talked about Master browsers, something I had not heard of before. Basically, the devices on a TCP/IP network get together and choose one of them to hold a map of the addresses of all the devices, and what workgroups they belong to. This speeds up network discovery. Windows 10 seems to depend on it much more than Windows 7.

    I came across a very handy description here:

    http://scottiestech.info/2009/02/14/...ows-workgroup/

    It also provides a simple tool to help you determine what you have on your network, and which device has the Master browser. I ran this tool and discovered that my workgroup had TWO devices claiming to be the Master: one was the NAS4Free NAS and the other was my Belkin router. Although one of the devices should have backed off, neither would. NAS4Free gives you the option in its CIFS settings to stop it becoming a Master. I did this, rebooted the PC and laptops, and everything worked. The Network folders of both Windows 10 machines showed all devices, whether in WORKGROUP or MSHOME. The protocol error disappeared as well. So if you are still having problems, give this solution a go.

    Hi there

    Just sits forever and doesn't do anything -- running latest build 1511 W10 x-64 pro.

    Network currently - One Linux server, W7 ultimate x-64, XP Pro (as a VM on Linux Host) , 2X W10 systems, one Linux test box.

    The W10 systems have the network problems - even the XP VM on a Linux Host sees the W10 machines.

    Click image for larger version. 

Name:	lantool.png 
Views:	5 
Size:	15.9 KB 
ID:	59502


    Cheers
    jimbo
      My System SpecsSystem Spec


  10. Join Date : Jan 2016
    Posts : 2
    Windows 10 Pro
       18 Jan 2016 #110

    Hmmm...


    jimbo45 said: View Post
    Hi there

    Just sits forever and doesn't do anything -- running latest build 1511 W10 x-64 pro.

    Network currently - One Linux server, W7 ultimate x-64, XP Pro (as a VM on Linux Host) , 2X W10 systems, one Linux test box.

    The W10 systems have the network problems - even the XP VM on a Linux Host sees the W10 machines.

    Click image for larger version. 

Name:	lantool.png 
Views:	5 
Size:	15.9 KB 
ID:	59502


    Cheers
    jimbo

    All I can say is that the little routine worked for me. All it does is automate the steps in Scott Orgin's explanation. You can try to duplicate the individual steps using the CMD prompt (run as administrator to be sure).
    "net view /domain" gives a list of the workgroups on your network
    "net view /domain:WORKGROUP" for each workgroup (substituting WORKGROUP with the name of the workgroup you are interested in). This eventually comes back with a list of devices in the workgroup in the format \\DEVICENAME.
    Then for each device: "nbtstat -a DEVICENAME". This gives you a table of information for the device.
    One or more of the devices in a workgroup should show a property in the format __MSBROWSE__. This is a Master browser. If you have more than one in a workgroup, you have found your problem...

    If you need more help, you could try looking through the comments on Scott's website - you'll see others had problems. Otherwise, you could try this site:

    http://petestechblog.com/archives/847

    Good luck!
      My System SpecsSystem Spec


 
Page 11 of 29 FirstFirst ... 91011121321 ... LastLast


Similar Threads
Thread Forum
i upgraded 2 computers to windows 10 and java doesnt work on both
i upgraded 2 computers to windows 10 and java doesnt work on both
Software and Apps
Business type workgroup Network
Finally installed Win10 on a computer with raw HD. It installed realtively easy. But I can not figure out how to setup a network to see two Win7 computers on a small business type workgroup. I disabled Homegroup since I am most comfortable...
Network and Sharing
Windows 9 Might Not Work on 32-Bit Computers – Report
More
Windows 10 News
Steampunk computer computer cases/keyboards....
http://i.imgur.com/6tiV6Mo.jpg http://i.imgur.com/hDcLSPe.jpg http://i.imgur.com/5s8rLWI.jpg http://i.imgur.com/Q7UIuP6.jpg
Chillout Room
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 19:53.
Find Us
Twitter Facebook Google+



Windows 10 Forums