groovynoob

I’m a senior network engineer.. and like it or not.. network management is forcing me to put on both a dba and amicrosoft hat.. needless to say im a little out of my element.. but i can research.. and i can usually figure out what i need to do. This issue however has completely stumped me. I was hoping someone here might have some insight.. I will explain the scenario as best as i can.. if you have questions just ask.. I will be following this post with great hope of a solution.. ok here we go. Platform: HP G4 DL360 MS Server 2003 R2 64 / 4GB Mem This server is a monitoring station. It is currently monitoring our production network as well as one un routed backup network. We recently added two new networks that are also not routed on our production network. These two new networks are actually our guest wireless and vendor wireless environments. Background: When we were monitoring just two networks.. (Production and Backup) there were no issues. I understand now the reason why there was no issue with the source address used and the backup network is because it is actually layer 2. So its not really using the source IP. The purpose of monitoring the two wireless environments is to be able to validate the infrastucture out to the internet. Each interface is DHCP and successfully obtains an IP address from their designated NAC's. a static route was created to direct traffic destined for the primary DNS to the first wireless network interface. a static route was created to direct traffic destined for the secondary DNS to the second netowrk interface. HERE IS THE ISSUE: A trace route executed on the server to either of the designated DNS servers will be directed to the correct interface but it will use the source IP of the primary interface (the production interface) The production network is not known in the wireless environment and this is for security reasons. So when the traffic arrives at the gateway in the wireless environemnt it is dropped. I was not familiar with this binding functionality in microsoft.. I would have assumed traffic exiting an interface would naturally be bound to that interfaces IP. This is clearly not the case by default.. Is there a way to enable this functionality? The server has no routing.. This is for security reasons.. So all 4 interfaces are connected to 4 seperate networks that do not need to know about eachother.. Traffic going out an a giving interface needs to source its IP address from the interface its exiting. I look forward to hearing what you guys have to say!