working from home. giving up. wife has cooked chocolate cake and all i can smell is cake!

@nadnerB said in What Are You Doing Right Now:

@siringo said in What Are You Doing Right Now:

running wsus cleanup wizard

hope you packed dinner. You might be there a while

haha, yeah. It wasn't too bad.

running wsus cleanup wizard

@scottalanmiller said in What Are You Doing Right Now:

Pretty sure we had BIND in HA a decade earlier.

or were you in a bind with HA??

just for interests sake, re dhcp:
https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-2000-server/cc958936(v=technet.10)?redirectedfrom=MSDN

@EddieJennings said in What Are You Doing Right Now:

Recording some videos for YouTube.

They've already got quite a few.

@scottalanmiller said in What Are You Doing Right Now:

@siringo said in What Are You Doing Right Now:

I have dhcp running on 2 servers with non overlapping address scopes
server 1 hands out a.b.c.100 - 254
server 2 hands out a.b.d.100 - 254

So to go along with your question. This means each server has 155 addresses to hand out and there are 310 addresses in the pools.

With the way it is set up, only 155 addresses are guaranteed to be usable. But if you made the scope continuous not only would you get both sets, but you'd get c.100-254, but c.100-d.254 for 410 total addresses! Way more. Because you have loads being lost just because you are blocking off random addresses in the middle of your range, too.

yep, no worries, thanks. but how can i add a second dhcp server for redundancy?

@scottalanmiller said in What Are You Doing Right Now:

@siringo this setup is what we like to call "being weird." LOL What caused you to go down this path?

it's what i learnt back in the day, (1990s).
hey this is good, i have a question.
i have noticed that i do get 1 server with most IPs handed out and the other with only a few.
if 1 server exhausts it's pool and receives a request for an address, does the server send back a 'sorry we're out of addresses' message?
coz if that's the case and PCs receive this message and don't re-broadcast their request, they could end up without an IP address.

I'm not against changing my thinking, I just need learn better ways.

@scottalanmiller said in What Are You Doing Right Now:

@siringo said in What Are You Doing Right Now:

@Dashrender said in What Are You Doing Right Now:

@siringo said in What Are You Doing Right Now:

@scottalanmiller said in What Are You Doing Right Now:

@siringo said in What Are You Doing Right Now:

having to put in reservations for .255 & .0 ip addresses as windows dhcp issues them when you have a /23 scope. annoying.

Why would you be reserving them? In a /23 scope they are just part of the normal range. You should be using them for something special. Nothing should be annoying in that system.

It can cause confusion for stand in support people seeing .0 and/or .255 IP addresses, it's not usual.

Plus I split the network up, 254 addresses on 1 dhcp server and 254 on another. You can't exclude 0 & 255 from being assigned so I just reserve them so they don't get assigned.

I thought MS added failover DHPC servers in Server 2016 - so two servers could share a single range without risk of double assigning? Perhaps I misread something.

@https://www.itprotoday.com/windows-78/configuring-dhcp-failover-windows-server-2016 said:

DHCP failover is a new feature (available in Server 2012 and later versions) for ensuring high availability of DHCP server on an enterprise network. The two servers in a failover relationship share lease information including reservations, scope options, exclusion, policies, and filters

Looks like I was wrong - added in 2012.

I have dhcp running on 2 servers with non overlapping address scopes
server 1 hands out a.b.c.100 - 254
server 2 hands out a.b.d.100 - 254

The scopes don't overlap, but the network does. How does a device know which one to ask for an address? Sounds like they currently just choose a range at random based on which DHCP server responds first? but... why?

they do they just broadcast for an address, doesn't matter whether they're on network a or b, the scope options are the same for both scopes/servers. It's no different to having a single dhcp server that gives out addresses from a.b.c.100 - a.b.d.254

@Dashrender said in What Are You Doing Right Now:

@siringo said in What Are You Doing Right Now:

@scottalanmiller said in What Are You Doing Right Now:

@siringo said in What Are You Doing Right Now:

having to put in reservations for .255 & .0 ip addresses as windows dhcp issues them when you have a /23 scope. annoying.

Why would you be reserving them? In a /23 scope they are just part of the normal range. You should be using them for something special. Nothing should be annoying in that system.

It can cause confusion for stand in support people seeing .0 and/or .255 IP addresses, it's not usual.

Plus I split the network up, 254 addresses on 1 dhcp server and 254 on another. You can't exclude 0 & 255 from being assigned so I just reserve them so they don't get assigned.

I thought MS added failover DHPC servers in Server 2016 - so two servers could share a single range without risk of double assigning? Perhaps I misread something.

@https://www.itprotoday.com/windows-78/configuring-dhcp-failover-windows-server-2016 said:

DHCP failover is a new feature (available in Server 2012 and later versions) for ensuring high availability of DHCP server on an enterprise network. The two servers in a failover relationship share lease information including reservations, scope options, exclusion, policies, and filters

Looks like I was wrong - added in 2012.

I have dhcp running on 2 servers with non overlapping address scopes
server 1 hands out a.b.c.100 - 254
server 2 hands out a.b.d.100 - 254