Thanks for the suggestions guys, but we've just established that it is definately either the router or the bridge. I'm hoping it is the router, since the WET54G doesn't have many configuration options.

The way I can say with confidence it isn't my computer is that another computer on our network is having similar issues.

I didn't realize that my roommate's computers had been running in Linux all weekend, so when I said all the other WinXP Pro boxes connected properly, I was wrong. Everything except WinXP Pro boxes work, but only Wireless LAN to Wired LAN connections die. Wireless to Internet works fine. Wireless to Wireless works fine. Wired to Wired works fine. Only with WinXP Pro. WinXP Home works correctly. Linux works correctly.

I'm guessing that XP Pro has some kind of setting that it doesn't like something about the bridged packets. Especially since you can circumvent the problem by adding a static route to the routing table of the XP Pro box (I successfully connected to the Linux box after making the appropriate route with route -s 192.168.0.8 MASK 255.255.255.255 192.168.0.1).

It could be a legacy from not resetting the routers configurations to default before replacing our old netgear router with it. Before the Linksys WRT54G router was acting as a bridge with out Netgear router. Then when we purchased the WET54G bridge the Netgear was replaced with the WRT54G. I'm thinking some of the settings might be holderovers from the router's repurposing.

I'm going to reflash the WRT54G to the newest Linksys ROM instead of the Sveasoft Alchemy ROM. Hopefully the two Linksys products will automatically play together nicely.

So, I'll post after work tomorrow after I reflash the router and get things re-established.

Thanks again!
Dhej