We have had instances in which traffic coming in on the 172.16.1.0 network tried to route back out through the 172.17.1.0 network. That gateway is a firewall, which discards the packets, thus rendering the Web sites unavailable. This only happens approximately once a week.
The question is: How can we configure the server to ensure traffic goes out the NIC it came in on?
The system uses an ordered list of access pathways known as binding. This is performed as follows:
- Open Network and Dial-up Connections.
- Click the connection you want to modify. On the Advanced menu, click Advanced Settings.
- On the Provider Order tab in Network Providers, click the provider you want to move up or down in the list, and then click the up or down button.
Note: To modify the network provider order, you must be logged on as a member of the Administrators group.
Put the interface at the top of the list (i.e. use priority) that is used most often.
Dig Deeper on Windows Server deployment
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.