Please note that using Computer Browser service would not prevent the new WS-Discovery protocol from discovering network devices on computers with operating systems satrting from Windows Vista, thus making the resulting list of computers and network devices the total of the two lists provided by the two distinct protocols.
In times of Windows XP (and I think in times of Windows 7/2008R2 as well) most network administrators were using Computer Browser service to populate Network Neighborhood folder: it was enabled by default on all Windows XP computers and was set to start manually on Windows 7 computers – it was possible to create a policy which starts Computer Browser service on all computers and continue using the old discovery method. Before making any suggestions about what can be causing this behaviour let’s recap what two main network discovery methods exist in Windows networks:ġ) Computer Browser service which depends on SMB1 (it was already in use in Windows NT)Ģ) WS-DISCOVERY protocol (presented in Windows Vista) This problem gets just more complicated when various OS are being used throughout an organization: for example, some users can see one subset of computers in their Network Neighborhood when logged on to a Windows 7 workstations and see the other when logged on to a Windows 10 workstation. Many of you may have seen plenty of questions on msdn/technet regarding network discovery in Windows 10 – something like “On my newly installed Windows 10 no computers (or not all) show up in Network folder”.
0 kommentar(er)
