• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

DHCP in Microsoft Server 2k3

B

beatmix01

Golden Member
Here is my issue.

My server has dual nics with the following IP addresses.

x.x.x.50
x.x.x.51

However, no matter what, when I install the DHCP component it always sets the server to x.x.x.51. The main DHCP server IP is supposed to be the .50 IP

Does anyone have any ideas?
 
Are both NIC's active? If so why? Is it multi-homed, if so the IP's seem to be on the same segment.
 
First question why are both nics in the same network? I will preface my suggestion with the usual This may not help may break your network yada yada.

open up your network connections right click the lan you want to be primary
1. goto properties
2. Goto TCP/IP then click Properties
3. Click advanced
4. at the bottom uncheck automatic metric and place a 10 in there

Now do the same for the one you want to be backup except make the metric 20.

Thanks,
W0ss
 
The easy way?

Start your DHCP. Disable your x.x.x.51 NIC. Hit refresh in the DHCP window a few times. DHCP will automatically switch over to the other IP. After it has, re-enable your x.x.x.51 NIC. It will stay on the other IP.

I'm sure there are nicer ways to do it, but that method has worked for me every time.
 
I agree. Eliminate the dual NICs. They're on the same network which kinda breaks all kinds of networking rules.

If you want dual network cards use some kind of driver teaming - that way the OS only "sees" a single interface and the driver takes care of the load-balancing/redundancy.

Windows HATES having more than one network card.
 
Windows doesn't necessarily hate multiple NICs. If it's a DC, its not a good idea. In this case, I don't see that two NICs are needed, but there are two possibilities here. You may need to change the binding order (right click on network neighborhood, properties, advanced menu, advanced settings), or bind DHCP to a different IP (DHCP console, right click on the server, properties, advanced tab, bindings).
 
I originally had my SBS2003 server setup as a DHCP with ISA server. The network performance was very poor compared to just using a router as the DHCP. What benefit are you trying to get over using a router?
 
I've never seen an increase or decrease in performace using a router compared to a server for DHCP. It takes practically no CPU power to do it. I use my server so that I can keep track of IP leases easily right there in windows; it also allows for sending more info like time servers, WINS servers, etc with the DHCP when you use the server version. Routers do basic stuff and that's all.
 
My decrease in network performance may have been one or more of a number of things. I only had 256 Ram on it at the time. I also may not have had ISA configured right. ISA is a pain to get right. So, that could have been my problem. But, I think its easier for newer people to just use the router. My router does everything I was going to use SBS2003 for as a DHCP.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top