Link Layer Topology Discovery driver on Windows 2003

Posted on August 16th, 2008 in Server 2003, Vista by alt-92

Vista (and Server 2008) introduced the Network Map feature ( as discussed here ).

This feature shows you a Diagram with all LLTD-capable hosts in your home network and you can start it from the Network and Sharing Center Control Panel applet by clicking View Full Map:

Your Network Map would look something like this:

Now, only Vista has this on by default, and the only other Windows version for which LLTD is available is XP.

Shuttle is a WIndows XP MCE2005 machine and has the LLTD Responder installed as provided from MSKB article 922120 (Validation is required to get the download).

My network however also features some 2003 Servers, how do we get these to show?
Installing the driver on Windows 2003 Server does not work, since the updater checks your Windows buildnumber. The update_SP2QFE.inf and update_SP2GDR.inf files contain this entry:

[Version]
Signature = "$Windows NT$"
LanguageType = %LangTypeValue%
NtBuildToUpdate = 2600
NtMajorVersionToUpdate = 5
NtMinorVersionToUpdate = 1
MaxNtBuildToUpdate = 2600
MaxNtMajorVersionToUpdate = 5
MaxNtMinorVersionToUpdate = 1
MinNtServicePackVersion = 512
MaxNtServicePackVersion = 512
ThisServicePackVersion = 512
CatalogFile = %SP_SHORT_TITLE%.cat

Editing the MaxNtMinorVersionToUpdate to 2 (NT 5.2 meaning 2003 Server) might seem like an option, but this invalidates the signature with which all Microsoft updates are signed to prevent tampering.

Turns out there is a very simple way to install the LLTD responder.
First, extract the hotfix to a directory:

.\WindowsXP-KB922120-v5-x86-ENU.exe /X:D:\temp\kb922120

Move the files into your preferred location. In my case, I’m using a DFS network share for AD software deployments.
Create a batchfile, vbscript or whatever you like, and let it perform the following actions:

copy "\\yourserver\appinstall\lltd_2k3\SP2QFE\rspndr.sys" %windir%\system32\drivers
copy "\\yourserver\appinstall\lltd_2k3\SP2QFE\rspndr.exe" %windir%\system32
copy "\\yourserver\appinstall\lltd_2k3\SP2QFE\ip\rspndr.inf" %windir%\inf
start %windir%\system32\rspndr.exe -i
exit

This obviously copies the files in their corresponding target locations and then starts the Responder Service.
Deploy the files in the way that suits you best,

Now, check your Network Map again and you will see your Windows 2003 Server:

And since the Responder can be started and stopped as a regular Service, you can influence the behaviour from whatever mechanism you prefer (MOM Tasks, startup/logon scripts, SMS, System Center) .

Note:
If you’re using VMware products, and both Host and Guest OS have the Responder installed, you’ll notice that VMware Bridging is represented as a Network Hub connection.

Comments are closed.