|06 May 2011||#1|
| || |
What protocols/services/clients for networking?
In Wireless and Local Area Network Connection Properties, on my Windows 7 Ultimate laptop and Starter Netbook, I have reduced everything down to:
Client for Microsoft Networks
Internet Protocol Version 4 (TCP/IPv4)
File and Printer Sharing for Microsoft Networks
- and everything still works, at least as well as before, and possibly even more responsively.
So, my first question is, what does all the other stuff - like "Link-Layer Topology" etc., really do at the moment? I realise that IPv6 implementation will require those protocols, etc., but not yet for Internet or peer-to-peer workgroups, or even Homegroup networking, which seems to operate OK under IPv4 alone.
Secondly, my main problem is preventing VMWare etc., Virtual Ethernet adapters becoming the "Master Browser" (old-fashioned "WINS" resolution) instead of the physical devices on my machine - any ideas?
|My System Specs|
|08 May 2011||#2|
| || |
At a basic function level, LLTD(Link-Layer Topology Discovery) gives users a graphical representation of their home network topology. In addition to the network map, LLTD offers network device manufacturers a standard way of ensuring that their devices are easily viewed and accessible to their users. Windows Vista enables the Network Map by default when a user is in a location designated as “Home.” However, LLTD and, therefore, the Network Map are both disabled by default in “Work” and “Public” locations.
You will receive a message inside the Network Map (Control Panel -> Network and Sharing Center -> Network Map) if the map is disabled. As long as your network policy (group policy) does not prohibit it, enabling the Network Map on a local machine is simply a matter of enabling the right setting in the local computer policy. “Network mapping is disabled by default on domain networks. Your network administrator can use Group Policy to enable mapping.”
Beyond offering users the convenience of having a visual representation and providing right-click access to information about the devices, the LLTD Responder also plays an important role in responding to, and taking part in, network diagnostics. LLTD helps to make distributed and coordinated network diagnostics possible, and if you are creating home network devices, you should strongly consider implementing an LLTD responder.
(source Link-Layer Topology Discovery Mapper I/O Driver and Responder)
And on your second issue, I guess I'm a bit confused as to what you mean by "master browser".
|My System Specs|
|Similar help and support threads for2: What protocols/services/clients for networking?|
|Services - Restore Default Services in Windows 7||Tutorials|
|Services utility to toggle and restore/enable disable services||Software|
|Remote Desktop (TCP-In) Properties Protocols and Ports tab grayed out||System Security|
|Services, Protocols and clients||Network & Sharing|
|Internet Printing Protocols and Windows 7||Network & Sharing|
|Can't Enable Protocols & Clients!||Network & Sharing|
|Messed Up IPv4 And IPv6 Protocols||Network & Sharing|
|Our Sites ||Site Links ||About Us ||Find Us |
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.
© Designer Media Ltd
All times are GMT -5. The time now is 05:52 PM.