leco Posted June 9, 2010 Posted June 9, 2010 (edited) Fresh install of 2008 R2 on a 64bit vm (Hyper-V), activated, and running fine. All except Windows Update, which refuses to connect - error 80072efd. I've looked at all the info from MS, turned off the firewall, turned the firewall on, put all the MS sites into the trusted zone, put all the sites into the firewall exceptions list, turned the anti-virus off (though it wasn't even installed when I first tried to MS update). So what's stopping it from working? All manner of possibilities I imagine - anyone suggest places/things to check? Edited June 10, 2010 by leco
SYNACK Posted June 9, 2010 Posted June 9, 2010 Is it joined to the domain and grabbing policies that make it try and use a local WSUS server that is possible nonfunctional?
leco Posted June 9, 2010 Author Posted June 9, 2010 Is it joined to the domain and grabbing policies that make it try and use a local WSUS server that is possible nonfunctional? It is joined to the domain - it's a DC - so no it shouldn't be trying to get to the WSUS server. Although that was my next port of call to see if it was doing. I try to keep the DCs on a more controlled update rather than through the WSUS.
ranj Posted June 9, 2010 Posted June 9, 2010 Do you use a proxy? If so could be a proxy problem with Windows Update refusing to connect, way to test if you can bypass it.
leco Posted June 9, 2010 Author Posted June 9, 2010 Do you use a proxy? If so could be a proxy problem with Windows Update refusing to connect, way to test if you can bypass it. Sadly can't bypass the proxy - yhgfl is the only way out of the school.
Cache Posted June 9, 2010 Posted June 9, 2010 (edited) I think it's to do with the proxy. I have mine reporting to the WSUS and was getting the same error until I added it to the bypass list. Odd, because I haven't had to do it on any other servers before. Edit: Could possibly have a run through this and see if it picking the proxy up properly: http://support.microsoft.com/kb/900935/ Edited June 9, 2010 by Cache
leco Posted June 9, 2010 Author Posted June 9, 2010 My physical servers connect OK, I have another VM DC and that connects OK as well - just this latest one that's not playing.
sted Posted June 10, 2010 Posted June 10, 2010 if it anything like lln xp/2003 could connect to windows update but 2008/vista couldnt at one bit i think thats now fixed iirc but it may be lea and there may not be a lot you can do about it other than updating it via wsus (hich did work)
danrhodes Posted June 10, 2010 Posted June 10, 2010 Leco if your still having trouble try using Repair Tool of the Week: Offline Update | Technibble I've had to use it numerous times when WU refused to work properly! D
leco Posted June 10, 2010 Author Posted June 10, 2010 Leco if your still having trouble try using Repair Tool of the Week: Offline Update | Technibble I've had to use it numerous times when WU refused to work properly! D Thanks for this I'll have a go. sted: it may be lea I'll shoot off an email in the morning to check on that - thanks.
Stuart_C Posted June 10, 2010 Posted June 10, 2010 I always seen to have to add the windows update sites to the list of trusted sites in IE to get windows update to work. You'd think by default they'd be in there...
leco Posted June 10, 2010 Author Posted June 10, 2010 I think it's to do with the proxy. Edit: Could possibly have a run through this and see if it picking the proxy up properly: How the Windows Update client determines which proxy server to use to connect to the Windows Update Web site Whoo hoo used proxycfg to put in the proxy and it works:) Thank you so much it was driving me insane.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now