TCP/IP interface metric issue

Question

There is a common issue at the company I work at has had recently. The issue begins when we move an associate to work using our new VPN solution and then the interface metric of that VPN's TAP adapter matches the interface metric of their wired ethernet connection and thus the computer ignores the VPN connection's access it should have when being VPN'ed into the company network.

We resolve this by forcing their TAP adapter to have interface metric of 1.

This has worked for everybody until recently, and I have one user that whenever he restarts his Surface Pro 4 that his interface metric reverts back to 25, which is also the automatic setting.

I have tried to make this setting change multiple ways, through Windows, through regedit, and through command prompt. No matter the method, still reverts on restart.

Then I thought maybe this was because of a group policy, but I have tried making this same change and restarting another user with same group policy as him and for that user the setting stuck just fine.

Also an FYI I have tried changing the interface metric for the actual ethernet connect to 35 and leave the TAP adapter at 25, but seems like that ALSO revert back to 25 on restart.

Thanks for looking into this.

Reply 0 people have the same question Edit | Subscribe

Answer 1

Hi,

Did you use third-party VPN client or windows build-in VPN client? Based on your description, it seems something prevent modify.

Try to perform a clean boot and change interface metric, then restart the machine in clean boot see whether the issue still occurs. This can narrow whether the symptom is related with third-party service.

Best Regards,
Candy

--------------------------------------------------------------

If the Answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.