CIS occasionally “wake up” and warns me of a newly detected network that starts with 169.254 …
In my network, EVERY device has long been a specific IP from me pre-assigned, and I am sure you do not have other devices - let alone wired - that require access to the network.
I kindly ask for help, even if they are almost certain that addresses beginning with 169.254 are internal to the network. But I’m breaking my head for no reason …
That’s an APIPA address. Did the computer just resume from sleep/hibernate? If so Window will have to retool the network settings to make sure their correct. If Window fails to get a response from a DHCP server it falls back to using APIPA.
Read here: What is Automatic Private IP Addressing (APIPA)? | Webopedia
@aim4it
Sorry for the delay in response. Thanks… 
I hope that I will read.
I understand what is APIPA, also confirm that the problem happens after resume from standby, but I do not understand why Windows should not find the DHCP server, regularly set in the network and router.
Moreover, in router I set DHCP with the pre-assignment of IP addresses for each MAC address of each device
If you’ve assigned every device it’s own IP address you don’t really need DHCP at all. So why not hard code the IP address in the computer? It won’t then need to try to contact a DHCP server and you won’t get this problem.
If you have set up the router to give a specific MAC address a specific IP address then you also need to set that IP address on the computer in question, manually. If you set a specific device to have a specific IP in the router but set the device to ask for DHCP then it might result in the issue you’re seeing.
I get it …
I decided to keep active the DHCP server, to avoid assigning a specific IP to friends/relatives/acquaintances who sometimes connect to my network, with different devices often …
I know that it is much better to assign specific IP to each machine, but the "reservation (or pre-assignment) is an acceptable compromise.
However, this detection performed by CIS is only about a month, not more … This is new …
Maybe I have not explained it well: at each my device connected permanently to my network (both LAN and WiFi) I assigned a specific IP.
In my router the same IP was “pre-assigned” associating it with the MAC of each machine in my network …
http://s17.postimg.org/5jr3geke3/Immagine.jpg
So in the router you have set an IP address to be reserved for a specific MAC address, then on the computer in question you have changed the ipv4 (or 6) properties of the NIC to use that specific IP address? In that case I don’t know why CIS would react like this, are you using wireless on the computer in question? Could it potentially be the wired Ethernet port (if present) that is acting up? Does it still happen if you disable the wired NIC in Windows? (again, if present and if you don’t need it)
You can have dynamic and fixed addresses on the same network. So for those devices where you can code a fixed IP address do so and they won’t use DHCP. For all other devices leave them as dynamic and they will use DHCP. Just be certain that the DHCP server is not able to allocate any of the fixed addresses.
So hard code the 192.168.1.101 to 192.168.1.117 addresses to your fixed devices and set the DHCP server to allocate the range 192.168.1.120 to 192.168.1.254.
how disable wired NIC in Windows? I do not know what …
More or less how you write … all my static devices have an IP pre-assigned… all other devices “guests” who require access to get an IP number more than 117…
However I emphasize that the problem that the (small) problem is evident only to “wake up” from standby, as another user has suggested …
I don’t know what version of Windows you’re using but you go to Control Panel > Network and Internet > Network and Sharing Center > In the left menu click “Changer adapter settings” > Identify the network adapter that is for the wired Ethernet port (as long as it’s not in use) and right-click it then click “Disable”
Edit: If you do this the interface will be disabled, if you plug in an Ethernet cable it won’t re-enable automatically, you would have to go into the same place and manually enable the interface again.
I understand what you wrote, but I’m sorry … I did not understand the utility.
Moreover, the operation that I suggest we do - for other reasons - I’ve already made several times … but also this morning, on the stand-by resume, I had once again warning of CIS.
Thing - with the same, identical, version of Windows 7 SP1 64bit , it’s never happened - I repeat, never happened, until about two months ago …
http://s21.postimg.org/bumlyavf7/Immagine.jpg
I could to flag the “Don’t detect more new networks”, but so, if I were to use another rede, the kind that you see below, would not be monitored.
Because first CIS did not give me this warning and now it provides daily :embarassed: ??
http://s16.postimg.org/98lgyorkh/Immagine2.jpg
I remember that every my network card, and then for each MAC of this computer and all other devices with internet access, I pre-assigned a specific IP as shown to the post n.5
Your problem is, I’m sure, because of some delay in waking your network card so that it fails to contact your DHCP server when the PC wakes. As I said, the problem can be easily sorted by not using DHCP for that PC and coding the fixed IP address etc. in the adapter itself.
With the contribution of you all I solved ! 
I remembered that a couple months ago, in “Device Manager” I have set in all Network card > Energy saving, the flag: “Allow the computer to turn off this device to save power”.
I removed the flag and has returned all right.
Was enough remember . . . ;D
It was not fault of CIS, but only my … :-[
Hi anyone, I have the same problem today (after new upgrade of comodo suite), I didn’t change anything from my pc/network and this window is show from a cold boot (no resume - ibernate status).
