Quantcast
Channel: WSUS forum
Viewing all articles
Browse latest Browse all 12874

No client computers have ever contacted the server.

$
0
0

My co-worker setup WSUS on a server that has since then died. WSUS was then set up on a different server. This one however tarted having issues so she fully uninstalled WSUS from that server and moved it to another server which is Windows Server 2016. This one now is having the issue of no computers showing up in the console. The GPO is set up right and is on all of the computers. The issue is that the computers can't seem to contact WSUS. 

2018/09/27 14:24:42.3121707 4208  14432 Misc            Got WSUS SimpleTargeting URL: http://wsus:8350""
2018/09/27 14:24:42.3144821 4208  14432 IdleTimer       WU operation (CAuthorizationCookieWrapper::InitializeSimpleTargetingCookie) started; operation # 79; does use network; is at background priority
2018/09/27 14:24:42.3144915 4208  14432 ProtocolTalker  Initializing simple targeting cookie, clientId = ec1643fd-7d11-4fc7-9c2e-851784936c97, target group = domainname, DNS name = computername.domainname
2018/09/27 14:24:42.3144934 4208  14432 ProtocolTalker    Server URL = http://wsus:8350/SimpleAuthWebService/SimpleAuth.asmx
2018/09/27 14:24:42.3145112 4208  14432 WebServices     Auto proxy settings for this web service call.
2018/09/27 14:24:44.3278185 4208  14432 WebServices     WS error: There was an error communicating with the endpoint at 'http://wsus:8350/SimpleAuthWebService/SimpleAuth.asmx'.
2018/09/27 14:24:44.3278479 4208  14432 WebServices     WS error: A connection with the server could not be established
2018/09/27 14:24:44.3279601 4208  14432 WebServices     *FAILED* [80240438] Web service call

The firewalls were turned off to try and help. I am not sure why it isn't working.




Viewing all articles
Browse latest Browse all 12874


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>