I have seen instances in earlier versions of Windows where the Windows network connection interface took awhile to initialize, and if you configure a static IP before the interface completed initialization, the static IP address failed. I think this might be what happened to you.
- Remove the VLAN.
- Wait 60 seconds
- Create a VLAN using the VLAN tab.
- Do something else for a few minutes. A few minutes is probably longer than needed, but I don't know how to tell when it is safe to assign the static IP address.
- Assign a static IP address to the VLAN interface.
I hope this helps.
Alright so this all was a HUGE code 18 on my part.
I am building my "new" PC at work alongside my working one... and like an idiot I set up the same static IP on both! When I reverted to installing Windows 7 it popped-up an IP address conflit message which Windows 8 never popped!
So I went back to Windows 8 making sure to have different IPs and all is well.
No bug in the drivers, simply bad handling on my part.
thanks for the help Mark H.!
I have to try to remember this symptom. Maybe Windows 8 calls an IP conflict a "duplicate." I hadn't thought of that when you shared the ipconfig information. Maybe Windows 8 is trying to be helpful by assigning an automatic address instead of warning of an IP conflict. I will watch for that situation in the future.
I am glad your issue is resolved. Have a great day.
that would indeed make sense! Still they could've kept the useful pop-up to let us know that we just did something wrong on the network.
have a good one!