PRicho Posted November 14, 2008 Posted November 14, 2008 As titled really, last successful sync was on the 3rd of Nov, and then it just fails, error says unable to resolve the specified upstream server name, which is set to be sync directly with microsoft updates. It goes out directly on our proxy.. nothings changed there.. whats the beef!?
Michael Posted November 14, 2008 Posted November 14, 2008 Instead of using/specifying an upstream server, try using another proxy. In WSUS 2.0 and 3.0 you can also specify a username and password (if you need to authenticate).
PRicho Posted November 14, 2008 Author Posted November 14, 2008 its set to use our ISP proxy (proxy.embc.org.uk) also tried the alternative proxy.embc.uk.com.. and ive also tried our internal proxy which does require authentication, in the logs i can see it trying to query the MS update site but that route still doesnt work. Anybody know the address of an alternative Update Server? Few peeps here with the same issue, WSUS server synchronization failed in microsoft.public.windows.server.update_services
7andY Posted November 18, 2008 Posted November 18, 2008 Do you use MSSQLExpress? I did until recently, when it ran out of room and stopped updating! I had a spare SQL2005 licence so I used that. Try doing some WSUS housekeeping. That will clear some space in SQL, and then try a manual update. Cheers, 7&Y
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