Router Behind Bridge

Archived from groups: microsoft.public.windowsxp.general (More info?)

Hello,

I have two networks. For simplicity sake lets call the 10.10.10.0/24 subnet
"Site A" and the other is on the 192.168.0.0/24 subnet "Site B".

-On Site A, I have a managed procurve 2524 switch, and a Windows XP SP2
Bridge.
-On the bridge there is 1 Ethernet Network Card and 1 Wireless 802.11g card
which are bridged together in the network connections control panel
-The wireless card is connected to the Site B subnet
-The NIC is connected to the "Site B" VLAN (This is a VLAN that I defined on
the Procurve Switch)


The problem that I am having is that if a user on "Site A" plugs their
computer into a port which is defined on "VLAN SITE B" of the Procurve
Switch, data would NOT route through the router on "Site B", which is
192.168.0.1. The user CAN get their IP Addresses from the router on "Site
B", browse computers and network shares in My Network Places, however, once
they are connected to the "VLAN SITE B" of the switch at "Site A" . They can
even ping 192.168.0.1 (the router) and everything on "SITE B"! But not route
through the router. I am stumped! Any tracert commands like "tracert
google.com" would time out on the first hop. It won't even try to go to
192.168.0.1.

The only solution that I have to allow users to route to 192.168.0.1 on
"Site A" is to give the Bridge an IP address like e.g. 192.168.0.2 /
255.255.255.0 / 192.168.0.1. With that done users can route through
192.168.0.1 from Site A. However there is also another subnet on Site B
where the router is 192.168.0.3. If I add a static route to a client on Site
A connected to the site B VLAN e.g. "route add 10.0.0.0 mask 255.255.255.0
192.168.0.3" the same thing happens, it won't route through 192.168.0.3,
even though its pingable, it would die at the first hop (no response at the
first hop). Tracert looks like "1. * * * Request timed out".

Why is the bridge doing this? I thought Windows XP's bridging feature was
PURE Layer 2, which would integrate seamlessly with the switches, but it
turns out that I must add IP addresses and default gateways onto the bridge
to let traffic route through it if the router is on the other side of the
bridge? This is not a solution since there are 2 gateways on site B. One
routing to the internet (192.168.0.1) and another one routing to another
private network (192.168.0.3).

Is there anyway around this?


-Thank You for your time