overflow Posted January 31, 2007 Report Share Posted January 31, 2007 Hi.I Need to divide a busy network to improve user responsiveness.The network has three servers and a bunch of PCs all sharing the same set of switches. We've identified that around 30% of the network traffic is server-to-server. A large number of Terminal Services sessions is partly responsible for this.What I want to do is give the servers their own channel on a private subnet using a second NIC in each server.I'm quite happy about the TCP/IP network aspects of this. What I'm not sure about is making sure that things like Active Directory don't get upset, while making sure the most is made of this private backbone.We have a starting point something like:SERVER1 - 10.0.0.1SERVER2 - 10.0.0.2SERVER3 - 10.0.0.3PCs - 10.0.0.xxxAfter the change, we'll have:SERVER1 - 10.0.0.1 & 10.0.1.1SERVER2 - 10.0.0.2 & 10.0.1.2SERVER3 - 10.0.0.3 & 10.0.1.3PCs - 10.0.0.xxxWhere the 10.0.1.x subnet is only shared between the servers on a dedicated switch.The problem I have is how to set up the DNS and Active Directory. DNS is shared with the rest of the network. I want the servers know to use the 10.0.1.x addresses between each other but the PCs still use 10.0.0.x to access the servers. I'm conscious of the importance of a properly configured DNS for Active Directory to work smoothly.Any help much appreciated.Thanks. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.