I generally endeavor to centralize the DHCP unless the WAN is REALLY, REALLY 
bad. It's also pretty resilient - you've got a full lease time before you need 
to check back in with DHCP and it starts trying automatically 50% through the 
lease.

Static IPs seems like a management nightmare to me. Just stand up DHCP in the 
hub and set the ip helper address on the routers.

From: Malcolm Reitz [mailto:[email protected]]
Sent: Wednesday, November 18, 2009 12:34 PM
To: NT System Admin Issues
Subject: RE: Multi-Site thoughts

+1 on this. We occasionally use a remote site's router to supply DHCP to the 
site, but it is far easier to manage with the centralized DHCP server as Jason 
describes. DHCP is very lightweight traffic, so there are no real bandwidth 
concerns, either.

-Malcolm

From: Jason Morris [mailto:[email protected]]
Sent: Wednesday, November 18, 2009 9:52 AM
To: NT System Admin Issues
Subject: RE: Multi-Site thoughts

If all the data is hosted in one location and the link goes down, there's no 
reason for the other sites to have network addresses then, right? In that case, 
just use an ip-helper address from the remote sites and manage dhcp on one 
server at the main site.

That's what I'd do.
Jason

From: Cesare' A. Ramos [mailto:[email protected]]
Sent: Wednesday, November 18, 2009 9:47 AM
To: NT System Admin Issues
Subject: Multi-Site thoughts

Hellos.

Wanted to bounce something off the group to get some thoughts.

We have a client that has 5 sites and a main / corp site.  Currently they have 
local file / printer servers at each site that are also hosting local DHCP.  We 
have recently implemented 100MB meshed metroe among all sites and they now want 
to remove all servers from the remote sites.

We have no concerns from a data perspective but where we have been bouncing 
back and force is as to the DHCP for the remote site systems.  Each remote site 
is about 5 to 10 users, so we are leaning towards static IPs to minimize 
complexity from use of an appliance or something for DHCP.

What do you guys think?

CAR

________________________________
This e-Mail and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed. If 
you have received this e-Mail in error please notify the sender via returned 
e-Mail. Please note that any views or opinions presented in this e-Mail are 
solely those of the author and do not necessarily represent those of the 
company. Although IDF operates anti-virus programs, it does not accept 
responsibility for any damage whatsoever that is caused by viruses being passed.

** Think before you print this message. **









------------------------------------------------------------------------------------------

The pages accompanying this email transmission contain information from MJMC, 
Inc., which

is confidential and/or privileged. The information is to be for the use of the 
individual

or entity named on this cover sheet. If you are not the intended recipient, you 
are

hereby notified that any disclosure, dissemination, distribution, or copying of 
this

communication is strictly prohibited. If you received this transmission in 
error, please

immediately notify us by telephone so that we can arrange for the retrieval of 
the original

document.





~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

Reply via email to