RE: DHCP reservations explained...

2011 13:33:54 -0800 Subject: RE: DHCP reservations explained... > We always prefer static addresses for servers. One less variable when > we're troubleshooting later. > > > > Ben M. Schorr > Chief Executive Officer >

RE: DHCP reservations explained...

r.com <mailto:b...@rolandschorr.com> From: Candee [mailto:can...@gmail.com] Sent: Monday, January 24, 2011 09:40 To: NT System Admin Issues Subject: Re: DHCP reservations explained... I use static addresses for my servers. I also have my pool start at say x.x.x.100, so I know the addr

Re: DHCP reservations explained...

+1 We had different groups depending on the device. Server, switch, router, sniffer etc. On Mon, Jan 24, 2011 at 5:40 PM, Candee wrote: > I use static addresses for my servers. > I also have my pool start at say x.x.x.100, so I know the address won't be > assigned elsewhere. > > On Tue, Jan 18,

Re: DHCP reservations explained...

I use static addresses for my servers. I also have my pool start at say x.x.x.100, so I know the address won't be assigned elsewhere. On Tue, Jan 18, 2011 at 2:14 PM, Jonathan wrote: > Hmmm... interesting concept. I personally prefer static addressing assigned > on each individual server. Though

RE: RE: DHCP reservations explained...

Probably :) From: Jonathan [mailto:ncm...@gmail.com] Sent: Monday, January 24, 2011 7:08 AM To: NT System Admin Issues Subject: Re: RE: DHCP reservations explained... Don't you mean broadcasts, rather than requests? Jonathan On Jan 24, 2011 10:05 AM, "David Lum" mailto:dav

Re: RE: DHCP reservations explained...

T EVALUATION ASSOCIATION > (Desk) 503.548.5229 // (Cell) 503.267.9764 > > > > -Original Message- > From: Phil Brutsche [mailto:p...@optimumdata.com] > Sent: Monday, January 24, 2011 7:00 AM > To: NT System Admin Issues > Subject: Re: DHCP reservations explained

RE: DHCP reservations explained...

lto:p...@optimumdata.com] Sent: Monday, January 24, 2011 7:00 AM To: NT System Admin Issues Subject: Re: DHCP reservations explained... I have one addition to this: The helper-address command tells the L3 device to forward ALL UDP broadcasts - DHCP, TFTP, NetBIOS, etc. You would also need to execute these comman

RE: DHCP reservations explained...

tonind.com] Sent: Monday, January 24, 2011 8:24 AM To: NT System Admin Issues Subject: RE: DHCP reservations explained... Just ran in to that with Cisco last week when I migrated my DHCP from 03 to 08r2. Only Vlan that could see the server was the one the server was on. Int vlan xx Ip help

Re: DHCP reservations explained...

I have one addition to this: The helper-address command tells the L3 device to forward ALL UDP broadcasts - DHCP, TFTP, NetBIOS, etc. You would also need to execute these commands to exclude everything that's not DHCP: no ip forward-protocol udp domain no ip forward-protocol udp time no ip forwar

Re: RE: DHCP reservations explained...

top any rogue DHCP servers. > > Bill Mayo > > > > From: N Parr [mailto:npar...@mortonind.com] > Sent: Monday, January 24, 2011 8:24 AM > To: NT System Admin Issues > Subject: RE: DHCP reservations explained... > > > Just ran in to that with Cisco last week w

RE: DHCP reservations explained...

January 24, 2011 8:24 AM To: NT System Admin Issues Subject: RE: DHCP reservations explained... Just ran in to that with Cisco last week when I migrated my DHCP from 03 to 08r2. Only Vlan that could see the server was the one the server was on. Int vlan xx Ip helper-address 1

RE: DHCP reservations explained...

, January 23, 2011 4:36 PM To: NT System Admin Issues Subject: RE: DHCP reservations explained... There is a feature on Cisco switches at least that will inspect and block DHCP server packets on switch ports not trusted for DHCP. My higher education customers who run residential networks tend to

RE: DHCP reservations explained...

"backwards" (e.g. LAN port into the resnet). Thanks, Brian Desmond br...@briandesmond.com w - 312.625.1438 | c - 312.731.3132 From: Erik Goldoff [mailto:egold...@gmail.com] Sent: Wednesday, January 19, 2011 8:29 AM To: NT System Admin Issues Subject: RE: DHCP reservations explained... "

Re: RE: DHCP reservations explained...

n.org] > *Sent:* Wednesday, January 19, 2011 6:10 AM > > *To:* NT System Admin Issues > *Subject:* RE: RE: DHCP reservations explained... > > > > Then go with Bluecat Devices… if you want the HA with your DHCP.. We are > doing that here with 2 Bluecat Appliances. >

RE: RE: DHCP reservations explained...

bservation that there are a number of options. From: Ziots, Edward [mailto:ezi...@lifespan.org] Sent: Wednesday, January 19, 2011 6:10 AM To: NT System Admin Issues Subject: RE: RE: DHCP reservations explained... Then go with Bluecat Devices... if you want the HA with your DHCP.. We are doing t

RE: RE: DHCP reservations explained...

...@gmail.com] Sent: Tuesday, January 18, 2011 2:38 PM To: NT System Admin Issues Subject: Re: RE: DHCP reservations explained... Right @ 100 servers. Haven't been burned, but I'm not thrilled about lack of true failover/redundancy in DHCP in W2k3. 80/20 doesn't cut it, IMHO. On Ja

RE: DHCP reservations explained...

f IT Consultant Systems, Networks, & Security ' Security is an ongoing process, not a one time event ! ' From: Andrew S. Baker [mailto:asbz...@gmail.com] Sent: Tuesday, January 18, 2011 4:50 PM To: NT System Admin Issues Subject: Re: DHCP reservations explained... I am not fond

Re: DHCP reservations explained...

+1 -- ME2 On Tue, Jan 18, 2011 at 11:16 AM, Erik Goldoff wrote: > I've always liked DHCP reservations over static IP addresses for servers > where possible for ease of management >Single view of most servers from DHCP client list >simple to change parameters globally ( default gatew

Re: DHCP reservations explained...

ialExchange.com > > > > *From:* David Lum [mailto:david@nwea.org] > *Sent:* Tuesday, January 18, 2011 3:06 PM > *To:* NT System Admin Issues > *Subject:* RE: DHCP reservations explained... > > > > If DNS stops responding, what’s working? > > > > Having

RE: DHCP reservations explained...

e MVP http://TheEssentialExchange.com From: David Lum [mailto:david@nwea.org] Sent: Tuesday, January 18, 2011 3:06 PM To: NT System Admin Issues Subject: RE: DHCP reservations explained... If DNS stops responding, what's working? Having said that, I see your point. We (%dayjob%) have 3 DN

Re: DHCP reservations explained...

templates trying to grab in-use addresses. YMM (vastly) V Typed frustratingly slowly on my BlackBerry® wireless device -Original Message- From: "Andrew S. Baker" Date: Tue, 18 Jan 2011 16:49:47 To: NT System Admin Issues Reply-To: "NT System Admin Issues" Subject: R

Re: DHCP reservations explained...

I am not fond of DHCP for server management, even though I will admit that it is a viable possibility. I prefer the flexibility of configuration that is possible when you have statically mapped IPs, and I've done this with hundreds of servers in various environments. In my experience, I've seen m

RE: DHCP reservations explained...

To: NT System Admin Issues Subject: Re: DHCP reservations explained... If DNS stops monitoring, I'd like my monitoring server to notice that too. The likelihood is that the apps I am running will rely on DNS, so other things will break beyond the monitoring. ASB (My Bio via About.Me

Re: DHCP reservations explained...

If DNS stops monitoring, I'd like my monitoring server to notice that too. The likelihood is that the apps I am running will rely on DNS, so other things will break beyond the monitoring. *ASB *(My Bio via About.Me ) *Exploiting Technology for Business Advant

Re: DHCP reservations explained...

I think this depends on one's environment. If you only have a handful of servers, manual configuration is fine, even preferred. If you've got 100 servers, manual configuration is unwieldy at best, and if you ever have to renumber your network, you're in for a lot of work. We manually config ou

Re: DHCP reservations explained...

on my BlackBerry® wireless device > -- > *From: *Jonathan Link > *Date: *Tue, 18 Jan 2011 16:09:24 -0500 > *To: *NT System Admin Issues > *ReplyTo: *"NT System Admin Issues" > > *Subject: *Re: DHCP reservations explained... > > I hav

Re: DHCP reservations explained...

ntialexchange.com/> > > > > *From:* Erik Goldoff [mailto:egold...@gmail.com] > *Sent:* Tuesday, January 18, 2011 4:03 PM > > *To:* NT System Admin Issues > *Subject:* RE: DHCP reservations explained... > > > > I **would** recommend having a proper host file available but

RE: DHCP reservations explained...

cess, not a one time event ! ' From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Tuesday, January 18, 2011 4:06 PM To: NT System Admin Issues Subject: RE: DHCP reservations explained... Automate, automate, automate. Regards, Michael B. Smith Consultant and Exch

Re: DHCP reservations explained...

*From:* Erik Goldoff [mailto:egold...@gmail.com] > *Sent:* Tuesday, January 18, 2011 4:03 PM > > *To:* NT System Admin Issues > *Subject:* RE: DHCP reservations explained... > > > > I **would** recommend having a proper host file available but not in > production. Personally

RE: DHCP reservations explained...

Automate, automate, automate. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Erik Goldoff [mailto:egold...@gmail.com] Sent: Tuesday, January 18, 2011 4:03 PM To: NT System Admin Issues Subject: RE: DHCP reservations explained... I *would* recommend

RE: DHCP reservations explained...

ons.com] Sent: Tuesday, January 18, 2011 2:37 PM To: NT System Admin Issues Subject: RE: DHCP reservations explained... I will always do one of two things: [1] use an IP address, or [2] have a rather complex hosts file on the server(s) running the monitoring software. After all

RE: DHCP reservations explained...

t flooded our switches, making the servers that could run really spotty to hit from a PC. SAN guy not happy, network guy not happy, but my DC's were fine, lol. Dave From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Tuesday, January 18, 2011 11:37 AM To: NT System Admin Issues

Re: RE: DHCP reservations explained...

n burned by DHCP issues in the past, or have few enough servers it's not too inconvenient? > > Dave > > From: Erik Goldoff [mailto:egold...@gmail.com] > Sent: Tuesday, January 18, 2011 11:16 AM > To: NT System Admin Issues > Subject: Re: DHCP reservations explained... > &

RE: DHCP reservations explained...

I will always do one of two things: [1] use an IP address, or [2] have a rather complex hosts file on the server(s) running the monitoring software. After all, if DNS stops responding, are you going to stop monitoring? Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialE

RE: DHCP reservations explained...

+1. For same reasons. Jonathan I'm guessing you've been burned by DHCP issues in the past, or have few enough servers it's not too inconvenient? Dave From: Erik Goldoff [mailto:egold...@gmail.com] Sent: Tuesday, January 18, 2011 11:16 AM To: NT System Admin Issues Su

Re: DHCP reservations explained...

I've always liked DHCP reservations over static IP addresses for servers where possible for ease of management Single view of most servers from DHCP client list simple to change parameters globally ( default gateway, primary DNS, secondary DNS, etc ) without having to visit each server les

Re: DHCP reservations explained...

Hmmm... interesting concept. I personally prefer static addressing assigned on each individual server. Though I could see the appeal of using DHCP, I don't have enough confidence in DHCP to use it for server addressing. Just my $0.02 On Jan 18, 2011 2:06 PM, "David Lum" wrote: > The other day some

Re: DHCP reservations explained...

Is that so they can continue to monitor servers during a DNS outage? The only thing I have to use IP address for is WebSense and that's just because it won't accept a hostname. Even my ESX servers do most everything by FQDN. Depends a lot on the apps you have around though, I guess. Typed frust