Windows 2003 Server Dual-Homed with DHCP, DNS Service on One NIC

I have a Windows 2003 Server Standard RC2 SP1 configured as a member server of a domain.  This server does not handle DNS or DHCP.  However, I enabled a second NIC card on the server and put that in a different subnet/VLAN from the existing NIC.  All I want/need this to do is handle one DHCP scope and DNS for the second NIC's subnet/VLAN.  First I the following message:

"Warning-multiple default gateways are intended to provide redundancy to a
single network (such as an intranet or the internet). They will not function
poperly when the gateways are on two separate, dsjoint networks (such as one
on your intranet and one on the internet). do you want to save this

So I removed the default gateway for the second NIC added and did not get the message.  I made sure that the DHCP scope was bound to the IP address of the second NIC and that DNS is listen on the second NIC as well.  

I cannot get the DHCP server to give out addresses on that subnet.  It is as if the scope doesn't exist.  I have read through some MS TechNet and EE items but can't seem to determine what the issue is.  I will have to sniff a segment to see what the traffic is doing.

Does anyone have any thoughts on this?  They would be much appreciated.  Thank you in advance.  

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.


At the risk of insulting you, did you authorize the DHCP scope and server? The scope is active?


of course it wont, you removed the gateway, it has no idea where to send anything
scrapeitAuthor Commented:
MidnightOne - the scope is authorized.

Jay_Jay70 - I did remove the gateway from the second NIC but that is not the issue.  

Here is what I did to get it working.  The second NIC I enabled happens to a lower numbered NIC than the first NIC which is connected to a subnet/VLAN that is part of an AD domain.  I was reading off of MS TechNet that DHCP will automatically bind or enable itself to the first active NIC it sees so I removed DHCP service and then reinstalled it and it was bound and enabled to the second NIC I activated.  It seems that I could not just changed the DHCP bindings alone.  After a server reboot, I was able to get DHCP working without an issue.  

Now if this is another question, I will post it but what should the exact configuration be for gateways on both NIC cards in this scenario.  Presently as I stated above it is working without a gateway configured on the second NIC that is serving DHCP and DNS only.  I assume this is working because the primary NIC is sending the traffic it needs to its connected subnet/VLAN but the second NIC is only serving DHCP and DNS only so it does not necessarily need a gateway address.

Anyway if anyone has any thoughts on this, I would appreciate it.  Even though it is now working I just want to make sure this is a good practice.  Or do I just ignore the multiple default gateway error message.  Thanks.


PAQed with points refunded (500)

Community Support Moderator

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.