Windows Server 2012R2 DHCP Server Memory Leak?
-
@popester It was an older article on 2012 R2. It appears that the problems created by disabling IPv6 are growing with Server 2016. This may become a "prison sex" scenario.
-
@popester said in Windows Server 2012R2 DHCP Server Memory Leak?:
@popester It was an older article on 2012 R2. It appears that the problems created by disabling IPv6 are growing with Server 2016. This may become a "prison sex" scenario.
I'm not familiar with how that term applies here (or anywhere other than when talking about sex.)
-
@scottalanmiller You can only put off IPv6 for so long. Eventually you will be assimilated. No pun intended.
-
My reference was very unprofessional and I would like to apologize to the group. I will refrain from such sophomoric behavior in the future. This is not the venue for such things. Thank you.
-
Do you have the latest Xen-Server tools install on your VM?
-
@popester said in Windows Server 2012R2 DHCP Server Memory Leak?:
My reference was very unprofessional and I would like to apologize to the group. I will refrain from such sophomoric behavior in the future. This is not the venue for such things. Thank you.
We are all sophomoric here. Just wasn’t sure how to apply the reference to the situation.
-
I’m testing quotes again.
-
Dammit
-
@black3dynamite said in Windows Server 2012R2 DHCP Server Memory Leak?:
Do you have the latest Xen-Server tools install on your VM?
No, looks like that was pretty old. I just updated and restarted. I'll monitor the memory for a while and see if that has any impact.
-
Odd question, why are you keeping snapshots for a week at time?
As for the leak, you mentioned the azure change and noticed this issue.
So what is pointing you to this as the possible issue?
-
@bnrstnr said in Windows Server 2012R2 DHCP Server Memory Leak?:
I have some warnings and errors in the event viewer that I'm going through now. Is there any reason to have IPv6 enabled if we're not using it? A lot of warnings in there about IP6 supposed to be static only.
I wouldn't disable ipv6 unless you are unable to find and fix the real root cause of an issue in which disabling ipv6 may mask.
https://blogs.technet.microsoft.com/jlosey/2011/02/02/why-you-should-leave-ipv6-alone/
