Wednesday, 26 August 2015

Windows cannot automatically bind the IP protocol stack Windows 10 Update

Recently completed the Network Managers upgrade to Windows 10.

Dell Inspiron 1545.  It arrived with Windows 7 on it.  

The first time I upgraded it errored out, rebooted and restored Windows 7.  The reason for this was I had over estimated the battery power.  It is not as good as it used to be.  (insert Ronnie Corbett-esque anecdote about laptop batteries?...maybe another time)

I tried again with the laptop running on the mains power and it completed.

There was however, an issue with the Ethernet and Wi-Fi.

Due to the age of the laptop Dell do not provide updated drivers for Windows 10 so I reinstalled the Windows 7 drivers.  They apparently installed with no issue, but it was still not working and not making the connection to the internet.

I ran a diagnostic on the network connections and the result was:
"Windows cannot automatically bind the IP protocol stack to the network adapter"
The reason for this was, installed on the adapter configuration were some items that were not required.

Control Panel -->  Network and Sharing Centre --> Change adapter Settings --> Right Click on the adapter name and select Properties.  The window below will appear or something very much like it

The items that should be checked are:
  • Client for Microsoft Networks
  • File and Printer Sharing for Microsoft Networks
  • QoS Packet Scheduler
  • Internet Protocol Version 4 (TCP/IPv4
  • Internet Protocol Version 6 (TCP/IPv6)
  • Link Layer Topology Discovery Mapper I/O Driver
  • Link Layer Topology Discovery Responder.
Uncheck anything else.

The culprit, it seems, on the Dell Inspiron, was Microsoft LLDP Protocol Driver.  It was checked. 

It was then unchecked and the adapter was disabled and then re-enabled and then it was finally able to connect to the internet.

There are other reasons that it may not work, one is an unsupported VPN application or connection.  I made sure that anything of this nature was removed from the laptop, but in this case it was the MS LLDP Protocol Driver.

Sadly, I cannot remember or find the site that this useful information came from and I do like to give credit where credit is due.  If I do find it I will add the link to the site as the discussion it came from did give other solutions if this was unsuccessful.

Other reasons could include :
  • the Ethernet cable may not be plugged in correctly
  • Firewall or AV software may need to be temporarily disabled.
  • Unsupported VPN software.


No comments:

Post a comment

Blue Keep Bluekeep what is it?

Patch early and Patch often! Microsoft is continually sending out patches and security updates. These should be applied as soon as possibl...