netsh bridge issue

  • Thread starter Thread starter Bilou
  • Start date Start date
B

Bilou

When i try the command:
netsh bridge show adapter
error message is returned:
The following command was not found: bridge show adapter.

My bridge is successfully built from the GUI.

After searching this newsgroup, i found some infos as described below:
IP Router Monitor Library


In addition to:


Network Command Shell
Network Command Shell Interface Context


Should be added to your run-time. These three components should
enable the
netsh functionality you require. At the command line, type:


netsh ?


To list the available contexts. If you require additional contexts,
add
these components as well: Home Networking Monitory Library, Network
Diagnostics, Remote Access Monitory to add support for bridge, diag,
and
ras, respectivley.
Click to expand...

As i can't ask the thin client OEM manufacturer to rebuild a runtime
image for me, can someone help me and check what are the binaries and
registry entries listed in 'Home Networking Monitory Library'
component in Designer Studio.

I can then export registry entries and copy binaries from regular
Windows XP Professional installation and inject them to my thin client
runtime image.

If somebody experimented before the same issue, can he give me some
hints how to solve it?
 
When i try the command:
netsh bridge show adapter
error message is returned:
The following command was not found: bridge show adapter.

My bridge is successfully built from the GUI.

After searching this newsgroup, i found some infos as described below:
IP Router Monitor Library

In addition to:

Network Command Shell
Network Command Shell Interface Context

Should be added to your run-time. These three components should
enable the
netsh functionality you require. At the command line, type:

netsh ?

To list the available contexts. If you require additional contexts,
add
these components as well: Home Networking Monitory Library, Network
Diagnostics, Remote Access Monitory to add support for bridge, diag,
and
ras, respectivley.
Click to expand...

As i can't ask the thin client OEM manufacturer to rebuild a runtime
image for me, can someone help me and check what are the binaries and
registry entries listed in 'Home Networking Monitory Library'
component in Designer Studio.

I can then export registry entries and copy binaries from regular
Windows XP Professional installation and inject them to my thin client
runtime image.

If somebody experimented before the same issue, can he give me some
hints how to solve it?
Click to expand...

Auto answer to my question:

Name: Home Networking Monitory Library
Description: Netsh helper for Homenet components - support the bridge
context.
Files: hnetmon.dll
Registry: "HKLM\SOFTWARE\Microsoft\NetSh" /v "hnetmon.dll" /t REG_SZ /
d "hnetmon.dll"

for reference only:

Name: Network Command Shell
Description: NetSh shell for command line administration.
Files: netsh.exe
Registry: "HKLM\SOFTWARE\Microsoft\NetSh"

Name: Network Command Shell Interface Context
Description: NetSh helper for interface context.
Files: ifmon.dll
Registry: "HKLM\SOFTWARE\Microsoft\NetSh"

Name: Local Network Bridge
Description: Layer Two Ethernet, and IP Bridge
File: bridge.sys
 
Back
Top