What Are You Doing Right Now
-
Have family visiting this weekend.
-
having to put in reservations for .255 & .0 ip addresses as windows dhcp issues them when you have a /23 scope. annoying.
-
@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.
-
@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.
-
@siringo said in What Are You Doing Right Now:
It can cause confusion for stand in support people seeing .0 and/or .255 IP addresses, it's not usual.
Actually it's 100% usual and if it causes problems for the support people, it means that they are 100% lost on the fundamentals of networking and have memorized incorrect information rather than learning how networking works. This is how all networking and DHCP works, all of the time. There is no system, no IPv4 and no DHCP that doesn't do this. If Windows did it any differently, it would be completely wrong.
If you have support people struggling with this, they are a serious problem and not in a position to be helping resolve network issues (but likely causing them.)
-
@siringo said in What Are You Doing Right Now:
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.
Why do you split up in that way? And how do you know which one is going to hand out the addresses? This sounds like a mess. A single DHCP server can handle so much more than this, even a tiny VM or Raspberry Pi could do DHCP for hundreds of thousands of machines. I'm not even sure how this would work.
-
About to check out and play a video game for a change!
Ni no Kuni: Wrath of the White Witch
-
grabbing Coffee #2 email purging and Monday team meeting out of the way.
Working on getting my Site out the door. applied for a few positions that I'm "under qualified" for and looking at a few more.
I saw this quote this weekend: "find a job you are under qualified for, then work until you're over qualified. then.. Repeat."
-
Only on coffee one, but because I was in a meeting for the last hour. Almost time for #2.
-
@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.
-
Upgraded Telegram for desktop to 1.9.4 using Choco
Threw an error that it couldn't find the path specified but upgrade went through . -
@WrCombs said in What Are You Doing Right Now:
Upgraded Telegram for desktop to 1.9.4 using Choco
Threw an error that it couldn't find the path specified but upgrade went through .did you originally install it using Choco?
If not, that could be the problem. -
@Dashrender said in What Are You Doing Right Now:
@WrCombs said in What Are You Doing Right Now:
Upgraded Telegram for desktop to 1.9.4 using Choco
Threw an error that it couldn't find the path specified but upgrade went through .did you originally install it using Choco?
If not, that could be the problem.yeah, i did..
-
@Dashrender said in What Are You Doing Right Now:
@WrCombs said in What Are You Doing Right Now:
Upgraded Telegram for desktop to 1.9.4 using Choco
Threw an error that it couldn't find the path specified but upgrade went through .did you originally install it using Choco?
If not, that could be the problem. -
@Dashrender said in What Are You Doing Right Now:
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.
You can definitely have two, we do that from time to time.
-
Wiping / reloading our current iPads, about to set up some new ones as well. Blech. Had to try 4x to get the software update to run on the 1st one.
-
Office moving day, YEA! Seems like every year or so the CxO decided everyone should play musical chairs
-
Trying to find a project in Redmine that my boss swears he's looked at before, but can't remember the name of it exactly, and can't remember the last time he saw it
-
Been getting absolutely destroyed with calls today.
-
scheduled windows 10 upgrade for tomorrow (where I'll be prepared to have my Laptop for calls. ) wanted to do it today , but haven't had a slow enough time to do so.
