Sync failed: unable to resolve the specified upstream server

[Anatoly Nazarenko]

Hello !

I have 2 Win2k3 (+SP2) servers with WSUS 3.0. One of them (e.g.
server1.mydomain) downloads updates from the Microsoft site, second (e.g.
server2.mydomain) was configured as a downstream server (not a replica).
Upstream works well, without any errors. But I have got the synchronization
error message from the downstream:
----------
Status: Failed
Result: Unable to resolve the specified upstream server. Details ->
----------
WebException: The request failed with HTTP status 404: Not Found.
at
System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
methodName, Object[] parameters)
at
Microsoft.UpdateServices.ServerSyncWebServices.ServerSync.ServerSyncProxy.GetAuthConfig()
at
Microsoft.UpdateServices.ServerSync.ServerSyncLib.InternetGetServerAuthConfig(ServerSyncProxy proxy, WebServiceCommunicationHelper webServiceHelper)
at
Microsoft.UpdateServices.ServerSync.ServerSyncLib.Authenticate(AuthorizationManager
authorizationManager, Boolean checkExpiration, ServerSyncProxy proxy, Cookie
cookie, WebServiceCommunicationHelper webServiceHelper)
at
Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.SyncConfigUpdatesFromUSS()
at
Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ExecuteSyncProtocol(Boolean allowRedirect)
-------
My synchronization options:
Server name: server1.mydomain
Port number: 80

Servers are in the same network without proxies, firewalls etc. (server1 -
domain controller, server2 - standalone, workgroup member). Ping from server2
to the server1.mydomain works fine, nslookup server1.mydomain shows correct
IP address. WWW service on the server1 is working (default server, port 80).

[Lawrence Garvin (MVP)]

Post by Anatoly Nazarenko
I have 2 Win2k3 (+SP2) servers with WSUS 3.0. One of them (e.g.
server1.mydomain) downloads updates from the Microsoft site, second (e.g.
server2.mydomain) was configured as a downstream server (not a replica).
Upstream works well, without any errors. But I have got the
synchronization
----------
Status: Failed
Result: Unable to resolve the specified upstream server. Details ->
----------
WebException: The request failed with HTTP status 404: Not Found.

The simple answer here is that server2.mydomain cannot find the desired
resources at server1.mydomain because the configured destination hostname is
not being resolved, by *WSUS*, to the correct IP Address.

Post by Anatoly Nazarenko
Server name: server1.mydomain
Port number: 80
Servers are in the same network without proxies, firewalls etc. (server1 -
domain controller, server2 - standalone, workgroup member).
Ping from server2 to the server1.mydomain works fine,
nslookup server1.mydomain shows correct IP address.
WWW service on the server1 is working (default server, port 80).

One gotcha that sometimes affects these type of diagnostics is that while
'nslookup' may return valid information, the internal calls through the APIs
to resolve a hostname to an IP Address may not be working correctly.

Using Internet Explorer on server2, can you successfully browse to these
URLs?

http://server1.mydomain/iuident.cab

http://server1.mydomain/simpleauthwebservice/simpleauth.asmx

http://server1.mydomain/serversyncwebservice/serversyncwebservice.asmx
--
Lawrence Garvin, M.S., MCTS, MCP
Independent WSUS Evangelist
MVP-Software Distribution (2005-2007)
https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E

Everything you need for WSUS is at
http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx

And, almost everything else is at
http://wsusinfo.onsitechsolutions.com
....

[Play-Doh]

On Jun 9, 6:31 pm, "Lawrence Garvin \(MVP\)"

Post by Lawrence Garvin (MVP)

I have 2 Win2k3 (+SP2) servers withWSUS3.0. One of them (e.g.
server1.mydomain) downloads updates from the Microsoft site, second (e.g.
server2.mydomain) was configured as a downstreamserver(not a replica).
Upstreamworks well, without any errors. But I have got the
synchronization
----------
Status: Failed
Result:Unabletoresolvethespecifiedupstreamserver. Details ->
----------
WebException: The request failed with HTTP status 404: Not Found.

The simple answer here is that server2.mydomain cannot find the desired
resources at server1.mydomain because the configured destination hostname is
not being resolved, by *WSUS*, to the correct IP Address.

Servername: server1.mydomain
Port number: 80
Servers are in the same network without proxies, firewalls etc. (server1 -
domain controller, server2 - standalone, workgroup member).
Ping from server2 to the server1.mydomain works fine,
nslookup server1.mydomain shows correct IP address.
WWW service on the server1 is working (defaultserver, port 80).

One gotcha that sometimes affects these type of diagnostics is that while
'nslookup' may return valid information, the internal calls through the APIs
toresolvea hostname to an IP Address may not be working correctly.
Using Internet Explorer on server2, can you successfully browse to these
URLs?
http://server1.mydomain/iuident.cab
http://server1.mydomain/simpleauthwebservice/simpleauth.asmx
http://server1.mydomain/serversyncwebservice/serversyncwebservice.asmx
--
Lawrence Garvin, M.S., MCTS, MCP
IndependentWSUSEvangelist
MVP-Software Distribution (2005-2007)https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D09...
Everything you need forWSUSis athttp://technet2.microsoft.com/windowsserver/en/technologies/featured/...
And, almost everything else is athttp://wsusinfo.onsitechsolutions.com
....

Is there an actual answer for this problem? I started having it
today, right after I upgraded to 3.0. I can browse successfully to
the first URL in your list, but none of the others.

[Play-Doh]

Post by Play-Doh
On Jun 9, 6:31 pm, "Lawrence Garvin \(MVP\)"

Post by Lawrence Garvin (MVP)

I have 2 Win2k3 (+SP2) servers withWSUS3.0. One of them (e.g.
server1.mydomain) downloads updates from the Microsoft site, second (e.g.
server2.mydomain) was configured as a downstreamserver(not a replica).
Upstreamworks well, without any errors. But I have got the
synchronization
----------
Status: Failed
Result:Unabletoresolvethespecifiedupstreamserver. Details ->
----------
WebException: The request failed with HTTP status 404: Not Found.

The simple answer here is that server2.mydomain cannot find the desired
resources at server1.mydomain because the configured destination hostname is
not being resolved, by *WSUS*, to the correct IP Address.

Servername: server1.mydomain
Port number: 80
Servers are in the same network without proxies, firewalls etc. (server1 -
domain controller, server2 - standalone, workgroup member).
Ping from server2 to the server1.mydomain works fine,
nslookup server1.mydomain shows correct IP address.
WWW service on the server1 is working (defaultserver, port 80).

One gotcha that sometimes affects these type of diagnostics is that while
'nslookup' may return valid information, the internal calls through the APIs
toresolvea hostname to an IP Address may not be working correctly.
Using Internet Explorer on server2, can you successfully browse to these
URLs?
http://server1.mydomain/iuident.cab
http://server1.mydomain/simpleauthwebservice/simpleauth.asmx
http://server1.mydomain/serversyncwebservice/serversyncwebservice.asmx
--
Lawrence Garvin, M.S., MCTS, MCP
IndependentWSUSEvangelist
MVP-Software Distribution (2005-2007)https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D09...
Everything you need forWSUSis athttp://technet2.microsoft.com/windowsserver/en/technologies/featured/...
And, almost everything else is athttp://wsusinfo.onsitechsolutions.com
....

Is there an actual answer for this problem? I started having it
today, right after I upgraded to 3.0. I can browse successfully to
the first URL in your list, but none of the others.- Hide quoted text -
- Show quoted text -

Found my problem. I just had to change the web port of the upstream
server in the sync options. There was an antiquated website no longer
in use still using that port.