Start Updating a file using random access

Updating a file using random access

There are several Windows Server components contributing to make this work.

A typical case would be a small company where you have the first floor clients using one NIC and the second floor using the other. However, keep in mind that this configuration won’t give your clients a dual path to the File Server.

While both of the IP addresses get published to DNS (assuming everything is configured correctly) and each of the SMB clients will learn of both, only one of them will be routable from a specific client. Each set of clients has only one way to get to the server.

Throughout this blog post, we will look into different configurations for Windows Server 2008 (and 2008 R2) where a file server uses multiple NICs.

Next, we’ll describe how the behavior of the SMB client can help distribute the load for a file server with multiple NICs.

This is useful to give you additional overall throughput, since you get traffic coming into both NICs.

However, in this case, you are using different subnets.

These solutions, providers by vendors like Intel, Broadcom and HP, effectively combine multiple physical NICs into one logical or virtual NIC.

The details vary based on the specific solution, but most will provide an increase of throughput and also tolerance to the failure of a NIC or to a network cable being accidentally unplugged.

The SMB client will then be able to query DNS for the file server name, find that it has multiple IP addresses and choose one of them.

Due to DNS round robin, chances are the clients will be spread across the NICs on the file server.

When RSS is not available, a single CPU services all the interrupts from a network adapter.