- Remove From My Forums
-
Question
-
Hello,
I am currently getting an error while WSUS tries to sync with microsoft update. WSUS is being controlled via SCCM 2012 in the scenario.
When manually starting a sync (scheduled sync is the same) I get the following error:
Sync failed: UssCommunicationError: WebException: The remote server returned an error: (403) Forbidden.~~at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context). Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS
I believe this to be related to either the proxy server or a firewall blocking the request. Could this be the case? I haven’t checked if I can reach the microsoft update site manually via IE, but I could verify general Internet access via IE, albeit a very
slow connection.Does anyone have an idea what else I could look at, to get to the bottom of this error and fix it?
Cheers,
Fred
Answers
-
Sync failed: UssCommunicationError: WebException: The remote server returned an error: (403) Forbidden.~~at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context). Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS
I believe this to be related to either the proxy server or a firewall blocking the request.
I would agree. Have you configured the proxy settings for the Software Update Point in the Configuration Manager console?
Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
SolarWinds Head Geek
Microsoft MVP — Software Distribution (2005-2012)
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.-
Marked as answer by
Thursday, January 31, 2013 2:56 AM
-
Marked as answer by
Microsoft Teams is a great way to communicate with your colleagues and customers, but in some cases you might run into an error message like ‘403’.
Tech Support 24/7
Ask a Tech Specialist Online
Connect with the Expert via email, text or phone. Include photos, documents, and more. Get step-by-step instructions from verified Tech Support Specialists.
On this page, you will find more information about the most common causes and most relevant solutions for the Microsoft Teams error ‘403’. Do you need help straight away? Visit our support page.
Error information
How to solve Microsoft Teams error 403
We’ve created a list of solutions which you can follow if you want to solve this Microsoft Teams problem yourself. Do you need more help? Visit our support page if you need professional support with Microsoft Teams right away.
Tech Support 24/7
Ask a Tech Specialist Online
Connect with the Expert via email, text or phone. Include photos, documents, and more. Get step-by-step instructions from verified Tech Support Specialists.
Have you found a solution yourself, but it is not in the list? Share your solution in the comments below.
Need more help?
Do you need more help?
Tech experts are ready to answer your questions.
Ask a question
Reason for 403 Error:
- The hosts file under «C:\Windows\System32\drivers\etc» is misconfigured.
- Your Antivirus or Firewall is causing issues.
- Error 403 can occur when you are making use of download assistant plugins or software with Windows Edge or other browsers.
- It could be so that the Windows Update Site Control is missing or is corrupt on your device.
You can get a 403 error, when you try to access the Windows 10/11/Server Software Update.
The 403 error can be of the below types.
HTTP 403 Access Unauthorized
Reasons:
How to fix Error 403
- Ad-blocker extension or plugins.
- Thirdy party antivirus software
- Web accelerators, Download assistants, or Security software.
-
Type %WinDir%\System32\Drivers\Etc in Run and open the location.
-
Rename the old hosts file to hosts_old
- Create a new file named hosts
- Copy the below text based on your Operating System type and save.
- https://learn.microsoft.com/en-us/troubleshoot/windows-client/deployment/error-403-connect-to-windows-update
- https://answers.microsoft.com/en-us/windows/forum/all/downloading-visio-this-error-http-403-forbidden/2d39ae42-2a0c-4343-b9e8-fc8f25688c40
- https://answers.microsoft.com/en-us/windows/forum/all/error-http-403-microsoft-edge-cannot-go-to-this/e0038757-a344-4cb5-a854-814ed158af67
Based on the reason for the error listed above, we can fix can be one of the following.
Disable Add-ons that can cause issues:
We can fix the Unauthorized/Access Denied/Forbidden errors by disabling third-party software like,
Reset the hosts file:
The host is a text file containing a map of hostnames and IP addresses. If this file is not configured correctly you may have problems accessing the internet.
Windows 11:
# Copyright (c) 1993-2006 Microsoft Corp. # # This is a sample HOSTS file used by Microsoft TCP/IP for Windows. # # This file contains the mappings of IP addresses to host names. Each # entry should be kept on an individual line. The IP address should # be placed in the first column followed by the corresponding host name. # The IP address and the host name should be separated by at least one # space. # # Additionally, comments (such as these) may be inserted on individual # lines or following the machine name denoted by a ‘#’ symbol. # # For example: # # 102.54.94.97 rhino.acme.com # source server # 38.25.63.10 x.acme.com # x client host # localhost name resolution is handle within DNS itself. # 127.0.0.1 localhost # ::1 localhost
Windows 10:
# Copyright (c) 1993-2006 Microsoft Corp. # # This is a sample HOSTS file used by Microsoft TCP/IP for Windows. # # This file contains the mappings of IP addresses to host names. Each # entry should be kept on an individual line. The IP address should # be placed in the first column followed by the corresponding host name. # The IP address and the host name should be separated by at least one # space. # # Additionally, comments (such as these) may be inserted on individual # lines or following the machine name denoted by a ‘#’ symbol. # # For example: # # 102.54.94.97 rhino.acme.com # source server # 38.25.63.10 x.acme.com # x client host # localhost name resolution is handle within DNS itself. # 127.0.0.1 localhost # ::1 localhost
Reference: https://support.microsoft.com/en-us/topic/how-to-reset-the-hosts-file-back-to-the-default-c2a43f9d-e176-c6f3-e4ef-3500277a6dae
Try different Internet Network
You can try the updates by connecting to a different internet connection.
You may find the below links helpful:
—