B
Bill
I think something is wrong with my previous post. I'm
unable to reply to it so here it goes again.
I have SUS configured on my network and have in the past
been able to successfully update the clients. I've
recently noticed the clients are no longer being updated.
The error
Unable to connect: Windows is unable to connect to the
Automatic Updates service and therefore cannot download
and install updates according to the set schedule. Windows
will continue to try to establish a connection.
appears in the clients system log, but I haven't found too
much out there regarding the error message. The sys log
of the SUS server looks OK otherwise. It shows updates
being downloaded from microsoft and that they are now
available for clients to install.
I've triple checked the configuration in the GPO and on
the sus server. I'm definately able to resolve the
hostname of the SUS server and I have reinstalled SUS.
The GPO is being applied to the machines, a gpresult kicks
back that it is being applied. IIS looks OK, I am able to
connect to a test site I've setup on the server. Is there
any other way I could verify that IIS or http is not the
culprit?
I've checked the windowsudate log and noticed it has been
trying to contact
https://v4.windowsupdate.microsoft.com/getmanifest.asp
instead of the SUS server. I've also checked the W3SVC
logs and see many of the following errors
2004-02-05 10:44:31 10.4.0.107 AU Self-Update Failed
80190191
thank you,
Bill
unable to reply to it so here it goes again.
I have SUS configured on my network and have in the past
been able to successfully update the clients. I've
recently noticed the clients are no longer being updated.
The error
Unable to connect: Windows is unable to connect to the
Automatic Updates service and therefore cannot download
and install updates according to the set schedule. Windows
will continue to try to establish a connection.
appears in the clients system log, but I haven't found too
much out there regarding the error message. The sys log
of the SUS server looks OK otherwise. It shows updates
being downloaded from microsoft and that they are now
available for clients to install.
I've triple checked the configuration in the GPO and on
the sus server. I'm definately able to resolve the
hostname of the SUS server and I have reinstalled SUS.
The GPO is being applied to the machines, a gpresult kicks
back that it is being applied. IIS looks OK, I am able to
connect to a test site I've setup on the server. Is there
any other way I could verify that IIS or http is not the
culprit?
I've checked the windowsudate log and noticed it has been
trying to contact
https://v4.windowsupdate.microsoft.com/getmanifest.asp
instead of the SUS server. I've also checked the W3SVC
logs and see many of the following errors
2004-02-05 10:44:31 10.4.0.107 AU Self-Update Failed
80190191
thank you,
Bill