CIS says it detected new netword. Wired 169.254.92.68/17. I have not joined on any new network.
My router have DHCP and I usually get 192.168.0.100 ip-address, mask is 255.255.255.0, gateway is 192.168.0.254 and DNS is Comodos. Ipconfig gives normal addresses.
Should I be worried? And what actions I should take?
You probably* do not need to be worried. It’s likely that your PC was merely unable get a DHCP response from the router in a timely manner, which meant Windows used the network adapter’s default IP (eg. 169.254.92.68). And CIS would detect that new IP.
This can happen when the PC is starts before the router or if the LAN cable is temporarily disconnected on Windows start-up. It can also happen when a network adapter’s drivers are updated (either manually or by a Windows Update).
In any event, often the DHCP does complete successfully a short time later and Windows sets the LAN IP with the DHCP value. Although this is not always the case and sometimes may require a PC reboot (the easiest solution) to resolve it.
The LAN IP you mentioned (169.254.92.68) is an internal LAN IP (169.254.1.0 - 169.254.254.255), just like 192.168.0.100 and cannot be routed from/to the internet by your router.
If your LAN contains other machines, they can also cause a new LAN IP to suddenly appear due to any of the above.
*Probably, because I don’t know exact circumstances of what happened.
I’ve been having a similar problem. One laptop, which shares a home network with two other laptops, uniquely connects to 169.254.92.68/17 (gateway 255.255.0.0), whereas the other two laptops connect correctly to 192.168.x.x (gateway 255.255.255.0). The laptop failed both wired and wirelessly. The laptop is less than 1 year old, and has worked normally until last week, when an attempt to share a public folder with another computer co-incided with the start of the issue.
Basic solutions - re-boot modem, check cables, clear wifi profiles - all failed. The router-modem appears to work normally for the other two laptops, so there are no grounds for suspecting a selective failure of DHCP.
Advanced solutions - like upgrading the device driver for the wireless adapter on the unconnected laptop - also failed. I got to the point of trying a Windows restore, which Windows aborted because, it said, of an anti-virus program. That resulted in the uninstallation of the anti-virus (AVG Free), which restored the wired connection to IP 192.168.x.x. But the wifi continued to connect to 169.254.92.68.
Only when Comodo Firewall was disabled did Comodo popup say that a new network 192.168.x.x had been detected. Hallelujah!! That’s the network I’ve been waiting for. So now Comodo has been uninstalled.
So the laptop now has good network access, but only if there is no anti-virus or firewall on it. Not much of a solution!
What’s happened? And where do I go from here?
As Kail mentioned, APIPA addresses (169.254.0.0/255.255.0.0) are allocated in the absence of a DHCP server. This maybe a temporary problem or, with smaller installations, intentional.
When Windows boots the DHCP client service attempts to acquire an IP address by broadcasting a DHCPDiscover message, assuming a response, form an appropriately configured DHCP server, is received, all proceeds normally. If, however, there is no response or the response is delayed (more than a minute), the Windows client enters auto-configuration mode. During this phase the client auto assigns an address from the APIPA range mentioned above. The question is, why, on some systems, is the client failing to find a DHCP server with CIS installed.
It looks like the services required to communicate over DHCP are being either blocked or restricted in some way, hence the auto-configuration. If there are no obvious problems with the firewall/D+, then my best guess would be driver initialisation/conflict.
It may be possible to use something like a combination of wireshark and process monitor to determine where the failure is occurring…