WSUS - Server 2012 R2
-
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 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. System.Net.Sockets.SocketException -- No connection could be made because the target machine actively refused it serverip:8530 Source System Stack Trace: at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress) at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception) ** this exception was nested inside of the following exception ** System.Net.WebException -- Unable to connect to the remote server Source Microsoft.UpdateServices.Administration Stack Trace: at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args) 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() -
I have seen that error or something similar from my workstation. It required deleting the cache for the mmc snapin.
-
Based on this my guess would be the firewall is block connections locally. . . .
-
Is the error when you run this from the console, or from RSAT tools from another machine?
-
@dustinb3403 said in WSUS - Server 2012 R2:
Based on this my guess would be the firewall is block connections locally. . . .
I agree. I would definitely disable the firewall to see if it resolves it.
-
@dashrender said in WSUS - Server 2012 R2:
Is the error when you run this from the console, or from RSAT tools from another machine?
Using the local console via RDP. Can't open WSUS and have it connect.
-
Yet this is saying the firewall isn't the issue. . .
And the firewall has exceptions for the WSUS ports. . .
-
I could delete the file at %appdata%\Microsoft\MMC called "wsus" but I don't know if that is actually the issue.
-
@dustinb3403 - If it isn't, the only problem is that you will have to recreate your custom update views, if you have any. So it won't hurt to try
Edit: These are what I am referring to -
-
@wrx7m said in WSUS - Server 2012 R2:
@dustinb3403 - If it isn't, the only problem is that you will have to recreate your custom update views, if you have any. So it won't hurt to try
Edit: These are what I am referring to -
Nope, removing the file simply removed the connection with MMC so now I don't even see the WSUS server (from which I'm running MMC and WSUS)
And I can't connect to the WSUS from MMC on this WSUS server. . . .
-
Not that I saw the server, but I saw the server and had the error in the OP.
-
Restoring the file gets me back to the error in the OP.
-
Open MMC, File Add/Remove Snap-in > update services..
Now you've created a new one.
-
@dashrender said in WSUS - Server 2012 R2:
Open MMC, File Add/Remove Snap-in > update services..
Now you've created a new one.
That works, but im still unable to connect to the WSUS server (localhost, or ip or by fqdn)
-
anything in the event log?
-
What is the status of the actual Windows Firewall service?
-
@dashrender said in WSUS - Server 2012 R2:
anything in the event log?
Try restarting IIS, SQL and update services
Which I've done and the error above in the code block.
-
@crustachio said in WSUS - Server 2012 R2:
What is the status of the actual Windows Firewall service?
Running
-
@dustinb3403 Try stopping it
-
