Below you can find some (older) IT and Security-related remarks, tips & tricks:

In this article I'll try to give you an idea how to force the system to use a determined network adapter for accessing the web (in case your browser gets confused when two or more adapters are enabled and throws a network / internet connection error, making the access to the WWW impossible).

This example shows the procedure of binding a Wi-Fi adapter to be used as a primary adapter for browsing purposes.

In other words, if you're not satisfied with the ForceBindIP's results, you can always edit the routing table by:

1. using the built-in route command
2. using a GUI tool like NetRouteView

In order to alter the table by using the built-in CLI tool (i.e. the route command), do the following:

1. raise an elevated command prompt (run cmd with the "Run as Administrator" option)

2. to take a look at the routing table in use, issue the route print command - the output should look like this (notice the interface number in the upper left corner!):
3. now it's time to check the IP4 Default Gateway (in the Network Connection Details, like shown below)                                                                                                          
4. in order not to get a duplicate values in the table, delete the existing route by issuing route delete 0.0.0.0 if <number of the interface you want to use>
5. go back to the command prompt and issue the following command: route -p add 0.0.0.0 mask 0.0.0.0 <ip of the gateway> metric 1 if <number of the interface you want to use> (you should get an "OK!" after running the command). The "-p" switch makes the change permanent (the route shouldn't be lost after the restart or reset), and the lower the metric value - the higher the affinity of the system to use this route for accessing the named address (the more preferred it would be for the purpose selected).
   
6. issue the route print command again to check the results- it should something like this now (notice the values marked in yellow - these are the actual changes):
7. check the connection by using your browser.

Except from the traditional (built-in) Microsoft CLI tool (invoked by issuing the route or more commonly the route print command), there's also a free GUI solution available under the name NetRouteView (just scroll to the end of the page to get to a download link).

I won't get into the details here (in the end, I find the tool very easy to use and there's a good explanation by the author himself) - however, this is how the routing table altered above looks in the same tool:

If you want to modify the route, just right-click on it and enter the values (the principle is same as above, mentioned in the method A) - and remember to make the change persistent by selecting "Yes" in the dropdown list at the bottom of the windows.