How Windows Creates the Network Map

Windows creates the Network Map in part by using the Link Layer Topology Discovery (LLTD) protocol. As the name suggests, LLTD functions at Layer 2 (the layer devices use to communicate on a LAN) and enables network devices to identify each other, learn about the network (including bandwidth capabilities), and establish communications (even if devices are not yet configured with IP addresses). Typically, you do not need to manage LLTD directly. However, you can configure two Group Policy settings located within Computer Configuration\Policies\Administrative Templates\Network \Link Layer Topology Discovery:

• Turn on Responder (RSPNDR) Driver This setting enables computers to be discovered on a network and to participate in Quality of Service (QoS) activities, such as bandwidth estimation and network health analysis. You can choose to enable the responder driver while connected to networks of the domain, public, or private location type. Windows enables the responder driver for all networks by default.
• Turn on Mapper I/O (LLTDIO) Driver This setting enables a computer to discover the topology of the local network and to initiate QoS requests. You can choose to enable the mapper driver while connected to networks of the domain, public, or private location type. This option is enabled for all networks by default. Windows enables the mapper driver for all networks by default.

Figure below illustrates how the LLTD responder and mapper relate to other networking components.

Note Windows Vista and Windows 7 include an LLTD responder, but earlier versions of Windows do not. To find out how to download an LLTD responder that you can add to Windows XP, read Microsoft Knowledge Base article 992120 at http://support.microsoft.com/kb/922120. This will enable computers running Windows XP to appear on the Network Maps in Windows 7, but they still cannot generate the maps.

LLTD is not a secure protocol, and there is no guarantee that the Network Map is accurate. It is possible for devices on the network to send false announcements, adding bogus items to the map.

Because each user can have his own set of network profiles, Windows creates Network Maps on a per-user basis. For each network profile that a user creates, Windows actually generates two maps: the current map and a copy of the last functional map (similar to the Last Known Good recovery option). When displaying the Network Map to the user, Windows combines these two maps.