WSUS No longer registering clients

Check from the clients

http://wsusserver

you should get Under Construction page

if not then check port 80 is open for clients

I get I am not Authorized to view this page

what is the best way to check that it is set to port 80 for the default website. I think the name of this server might have been changed and it was updated so I am not sure if that could cause these issues. but I get I am not authorized to view this page

how do I check to make sure port 80 is open to clients

Telnet to port 80
 telnet <server IP> 80

I typed telnet at the command prompt and then I get microsoft telnet> then I type \\Server IP and then 80 and it just says connecting but it never connects. I am not sure what that means but it seems like it is not connecting how do I get IIS to accept connections on this port

is there any firewall between server and client, if it is... ask them to open any any rule

I shut down the firewall  on both systems the system has lots of locked downs and when I go into services to turn on telnet it will not start. Any other way to know if port 80 is accepting connections or how would I enable that setting?

I was able to get the telnet service started but it still does not seem to be connecting I even tried o localhost 80 on the server after starting telnet service and it just hangs at connecting. I am not be using telnet correctly

I used a o localecho 80 and received could not open connection to the host on port 80 connection failed from the server using telnet

Do you have any proxy for IE?

no proxy and I just got a connection failed typing telnet open \\192.168.10.57 80

I have an older vm build where this works all I did not add critical updates and the name was changed to the server but the IIS website is the same WSUS When I try to connect to the older VM windows update works so I am not what stopped it from working. When I check the setttings they all look the same but for some reason the client can't update and I get those error messages in event viewer

These errors have nothing to do with the clients, they are from a WSUS server misconfiguration.
 
Go over "Verifying WSUS server settings"
 
http://technet.microsoft.com/en-us/library/cc708545(WS.10).aspx 

Also go over....
 
http://www.microsoft.com/products/ee/transform.aspx?ProdName=.NET%20Framework&ProdVer=2.0.50727.42&EvtID=13042&EvtSrc=Windows%20Server%20Update%20Services&FileVer=2.0.50727.42&FileName=EventLogMessages.dll&EvtType=%E9%94%99%E8%AF%AF&LCID= 

I am going to try to uninstall WSUS and then reinstall it and hopefully it fixes whatever is broke if that does not work I will look to see if anything is miss configured

I received this error after reinstalling WSUS so maybe I need to reinstall IIS and SQL and WSUS



The WSUS administration console was unable to connect to the WSUS Server via the remote API.

Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service.

The WSUS administration console has encountered an unexpected error. This may be a transient error; try restarting the administration console. If this error persists,

Try removing the persisted preferences for the console by deleting the wsus file under %appdata%\Microsoft\MMC\.


System.IO.IOException -- The handshake failed due to an unexpected packet format.

Source
System

Stack Trace:
   at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
   at System.Net.TlsStream.CallProcessAuthentication(Object state)
   at System.Threading.ExecutionContext.runTryCode(Object userData)
   at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
   at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
   at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size)
   at System.Net.ConnectStream.WriteHeaders(Boolean async)
** this exception was nested inside of the following exception **


System.Net.WebException -- The underlying connection was closed: An unexpected error occurred on a send.

Source
Microsoft.UpdateServices.Administration

Stack Trace:
   at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)
   at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer(String serverName, Boolean useSecureConnection, Int32 portNumber)
   at Microsoft.UpdateServices.UI.AdminApiAccess.AdminApiTools.GetUpdateServer(String serverName, Boolean useSecureConnection, Int32 portNumber)
   at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.GetUpdateServer(PersistedServerSettings settings)
   at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ConnectToServer()
   at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.get_ServerTools()

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

I used that to remove and then reinstall and it is still jacked up. I have no idea I am about to remove IIS SQL and WSUS and try that. I get the same errors in the event viewer

I tried to reinstall and nothing seems to work it will not register workstations and when I try to access the web site I get you are not authorized to view this page but the rights look correct I

From a client, what are the results of clientdiag?
 
http://download.microsoft.com/download/9/7/6/976d1084-d2fd-45a1-8c27-a467c768d8ef/WSUS%20Client%20Diagnostic%20Tool.EXE
 
Also go over:
 
Troubleshooting guide for issues where WSUS clients are not reporting in

When I run WSUS Diag on the client and everything passed but the end that says verifyWUServerURL() failed with hr-0x800710dd
the operation identifier is not valid

It seems like there is a problem with the website or IIS and if I try to connect to the default website I get this

You are not authorized to view this page
You do not have permission to view this directory or page using the credentials that you supplied.
--------------------------------------------------------------------------------

Please try the following:

Contact the Web site administrator if you believe you should be able to view this directory or page.
Click the Refresh button to try again with different credentials.
HTTP Error 401.1 - Unauthorized: Access is denied due to invalid credentials.
Internet Information Services (IIS)

I checked out that one link and changed all the permissions and redid the IIS guest user password and it still does not work. I think ran the Authentication and Access Control Diagnostics and this is what I got back. Not sure but it looks like the anonymous user pass does not work

AnonymousPasswordSync
The current configuration uses IIS subauthentication for anonymous authentication. This requires that the worker process be configured to run as the Local System identity, which is not recommended for security reasons.Path:W3SVC/1/ROOT/Selfupdate
AuthType:Anonymous
Server's response: HTTP/1.1 401 Unauthorized
Learn about IIS status codesPath:W3SVC/1/ROOT/Selfupdate
AuthType:Anonymous
AnonymousUserPass
logon failedPath:W3SVC/1/ROOT/ServerSyncWebService
AuthType:Anonymous
AnonymousPasswordSync
The current configuration requires IIS subauthentication. However, the IIS subauthentication component, iissuba.dll, is not currently configured.Path:W3SVC/1/ROOT/ServerSyncWebService
AuthType:Anonymous
AnonymousPasswordSync
The current configuration uses IIS subauthentication for anonymous authentication. This requires that the worker process be configured to run as the Local System identity, which is not recommended for security reasons.Path:W3SVC/1/ROOT/ServerSyncWebService
AuthType:Anonymous
Server's response: HTTP/1.1 401 Unauthorized
Learn about IIS status codesPath:W3SVC/1/ROOT/ServerSyncWebService
AuthType:Anonymous
AnonymousUserPass
logon failedPath:W3SVC/1/ROOT/SimpleAuthWebService
AuthType:Anonymous
AnonymousPasswordSync
The current configuration requires IIS subauthentication. However, the IIS subauthentication component, iissuba.dll, is not currently configured.Path:W3SVC/1/ROOT/SimpleAuthWebService
AuthType:Anonymous
AnonymousPasswordSync
The current configuration uses IIS subauthentication for anonymous authentication. This requires that the worker process be configured to run as the Local System identity, which is not recommended for security reasons.Path:W3SVC/1/ROOT/SimpleAuthWebService
AuthType:Anonymous
Server's response: HTTP/1.1 401 Unauthorized
Learn about IIS status codesPath:W3SVC/1/ROOT/SimpleAuthWebService
AuthType:Anonymous
Diagnostics complete

Eveyrthing works now thanks