Article ID: 103275 - Last Review: November 1, 2006 - Revision: 2.1 How to Find Lana Numbers for Applications
This article was previously published under Q103275 SUMMARY
Microsoft LAN Manager redirector uses a NetBIOS interface to
communicate with lower-level transport protocols (that is, NBF, TCP).
NetBIOS requires that the redirector provide a LAN adapter (Lana)
number to identify a unique combination of one protocol driver and one
network adapter (NIC) MAC driver. For each protocol and network card,
there is exactly one unique Lana number. In Windows NT, Lana numbers
are not important to the redirector because the Windows NT redirector
uses TDI (Transport Device Interface) to communicate with the
lower-level transports.
Although TDI does not require Lana numbers, they are still important to other NetBIOS-based applications running in Windows NT. These applications submit NetBIOS commands called NetBIOS Command Blocks (NCBs). The NCB structure contains a field called Lana Number that must be filled in with the unique number (that is, the protocol/MAC pair) of the network where the destination computer is located. MORE INFORMATION
For more information on NetBIOS, see the IBM Local Area Network
Technical Reference.
To see the NetBIOS Interface dialog box (which includes a box that details the Network Route and Lana number associated with the particular network), choose the Networks icon in Control Panel, choose the Add Software button, select NetBIOS Interface, choose Continue, and choose Configure. Any changes you make in the NetBIOS Interface dialog box, will appear in the Registry under the following key:
=================================================================
SYSTEM\CurrentControlSet\Services\NETBIOSInformation\parameters
=================================================================
LanaNum1 0x2
LanaNum2 0x3
LanaNum3 0x4
LanaNum4 0x5
LanaNum5 0x1
LanaNum6 0
ROUTE
"Nbf" "RasHub" "RasHub04"
"Nbt" "Streams"
"NWNBLINK" "Streams"
"Nbf" "RasHub" "RasHub05"
"Nbf" "Elnk16" "Elnk1601"
"Ubnb" "Streams"
You can also obtain the order of Lana numbers from the following Registry key:
=================================================================
SYSTEM\CurrentControlSet\Services\NETBIOS\linkage
=================================================================
BIND
\Device\Streams\NWNBLINK
\Device\Streams\Ubnb
\Device\Streams\NBT
\Device\Nbf_Elnk1601
\Device\Nbf_RasHub04
\Device\Nbf_RasHub05
EXPORT
\Device\Netbios\Streams\NWNBLINK
\Device\Netbios\Streams\Ubnb
\Device\Netbios\Streams\NBT
\Device\Netbios\Nbf_Elnk1601
\Device\Netbios\Nbf_RasHub04
\Device\Netbios\Nbf_RasHub05
LanaMap
010401000103010101020105
ROUTE
"NWNBLINK" "Streams"
"Ubnb" "Streams"
"Nbt" "Streams"
"Nbf" "Elnk16" "Elnk1601"
"Nbf" "RasHub" "RasHub04"
"Nbf" "RasHub" "RasHub05"
01 04 - 01 00 - 01 03 - 01 01 - 01 02 - 01 05 From this information you can determine that:
"NWNBLINK" "Streams" is Lana number 04
To see a list of the NetBIOS interface bindings, choose the Network
icon in Control Panel, choose Bindings, select NetBIOS Interface, and
choose Show Bindings For. If you use the arrow keys to manipulate the
order of the bindings, you actually manipulate the BIND, EXPORT, and
ROUTE order in the Registry.
"Ubnb" "Streams" is Lana number 00 "Nbt" "Streams" is Lana number 03 "Nbf" "Elnk16" "Elnk1601" is Lana number 01 "Nbf" "RasHub" "RasHub04" is Lana number 02 "Nbf" "RasHub" "RasHub05" is Lana number 05 For More information on the BIND, EXPORT, and ROUTE parameters, see the DDK or the Resource Kit Registry Help files. NOTE: There is a new NCB command NCBENUM that is supported by the WIN32 API: Enumerate LAN adapter (Lana) numbers. When this value is specified, the NCB_BUFFER member points to a buffer to be filled with a LANA_ENUM structure. | Other Resources Other Support Sites
CommunityArticle Translations |






Windows Live
Facebook
Twitter
Linkedin
Digg it
Yahoo
Delicious
StumbleUpon
Yammer
Reddit
Technorati
FriendFeed
Email
Back to the top