Fixing 169.254.x.x problem with network bridge

You may get 169.254.x.x because of the Automatic Private IP Address (APIPA) feature of windows. The windows OS may assign a private IP if the network card is setup to get IP from a DHCP server and is not able to do so. This can be a generic problem and the solution will be specific to the problem. The above info should give you some pointer to explore further. One of the most common problems is that a firewall on you machine may be preventing your machine from getting the IP from the DHCP server.

The problem that we are going to solve today is when this problem may happen because of network bridge. A network bridge is typically used to share the internet between two network devices. One of it could be a wireless device and the other a wired device. The exact problem that I am facing is as follows:

I have a network bridge between my wireless device and my ethernet card. When I connect to internet using LAN cable between the ethernet port of my PC and router, I could share the internet on my LAN with the devices connected to my wireless. Also, if I do not have the network bridge, I can connect to the internet over my wireless. But while having the network bridge, if I try to connect to the internet over wireless, I am not able to do so. I get the 169.254.x.x IP which is not in the range of my router's IP. The fix is as follows:

1. Open the command window (from Run->cmd.exe or programs)
2. Issue the command "netsh bridge show adapter"
3. See the id of the adapter that is not working
4. If the "compatibility mode" is not enabled, you should force it
5. Issue the command "netsh bridge set adapter id forcecompatmode=enable" (Replace "id" with the number of adapter id)
6. Run the command "netsh bridge show adapter" and verify that it is enabled.
7. Issue the command "ipconfig /renew" to renew the IP and then issue "ipconfig".
8. You should see an IP that is in the range of your router's IP address.
9. Enjoy!

Source: Microsoft Knowledgebase