At the office, I have several PCs running Win7 and two running Win8.1. The server runs Windows Server 2008. We're behind a UTM appliance by Untangled (including a firewall and Spam filter) and using Symantec Endpoint Protection for antivirus. Mysteriously, on August 18th, we stopped being able to check for Windows Updates. Every machine (including the server) shows 18 August as the most recent date checked, and 12 August as the last date that updates were installed. (This is true even when I have manually checked for updates.)
When I check for updates manually, I consistently get error 80072EE2. I have tried the simple solutions found online, including disabling both the UTM firewall and the SEP suite; still bupkis. (I also added all the Windows Update addresses to the exceptions list, just to be sure. It's worth noting that these are the same systems that have been in place for years without any changes, except for periodic definitions updates.) Windows Firewall is turned off.
I cannot ping update.microsoft.com from the command line. When I run a tracert I get out of my network, out to Time-Warner, into Microsoft's addresses, but die at that point. I get similar results with pathping, though the command times out at a slightly different Microsoft.com address. This further leads me to believe that this isn't a firewall problem.
Does anyone have any idea why this is happening, and how I can get the systems to update again?
When I check for updates manually, I consistently get error 80072EE2. I have tried the simple solutions found online, including disabling both the UTM firewall and the SEP suite; still bupkis. (I also added all the Windows Update addresses to the exceptions list, just to be sure. It's worth noting that these are the same systems that have been in place for years without any changes, except for periodic definitions updates.) Windows Firewall is turned off.
I cannot ping update.microsoft.com from the command line. When I run a tracert I get out of my network, out to Time-Warner, into Microsoft's addresses, but die at that point. I get similar results with pathping, though the command times out at a slightly different Microsoft.com address. This further leads me to believe that this isn't a firewall problem.
Does anyone have any idea why this is happening, and how I can get the systems to update again?