Networking Windows Server 2003

How to Set Your Dual LAN Workstation to Use Separate Internet Connections with Windows Server 2003

When you’re working with a dual LAN workstation, it can sometimes be a challenge to manage how your system uses these connections—especially when each network serves different purposes. For instance, if you have a workstation connected to both a 10.17.x.x network and a 10.16.x.x network, you might need to configure it in such a way that minimizes bandwidth use on one network while maximizing access on the other. In today’s blog post, we’ll explore how to set up a Windows Server 2003 machine to use the most efficient connection for both internal tasks and external internet traffic.

The Problem

In your scenario, you have two LAN connections:

10.17.x.x: This connection is configured for external traffic.
10.16.x.x: This connection is primarily for internal communication and should not bear the load of internet traffic.

You would like to ensure that your Windows Server 2003 machine effectively uses the 10.17.x.x connection for all external traffic while reserving the 10.16.x.x connection strictly for local network communications.

The Solution: Configuring Your Routing

To achieve this setup, you’ll use the route command in Windows to define how your system treats network connections. Below are several steps to guide you through this process.

Step 1: Add a Default Route

You need to set the 10.17.x.x network as your default route for all external traffic. Open the Command Prompt and execute the following command:

route add 0.0.0.0 MASK 0.0.0.0 <address of gateway on 10.17.x.x net>

Explanation: This command directs all traffic not specifically routed through another interface to the gateway of your 10.17.x.x network.

Step 2: Adjust the Route Metric

Route metrics determine the priority of routes. If there are multiple routes available for data packets, the system will choose the one with the lowest metric. To ensure your new route takes precedence:

Add a Metric: Modify the command to specify the metric at the end. For example:
```
route add 0.0.0.0 MASK 0.0.0.0 <address of gateway on 10.17.x.x net> METRIC 1
```
- Note: Using a metric of 1 gives this route the highest priority.

Step 3: Adjust TCP/IP Settings (Optional)

As an alternative to configuring metrics via the command line, you can also adjust the network settings in the Windows interface:

Go to Network Connections.
Right-click the connection for the 10.17.x.x network and choose Properties.
Select Internet Protocol (TCP/IP) and click Properties.
Click on the Advanced button.
Untick the Automatic Metric checkbox and set the value to 1 or 2.

What If I Encounter Issues?

It’s not uncommon to run into complications when manipulating routes. If the changes do not seem to take effect:

Ensure you remove any conflicting routes. Use:
```
route delete <IP-address>
```
Confirm that your route to the 10.17.x.x network is still active and correctly configured.

Conclusion

Configuring a dual LAN setup effectively can significantly improve network efficiency, especially in environments where you have separate needs for internal and external traffic. By following these steps, you can ensure that your Windows Server 2003 machine utilizes its connections appropriately, saving bandwidth on the 10.16.x.x network and streamlining internet traffic through the 10.17.x.x connection.

If you’re still having trouble or need more sophisticated control over your network, consider researching dedicated networking software that can help manage your routes more easily.

By following this guide, you should be equipped to optimize your dual LAN workstation successfully. Happy networking!