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.


Tuesday, 4 August 2015

Windows 10 upgrade

So we were away on 29th July and I had to wait until 2nd August before I could even think about getting my grubby mitts into the Windows 10 upgrade.

The first in line for an upgrade was my faithful war horse PC.  This PC is the "Triggers Broom" of PCs.  It was first purchased in about 2000 and it had Millenium installed!  Pausing so you can wipe the tears of laughter from your eyes.

It has been upgraded through XP, Windows 7, and now to 10. (Skipped over Vista, 8 and 8.1) Over the years it has had, in no particular order, new HDD & SSD.  New Optical drive, I upgraded the Motherboard and processor at one point and I have also replaced the PSU added RAM... and a new case, but it has been with me all these years.

I am writing this blog on it and it is now working fine upgraded to Windows 10.  There is a bit of back story including me being a little impatient and not waiting for the official release and upgrading to the Insider Preview version.  This version upgraded ok, but did not like it when I tried to upgrade to the full version.  I was a victim of the "explorer and cortana is not responding" critical error.

I had to reinstall Windows 7 from scratch and then update to windows 10.  I will gloss over the fact that I have now got to install all my applications again, but sometimes that's a good thing. It was due a clean out anyway.  But that is my desktop, I accumulate applications for this and that and sometimes don't uninstall them.

My Laptop on the other hand, was a bit of a "surprise - I'm upgrading to 10"  Still not entirely sure how it started.  I really wanted the desktop working first, but my laptop decided that it had all the necessary and was going with Windows update and was going off to Windows 10 land whether I liked it or not.  I registered for the upgrade almost the second it came out so I have only myself to blame.

It is working fine.  There have been some ID 10T errors from the k2c interface, but these are slowly being resolved, as I find out new stuff.

There are other Systems here at Lamas HQ and some of my clients have asked me to "do" the upgrade for them.  I have one sitting here beside me at 18%.  This client is firmly in the Hate Windows 8 camp.  (Laptop with no touchscreen!)  She did not want to wait any longer to get rid of 8.1 and upgrade to 10.

All in all it is going well so far.  I have no wisdom to impart as I have not really had any issues, other than those of my own making, so far.  Or maybe just one.  Custom Installation or you will be furnishing Microsoft with all of your personal browsing habits and application info.  Double check all the toggle switches about sending this that and the other bits of info out to all and sundry.

There will be more on the Lamas Windows 10 journey in the future as there are more systems to go!

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...