I wanted to post a difficult issue and solution that I found.
[Wireless Router] ~ ~ ~ [XPPro-d]-[XPPro-f]-[XPPro-e]
These three machines XPPro-d, XPPro-e, XPPro-f are located in a
bedroom converted into an office. They are connected by crossover
CAT-5 (regular, plain-'ol) Ethernet Cable with XPPro-f at the center.
XPPro-d provides connectivity for the room to the rest of the home
network through a DLink DWL-520+ Wireless Ethernet Adapter.
The wireless router is located in a different room, more central to
the rest of the house. All other components of the network (laptops,
stand-alone PCs) connect via wireless to the router.
Issue: When using Windows XP to "bridge connections" between the
wired Ethernet card and the Dlink DWL-520+, the bridge would appear to
be created but no traffic was being passed and the router was not
pingable.
Solution found in a paragraph at
http://www.microsoft.com/windowsxp/e.../02april22.asp
-- which then referred me to the below Knowledge Base article. Hours
of troubleshooting and searching ended.
Note: In order to follow Microsoft's instructions, you need to have
the bridge created (even though it appears inoperative). Otherwise
the 'netsh bridge show adapters' command comes up blank.
http://support.microsoft.com/default...EN-US;Q302348&
Microsoft Knowledge Base Article - 302348
Bridge May Not Work With a Non-Promiscuous Mode Network Adapter
The information in this article applies to:
Microsoft Windows XP Home Edition
Microsoft Windows XP Professional
Microsoft Windows XP 64-Bit Edition
This article was previously published under Q302348
SYMPTOMS
Some network interface cards (NICs) may not work after you try to
create a network bridge. Specifically, the bridge seems to be created
but it does not work (traffic is not passed).
CAUSE
This problem occurs because some NICs do not automatically enter into
Promiscuous mode to create a successful network bridge.
RESOLUTION
To work around this behavior, force the adapter into Compatibility
mode:
At a command prompt, type netsh bridge show adapter.
Locate the identification number of the NIC that is not responding.
If the NIC is not in Compatibility mode, you can change it manually if
you type the following command, where 1 is the number of the NIC that
is displayed in the first step:
netsh bridge set adapter 1 forcecompatmode=enable
Run the netsh bridge show adapter command again to verify that the
ForceCompatabilityMode field for the NIC is displayed as Enabled.
MORE INFORMATION
The following NICs may exhibit this behavior:
Proxim Symphony Cordless PnP ISA card
DWL-120 USB 802.11b
5.8GHz RadioLAN card
Additionally, contact the manufacturer or check their Web site for
more information about possible updates.
The third-party products that are discussed in this article are
manufactured by companies that are independent of Microsoft. Microsoft
makes no warranty, implied or otherwise, regarding the performance or
reliability of these products.
Similar Threads
