Beire Posted August 6, 2015 Share Posted August 6, 2015 I've got a weird problem with my windows 10 installation. Though i'm not quite sure this wasn't happening before i upgraded from 8.1... Anyway.. When i view the details section of my ethernet adapter i noticed it having 2 ipv4 adresses. One of which i never added myself. I found multiple posts online to reet the network configuration. But none of them work. Upon initialising the adapter, i get only 1 (static) ip address, but after a few seconds the second one comes up. This one is always different also. In the advanced section i'm not seeing a second ip address either. It annoys me because my unraid server is spamming syslog errors because of this ip address.... Anyway i hope someone can help Link to comment https://www.neowin.net/forum/topic/1267746-windows-10-second-ipv4-address-unable-to-remove/ Share on other sites More sharing options...
TheReaperMan Posted August 6, 2015 Share Posted August 6, 2015 are you running vmware? can you post the full ipconfig /all Link to comment https://www.neowin.net/forum/topic/1267746-windows-10-second-ipv4-address-unable-to-remove/#findComment-596961718 Share on other sites More sharing options...
Zinomian Posted August 6, 2015 Share Posted August 6, 2015 take a screen shot of your network adapters. Like "TheReaperMan" said, it could be some sort of virtual machine software. Link to comment https://www.neowin.net/forum/topic/1267746-windows-10-second-ipv4-address-unable-to-remove/#findComment-596961726 Share on other sites More sharing options...
Beire Posted August 6, 2015 Author Share Posted August 6, 2015 I had vmware installed before but removed it to eliminate. The screenshots were taken after removing vmware. Here's the full ipconfig Link to comment https://www.neowin.net/forum/topic/1267746-windows-10-second-ipv4-address-unable-to-remove/#findComment-596961908 Share on other sites More sharing options...
AnDom Posted August 6, 2015 Share Posted August 6, 2015 If I am reading that correctly, that address is 169.254.x.x which is Link-Local: https://en.wikipedia.org/wiki/Link-local_address I am not using Windows 10, so I don't know if this is normal behavior for it or not... but it is advised against in the RFC: Quote A host with an address on a link can communicate with all other devices on that link, whether those devices use Link-Local addresses, or routable addresses. For these reasons, a host SHOULD NOT have both an operable routable address and an IPv4 Link-Local address configured on the same interface. Link to comment https://www.neowin.net/forum/topic/1267746-windows-10-second-ipv4-address-unable-to-remove/#findComment-596962134 Share on other sites More sharing options...
Recommended Posts