I had found that the error was related to the Windows Firewall but was unable to turn it on. It was the detail in your posting--to re-enable the feature via Services--that has resolved several...