spadge Posted January 19, 2016 Report post Posted January 19, 2016 I am trying to run synchronise software updates from the SCCM console and it is failing. The wsyncmgr.log indicates the following errors: Sync failed: UssCommunicationError: WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A socket operation was attempted to an unreachable network [2a01:111:f335:1792::a01]:443~~at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context). Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=EDITED SITE=EDITED PID=5356 TID=8596 GMTDATE=Tue Jan 19 15:58:35.816 2016 ISTR0="Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS" ISTR1="UssCommunicationError: WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A socket operation was attempted to an unreachable network [2a01:111:f335:1792::a01]:443~~at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 I have researched the error and it indicates a potential problem with a proxy server. However, the primary site server has direct access to the internet which I have confirmed by browsing the internet and allowing the inbuilt windows update to run on the 2012 R2 server (I haven't actually installed any updates). I cannot see anything being blocked by the firewall for either the primary site server or the server which hosts the SUP role. I have rebooted both servers which hasn't fixed the error. SUP is configured to use ports 8530 and 8531 with no proxy or upstream server specified. The updates are set to download from Microsoft directly. Before I remove the SUP role and WSUS database and start afresh I was wondering if there is anything else I can try. Quote Share this post Link to post Share on other sites More sharing options...
Peter van der Woude Posted January 19, 2016 Report post Posted January 19, 2016 Based on the log files it looks like it's trying to connect on port 443 though... Quote Share this post Link to post Share on other sites More sharing options...
spadge Posted January 19, 2016 Report post Posted January 19, 2016 Hi Peter, do you have any ideas what settings I could change? Quote Share this post Link to post Share on other sites More sharing options...
jorlando Posted January 19, 2016 Report post Posted January 19, 2016 Check your WSUS Console. It should tell you what port is being used. Might try 8531. (Administration > Site Configuration > Server and Site System Roles) Find the Software update point role and make sure the ports match WSUS settings. Quote Share this post Link to post Share on other sites More sharing options...
spadge Posted January 19, 2016 Report post Posted January 19, 2016 Thanks for your reply. The SUP is already configured to use 8530 and 8531. Quote Share this post Link to post Share on other sites More sharing options...
spadge Posted January 20, 2016 Report post Posted January 20, 2016 I have removed the SUP role, uninstalled WSUS from the server and deleted the SUSDB from the primary site server SQL installation. After reinstalling WSUS, SUP and database I am getting the same errors in wsyncmgr.log Sync failed: UssCommunicationError: WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A socket operation was attempted to an unreachable network [2a01:111:f307:1794::a01]:443~~at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context). Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS= SITE= PID=20524 TID=21192 GMTDATE=Wed Jan 20 12:45:43.300 2016 ISTR0="Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS" ISTR1="UssCommunicationError: WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A socket operation was attempted to an unreachable network [2a01:111:f307:1794::a01]:443~~at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 The WCM.log does not indicate any errors File notification triggered WCM Inbox. SMS_WSUS_CONFIGURATION_MANAGER 20/01/2016 12:39:03 20924 (0x51BC) Attempting connection to WSUS server: EDITED, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 20/01/2016 12:39:03 20924 (0x51BC) Successfully connected to server: EDITED, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 20/01/2016 12:39:03 20924 (0x51BC) Subscribed Update Categories <?xml version="1.0" ?>~~<Categories>~~ <Category Id="UpdateClassification:0fa1201d-4330-4fa8-8ae9-b877473b6441"><![CDATA[security Updates]]></Category>~~ <Category Id="UpdateClassification:28bc880e-0592-4cbf-8f95-c79b17911d5f"><![CDATA[update Rollups]]></Category>~~ <Category Id="UpdateClassification:68c5b0a3-d1a6-4553-ae49-01d3a7827828"><![CDATA[service Packs]]></Category>~~ <Category Id="UpdateClassification:cd5ffd1e-e932-4e3a-bf74-18bf0b1bbd83"><![CDATA[updates]]></Category>~~ <Category Id="UpdateClassification:e0789628-ce08-4437-be74-2495b842f43b"><![CDATA[Definition Updates]]></Category>~~ <Category Id="UpdateClassification:e6cf1350-c01b-414d-a61f-263d14d133b4"><![CDATA[Critical Updates]]></Category>~~</Categories> SMS_WSUS_CONFIGURATION_MANAGER 20/01/2016 12:39:03 20924 (0x51BC) Successfully inserted WSUS Enterprise Update Source object {28951FC5-158F-4652-B0E6-59A873ACA302} SMS_WSUS_CONFIGURATION_MANAGER 20/01/2016 12:39:03 20924 (0x51BC) Configuration successful. Will wait for 1 minute for any subscription or proxy changes SMS_WSUS_CONFIGURATION_MANAGER 20/01/2016 12:39:03 20924 (0x51BC) Setting new configuration state to 2 (WSUS_CONFIG_SUCCESS) SMS_WSUS_CONFIGURATION_MANAGER 20/01/2016 12:40:03 20924 (0x51BC) Waiting for changes for 20 minutes SMS_WSUS_CONFIGURATION_MANAGER 20/01/2016 12:40:03 20924 (0x51BC) Trigger event array index 1 ended. SMS_WSUS_CONFIGURATION_MANAGER 20/01/2016 12:40:03 20924 (0x51BC) File notification triggered. SMS_WSUS_CONFIGURATION_MANAGER 20/01/2016 12:40:03 20924 (0x51BC) File notification triggered WCM Inbox. SMS_WSUS_CONFIGURATION_MANAGER 20/01/2016 12:40:08 20924 (0x51BC) Waiting for changes for 20 minutes SMS_WSUS_CONFIGURATION_MANAGER 20/01/2016 12:40:08 20924 (0x51BC) Trigger event array index 1 ended. SMS_WSUS_CONFIGURATION_MANAGER 20/01/2016 12:40:08 20924 (0x51BC) File notification triggered. SMS_WSUS_CONFIGURATION_MANAGER 20/01/2016 12:40:08 20924 (0x51BC) File notification triggered WCM Inbox. SMS_WSUS_CONFIGURATION_MANAGER 20/01/2016 12:40:13 20924 (0x51BC) Waiting for changes for 20 minutes SMS_WSUS_CONFIGURATION_MANAGER 20/01/2016 12:40:13 20924 (0x51BC) Would appreciate any comments on how to proceed next. Quote Share this post Link to post Share on other sites More sharing options...
spadge Posted January 20, 2016 Report post Posted January 20, 2016 fixed, issue was the SUP server not having access to the internet. Firewall rule change since the last time I sync'd the catalogue! sorry for wasting anyone's time. 1 Quote Share this post Link to post Share on other sites More sharing options...