I have a laptop running Windows XP SP3 with a wireless NIC and a wired NIC. I bridge the two network connections under Windows\Control Panel\Network Connections. This gives me a single bridged network connection. DHCP is enabled on this bridged connection and everything functions as expected on the laptop as though I had a single wireless DHCP enabled connection.
I want to connect a desktop PC with only a wired NIC to the same network as the laptop. It appears that I wrongly assumed that the Windows Bridging feature would act as basic layer two switching device with the added function of translating from wireless to wired. The first thing I tried to do was attach the desktop PC to the laptop with DHCP enabled on the desktop PC. But when I try this I get an IP conflict on both the laptop and the desktop PC. Why doesn't this work?
The only way I can get the desktop PC to access the network correctly (with this particular setup) is to manually configure the IP address of the desktop PC. Why does this work but enabling DHCP doesn't?
This may or may not be relevant but to get the bridge working at all I had to force the wireless NIC into 'promiscuous mode' as described in this article.
Someone did mention (on another site) that it might be something to do with MAC address masquerading. But why would MAC masquerading be implemented by the bridge? And if this is the case how can it be turned off?