This "bridge" nonsense didn't come about until XP and Server 2003, and has
been no end of confusion to people. Win2k, NT, Win9x all worked happily on
various networks long before XP and 2003 came along and they didn't use any
bridging of any kind. These bridging functions are only used for situations
where you actually require bridging to be used,..and it doesn't happen very
often.
Get rid of the bridging and run the network the same way you would if you
were runnig the old NT4.0 or Windows 2000 and everything will work.
--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
"Michael Heier" <(E-Mail Removed)> wrote in message
news:1b6f301c44fc1$cf6fa760$(E-Mail Removed)...
> I am having a problem with my network bridge. I have a
> wireless network connection that is connected to a
> wireless router, and a wired ethernet connection to a hub
> wiht 2 other computers connected to it. I set up the
> bridge and I lose the wireless connection. I read some
> articles saying that it is a problem with promiscuous code
> or something and that I need to force compatibility using
> the "netsh bridge" context. However, there is no bridge
> context available even though the bridge is installed. If
> anyone can help me out, please reply or more preferably
> email me. Thanks.
>
> -Mike Heier ((E-Mail Removed))