Problems After Changing WSUS Port

Hello Everyone,

I am running a fresh install of Windows Server 2012.  I installed WSUS from server manager.  To the best of my memory, I was NOT asked which ports to use for WSUS.

I want to use custom ports for WSUS.  I went into IIS and I changed the bindings for the WSUS website.  After doing so, my server ran for days and didn't have problems.  My clients are actively checking in to my server and things look good.

But when I reboot my server, I am getting a lot of errors.  The primary error is shown below.  The most important thing is that there are still services attempting to connect to port 8530.  It looks like I have more work to do to change the port for WSUS.  What can I do to fix this error?  The port should NOT be 8530.

Thank you for your help.

-----------------------------------------

The WSUS content directory is not accessible.
System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 192.168.10.100:8530
   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)
   --- End of inner exception stack trace ---
   at System.Net.HttpWebRequest.GetResponse()
   at Microsoft.UpdateServices.Internal.HealthMonitoring.HmtWebServices.CheckContentDirWebAccess(EventLoggingType type, HealthEventLogger logger)

October 10th, 2013 1:32am

Hi,

Did you do follow steps:

1)Change the port on the WSUS website: go to IIS Manager>Server>Web Sites>Default Web Site (by default). Edit this to change the port to what you want.

2)Change the port in the client settings:(assuming settings through GPO) Go to computer config>administrative settings>Windows components>windows update>Specify Intranet Microsoft update service location. Change the address to include the new port (e.g. http://WSUSServer:8123)

In addition, please also refer to the below thread:

http://social.technet.microsoft.com/Forums/en-US/8907dd07-8cc2-4aec-b542-d52e4691ba1e/how-to-change-port-settings-in-wsus?forum=configmgrgeneral

Free Windows Admin Tool Kit Click here and download it now
October 11th, 2013 6:06am

Hi Yan Li,

Thank you for the message.  I just went and checked the bindings for the "Default Web Site" inside IIS.  While this site isn't what houses WSUS on my server I noticed that its only binding is port 80.  So this tells me that the error message on my server is not referencing this area because my error message references port 8530.  Having said this, there is another site on my server named "WSUS Administration".   I changed this port from 8530 to my new custom port (a week ago) and this is what started the error messages on my server :(  

Right now my clients are not having any errors--it's all server side.  I really appreciate the input, though!

October 11th, 2013 4:21pm

Ok, I believe I found a solution.  So far this seems to be working well and my error messages have gone away.  Here's what I did:

1. In IIS, add an ADDITIONAL binding for the custom port I want to use.  So I went to IIS > Sites > WSUS Administration > Edit Bindings and added my new port.

2. Because my server is listening on an additional port, I can use group policy and specify the new custom port on my clients.  My clients are checking in.  Also, because the default 8530 port is still active, my internal WSUS services are able to connect on this port and I'm no longer getting error messages.  

Also, it is worth noting that the Windows Server Firewall is blocking port 8530 so no computers can talk to the server on this port.  The 8530 port is only being used internally by IIS and WSUS.  My Windows Server Firewall is open, however, for my custom port.

So far this seems to be working well.  I'm thinking it probably isn't very typical, so if anyone sees any issues with this, I would like to hear about it.

  • Marked as answer by Roger CPAR Friday, October 11, 2013 4:25 PM
Free Windows Admin Tool Kit Click here and download it now
October 11th, 2013 4:25pm

Hi All,

Guess this post been posted for sometime. Having some IIS issue with Port 8530. When I did a binding on 8530 Example name it as WSUS when I click on browser the page does not appear. IP setting was set to unassigned address. Please enlighten on this issue

Thank & regards


Melvin
  • Edited by Melvin_C 2 hours 42 minutes ago
June 8th, 2015 12:20am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics