Windows IP Assignment Issue
-
Windows Server 2012 R2. One adapter. VM. KVM with drivers installed. Just want to set the IPv4 address as static. Seems like this would be simple, I do this all the time. But this one is confusing me. This has to be super simple, I'm just lost.
Only one adapter...
Set static:
Then this...
What am I doing wrong?
-
The 169. Network is for
DHCPAPIPA, I'm sure your aware of that. You have "configured the settings correctly" They just didn't take effect. It seems that the Dhcp failed and reverted to the APIPA address.Sometimes if you tick the box "validate settings upon exit" it will force the settings change.
Or
A disable and reenable of the ethernet adaptor will usually resolve it.
Or
from cmd... ipconfig \release.
Then
ipconfig \renewJust some of the different ways I have resolved it when it happened to me.
-
The 169. Network is for
DHCPAPIPA, I'm sure your aware of that. You have "configured the settings correctly" They just didn't take effect. It seems that the Dhcp failed and reverted to the APIPA address.Sometimes if you tick the box "validate settings upon exit" it will force the settings change.
Or
A disable and reenable of the ethernet adaptor will usually resolve it.
Or
from cmd... ipconfig \release.
Then
ipconfig \renewJust some of the different ways I have resolved it when it happened to me.
-
I've rebooted a few times, you'd think that that would trigger it.
-
@StrongBad said in Windows IP Assignment Issue:
I've rebooted a few times, you'd think that that would trigger it.
Yes normally I would say that would work. Hmmm.
-
What happens if you try the other methods in my first post
-
@prcssupport said in Windows IP Assignment Issue:
What happens if you try the other methods in my first post
I'm sorry I just realized I reversed the "/" to \
On my mobile device I tend to do that. Just like I can't type lol.
-
Okay, I rebuilt a second machine and started from scratch. SAME ISSUE!!
-
Okay, tried the "Validate" option, and that seemed to make it work. It complained that DNS failed, but DNS did not fail, oddly. So looks like it might be working now.
-
Appears to be working now. Why would it only work with the extra check box?
-
@StrongBad said in Windows IP Assignment Issue:
Okay, I rebuilt a second machine and started from scratch. SAME ISSUE!!
Hmmm not sure why it would give you the same issue. That doesn't make to much sense.
-
@StrongBad said in Windows IP Assignment Issue:
Appears to be working now. Why would it only work with the extra check box?
Was there some policy / GPP or script in place which overrides the NIC to use DHCP? That would explain the APIPA address.
-
@StrongBad said in Windows IP Assignment Issue:
Okay, I rebuilt a second machine and started from scratch. SAME ISSUE!!
Have you tried something apart from Windows? Some live Linux for example?
-
@thwr said in Windows IP Assignment Issue:
@StrongBad said in Windows IP Assignment Issue:
Appears to be working now. Why would it only work with the extra check box?
Was there some policy / GPP or script in place which overrides the NIC to use DHCP? That would explain the APIPA address.
Just read your response and then realized I mispoke. My mind was thinking APIPA (but forgot the term) and was thinking Dhcp assignment failed and then the APIPA was assigned instead.
-
Wow crazy problem, never seen that before.
