[SOLVED] ForceBindIP usage on chrome ver. 86+

Solution
I am not [full disclosure] a Chrome user per se.

However for most users their computer is setup/configured to use either a wired or wireless network connection.

Meaning that only one network adapter (either wired or wireless) is enabled at a time. Not both.

Exception being some requirement for bridging.

Run "ipconfig /all" (without quotes) via the Command Prompt and post the results.

ForceBindIP may have been doing the network adapter change for you.

You may now need to manually make the change. My first thought was Powershell so I started looking for cmdlets and scripts.

Found the following link:

https://www.tenforums.com/tutorials/106397-enable-disable-network-adapters-windows.html

Fortunately it appears that...
As I understand your post you wish to have Chrome use a specific IP address.

The provided ForceBindIP link is not dated but the last shown version date is about 3 1/2 years ago.

Are you able to explain more about your environment and requirements?

There may be other options available in lieu of ForceBindIP.
 
I have ethernet cable connected with Wifi network togeather. My wifi connections is set as primary via metrics. I need Chrome browser to use ethernet connection. I used ForceBindIP software for it before. But after chrome updated to newer version it stopped working. One step when setting it up is to swith #network-service-in-process in chrome to enabled. But that option is missing now in newer version.
So my question is, is there some way to do this now ?
 
I am not [full disclosure] a Chrome user per se.

However for most users their computer is setup/configured to use either a wired or wireless network connection.

Meaning that only one network adapter (either wired or wireless) is enabled at a time. Not both.

Exception being some requirement for bridging.

Run "ipconfig /all" (without quotes) via the Command Prompt and post the results.

ForceBindIP may have been doing the network adapter change for you.

You may now need to manually make the change. My first thought was Powershell so I started looking for cmdlets and scripts.

Found the following link:

https://www.tenforums.com/tutorials/106397-enable-disable-network-adapters-windows.html

Fortunately it appears that you have multiple options to manually change the adapter to be used.

And Option 5 seems to fit right in.

However, there may be true Chrome user who knows how or has discovered how to make Chrome do the work again.

Thus there may be other ideas and suggestions.
 
Solution
I am not [full disclosure] a Chrome user per se.

However for most users their computer is setup/configured to use either a wired or wireless network connection.

Meaning that only one network adapter (either wired or wireless) is enabled at a time. Not both.

Exception being some requirement for bridging.

Run "ipconfig /all" (without quotes) via the Command Prompt and post the results.

ForceBindIP may have been doing the network adapter change for you.

You may now need to manually make the change. My first thought was Powershell so I started looking for cmdlets and scripts.

Found the following link:

https://www.tenforums.com/tutorials/106397-enable-disable-network-adapters-windows.html

Fortunately it appears that you have multiple options to manually change the adapter to be used.

And Option 5 seems to fit right in.

However, there may be true Chrome user who knows how or has discovered how to make Chrome do the work again.

Thus there may be other ideas and suggestions.

Hi,
Well the thing is, ForceBindIP Actually enables you to use multiple network adapters at the same time. What wasshup wants to do is to use one adapter to browse in chrome and the other one to use another app.
 
Interesting....

Not going to question the requirements per se but I do wonder why.

I just open Edge to do what I need to do and then maybe open Firefox for some other purpose. I have never had the need for two network adapters...

Will defer to Chrome and/or ForceBindIP users who have worked with such configurations.
 
Not sure they fixed this. Forcebindip gets broken all the time because it is old software. Not sure why nobody works to update this. I know I stopped using it when the 64bit issues came up in win10 years ago.

Your problem is chrome does not use a single process anymore to improve performance. I have seen the dll stuff but that also tends to sometime break chrome.

This is one of those things you get when you run unsupoprted software. Chrome is updated almost constantly and someone needs to update forcebindip.

From what I can tell there must be very little interest in this. I know I just use the route command but that is use to direct traffic by destination not the source program the initiated it. Maybe you could use the proxy settings in chrome to somehow force the traffic. You might be able to load the proxy on the same machine and then use forcebind on the proxy. process. Then again it might just be easier to use something like a raspberry pi as the proxy on the actual network.
 
  • Like
Reactions: aliesfehani

Latest posts