Windows 10: No network connectivity

Hi, I suffer total loss of network connectivity after a computer crash.

I am on win 10 x64

Here is my ipconfig /all, hopefully someone can spot what is wrong:

C:\WINDOWS\system32>ipconfig /all


Windows IP Configuration


Host Name . . . . . . . . . . . . : Xello
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No


Ethernet adapter Ethernet:


Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) Ethernet Connection (2) I218-V
Physical Address. . . . . . . . . : 10-C3-7B-A1-3E-4D
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::35c2:8a75:1fb4:66d8%9(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.102.216(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 185647995
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1D-55-A6-7B-10-C3-7B-A1-3E-4D
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled


Tunnel adapter isatap.{C0C4496D-EA53-4D75-BFEF-FC6EEC652592}:


Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes


C:\WINDOWS\system32>


​Windows troubleshooter reports that "One or more network protocols are missing on this computer".

Some other info: i am unable to connect to 192.168.0.1, which is my router's home page. I can load this page on my laptop if i connect my laptop with ethernet, so the router is fine.

:)

 

No network connectivity

@AlanWatson



You probably won't want to hear it but sometimes only solution is to backup essential data, reset device to "Out of box" state check features out before restoring data to device and probably avoid restoring "Settings".

 

No network connectivity

Hi,



I have a c5-03 running s60 5th edition v 20.0.024.211.01. I have default connectivity set either to 'internet' or to 'always ask' and always get a dialog entitled 'select connection' before I go on line with the browser, apps like internet radio etc.



Recently, when listening to internet radio in places with variable wifi signal strength I have lost the connection a few times and, when I try to reconnect, I get an error message 'no network connectivity' This comes up in place of the 'select connection'
dialog.



When I check the wlan wizzard it shows that I am still connnected to the wifi network and the networks diagnostics tool tells me that the connection is working fine, but I can't get the browser or any other app using connectivity to work. They carry on not
working even if I come back home and use my reliable wifi here.



Turning individual apps on and off or disconnecting and reconnecting to the wifi network seem not to work, but turnining the phone off and on again does.



It therefore seems to me that there is some bug in the software that should bring up the 'select connection dialog'.



Any suggestions on how to avoid or fix this problem would be gratefully received.



Thanks



Alan Watson

 

169,254... is a local IP address. Also, no Gateway, your PC is not picking up a DHCP address from your router. Check the connections to your router and restart your router.

 

Hi, I've been trying to sort this for around 4 hours now without success, but in that time i have restarted computer, reset router, and reset cables several times. I have even verified the lan ports on the router by using them with other systems.

My ipconfig /all has changed slightly, here it is now:

C:\WINDOWS\system32>ipconfig /all
Windows IP Configuration

Host Name . . . . . . . . . . . . : Xello
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Ethernet:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) Ethernet Connection (2) I218-V
Physical Address. . . . . . . . . : 10-C3-7B-A1-3E-4D
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::e5b5:ce37:9c32:968f%5(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.0.2(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 04 February 2016 17:05:05
Lease Expires . . . . . . . . . . : 05 February 2016 17:05:05
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DHCPv6 IAID . . . . . . . . . . . : 84984699
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1D-55-A6-7B-10-C3-7B-A1-3E-4D
DNS Servers . . . . . . . . . . . : 192.168.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{56956E17-939B-4ACD-B337-D033B72081D1}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

C:\WINDOWS\system32>

I have even performed a system restore to 2 weeks ago and the issue remains.

Another issue is that when doing ipconfig release and renew, I get this error when trying to renew (after hanging for a few mins):

Windows IP Configuration

An error occurred while renewing interface Ethernet : unable to contact your DHCP server. Request has timed out.

It's after trying the release + renew that my ipconfig /all gives the result in my first post.

Other commands I have tried are netsh winsock reset and netsh int ip reset.

I have also uninstalled my NIC in device manager and rebooted, using the default windows 10 driver for my NIC.

I have also uninstalled the NIC then tried using the latest driver for it from motherboard website.

 

I would set your adapter to a static IP
Open Network connections
Press the Windows Key + r
Copy and paste this
Code: ncpa.cpl[/quote] Right click on your adapter and select properties
Double click on Internet Protocol version 4 (TCP/IPv4)
Change your settings to
IP: 192.168.0.99
Subnet: 255.255.255.0
Default Gateway: 192.168.0.1

Use the following DNS server
8.8.8.8
8.8.4.4





Try using Googles DNS server
I live in Ontario Canada and I find that Googles DNS server works great here. You could also use your ISP's DNS server, To find that you will have to do a Google search for it.
Code: 8.8.8.8 8.8.4.4[/quote] Make sure your DHCP Client service is running...
Startup the Services window (Windows Key + r "services.msc"), then look for a line labeled "DHCP Client". Make sure that the Status column shows "Started" and the Startup Type column is "Automatic".

While your there check these ones too

Code: Computer Browser DHCP Client DNS Client Network Connections Network Location Awareness Remote Procedure Call (RPC) Server TCP/IP Netbios helper Workstation[/quote] Some general command line tips for trying to fix network problems
Go to command Prompt (Admin)

Reset WINSOCK entries to installation defaults:
Code: netsh winsock reset catalog[/quote] and after that
Reset IPv4 TCP/IP stack to installation defaults.
Code: netsh int ipv4 reset [/quote] And last but hopefully last
Reset IPv6 TCP/IP stack to installation defaults
Code: netsh int ipv6 reset[/quote]

Note After a reboot and you still have no connection check this ---if you have a static IP check your internet protocol (TCP/IPv4). They may have changed to 0.0.0.0
Reboot the machine.

 

thanks for the suggestions,

have run through them all with no success.
All the listed services had status 'Running', and all Automatic (with some being automatic: triggered start and things like that)

I also put in the static ip settings again after reboot, with no success. They are taking effect, they show in the "details" window of the connection status window, I just still have no data throughput.

The netsh commands are ones I already did try, but I tried again. Some of the 'resetting' statements fail.
However, I have now tried running those commands on my laptop (which has no issues) and they also have some failures there, so I don't think that is indicative of the issue.

 

I would check your network cable and if possible switch the cable from a working computer to the non working one, I guess you already tried rebooting the router.

Try to ping the router
Code: ping 192.168.0.1[/quote]

 

Yeah i have tried spare cables and pinging the router results in time outs.

I may be on to something, I noticed in my uninstall programs list i have "Intel(R) Technology Access" which was apparently installed today, I don't know what it is, but googling it makes me think it is probably causing this issue.

When I try to uninstall it, the uninstall fails with "The set up program ended prematurely because of the following error:
Fatal error during installation.

click here to open log file location."

I'm not sure if it would have been part of the driver installations I have run several times while troubleshooting, but either way the fact that I can't uninstall it is troubling. I actually have 3 instances of Intel(R) Technology Access in my programs list, all different versions.

 

I just thought, I can have windows reinstalled and up to my desired state in around 2 hours, but I have spent over 7 hours trying to fix this, so it's time to cut the losses and reinstall.

Thanks for suggestions.

 

Did a fresh install of windows 10 and the issue remains, how is this even possible ?

"One or more network protocols are missing on this computer" - on a brand new installation? i don't think so...

 

I'm battling the same issue. I think that the missing protocols issues has to do with missing winsock entries in the registry. I got past that by following the instructions here:
Network Protocols Missing

Essentially, the fix to the protocols error is to copy the winsock entries from a working machine.

I also note that your IP subnet mask is 255.255.0.0. I have the same issue. It's my understanding that it should be 255.255.255.0 for a typical home setup and that is must match the subnet mask used by your router. I don't know how to change the default subnet mask on my machine. Manually setting an IP address did not work. My wife's laptop and my router both use 255.255.255.0 as the subnet mask.

Take all this with a grain of salt. I know very little about the ins and outs of networking, apart from what I've picked up here while trying to get my computer back on line.

I hope that helps or gets a knowledgeable person on the right track.

on edit: I see from your third post that your subnet mask changed to 255.255.255.0, which should be OK.

 

sml156,

Thanks for your very detailed post, #3 above!

I tried all your suggestion. I tried disabling my ethernet and using my computer's WiFi to connect. I manually set the IP address, as you suggested, except that my router is 192.168.1.1. Wi-Fi status has the SSID showing the name of my router, so I believe that the link is OK. IPv4 and 6 show no network access. I can't ping the router and when I try to ping myself (192.168.1.99) I also get a general failure.

Thanks in advance for any help or suggestions.

 

Quick update, last thing i did last night was run a sfc /scannow, it picked up multiple corrupt files but said they had been repaired.

Previous to my system reinstall i was running this command and getting an unrepairable corrupt file windows\syswow64\opencl.dll, which appeared to be an unrelated issue to my network problem.

Anyway, the network issue still remained, even after a reboot, so I shut down the system and planned to do another clean install today. I figured that since i did the 'refresh my system' version of a clean install it was using files present on the HDD to do this and that is how there was still corruption, so I figured i would do another clean install using a DVD from pre-boot envrironment.

Booted up the system this morning, and the issue is gone....

I'm still going to do the DVD-based clean install later today.

What an infuriating problem!