A sine sunny day, this nic desicded to assign itself IPs outside the network and does not connect to the DHCP anymore. Even after manually assigning an IP address, it does not connect. I dont know what caused this or how to fix this. I have reinstalled the Connect X 3 VPI drivers and also reset network settings a number of times but no joy. It keep getting stuck at identifying network.
Does anyone have any insight into why this is happening?
Have a look at the IP address it assigns itself. My range is between 192.168.1.2 to 240 and the subnet mask is bonkers.
Even after manually assigning an IP, it still is stuck at identifying network.
I have release the leases with cmd and also flushed DNS a few times but no joy.
I have messed around with the adapter settings and also removed the device from device manager a number of times but it just does not work.
It was working fine just a few days ago and now this.
Any help would be much appreciated. It does not seem to be the nic, its a windows setting somewhere from what I can see
Does anyone have any insight into why this is happening?
Have a look at the IP address it assigns itself. My range is between 192.168.1.2 to 240 and the subnet mask is bonkers.
Even after manually assigning an IP, it still is stuck at identifying network.
I have release the leases with cmd and also flushed DNS a few times but no joy.
I have messed around with the adapter settings and also removed the device from device manager a number of times but it just does not work.
It was working fine just a few days ago and now this.
Any help would be much appreciated. It does not seem to be the nic, its a windows setting somewhere from what I can see