RE: WSUS Problems



Thank for you help. I have done all those things. How do I attach a file to
a post? I've a screen dump of my proxy settings but don't seem to have any
means to attach it.

However, despite that, it appears to have worked. I'm not sure which of the
steps you asked me to do, worked. I had alread done all the steps except
step (2) - I had used a qualified name, instead of an IP number (as per the
step-by-step guide which only talks about needing the "server's name" -
perhaps it might be a good idea to get this changed?) and step (5b).

Now, onto the next step which is at the client end!

Thanks again!



""Nathan Liu [MSFT]"" wrote:

> Hello Brian,
>
> Thank you for posting in the SBS newsgroup.
>
> According to your description, I understand that you received this error
> message "The remote server returned an error: (407) Proxy Authentication
> Required" on the SBS 2003 with WSUS Server. If I have misunderstood the
> problem, please don't hesitate to let me know.
>
> To narrow down this issue, please kindly check the following settings:
>
> 1. Open the ISA 2000 Management console on the SBS Server, right-click
> SBSServerName and select Properties, click "Outgoing Web Requests" tab,
> uncheck the "Ask unauthenticated users for identification" check box, and
> then click Apply and OK, then restart the Microsoft Firewall service, then
> check if the issue can be reproduced.
>
> 2. Please use the IP Address of the IE Proxy Server and not the FQDN or
> short name, and then try again.
>
> 3. Is the WSUS server trying to connect to an upstream server or
> Microsoft Update web site?
>
> 4. What is the port you used in Proxy Server configuration? Please take a
> screen shot for the Proxy Server configuration of WSUS and attach it in
> your reply.
>
> 5. In addition, I would like to suggest that you check on the proxy
> server to make sure the following settings are set correctly.
>
> a. Allowed the internal computers to access the following web site.
>
> http://windowsupdate.microsoft.com
> http://*.windowsupdate.microsoft.com
> https://*.windowsupdate.microsoft.com
> http://download.windowsupdate.com
> http://*.download.windowsupdate.com
> http://*.windowsupdate.com
> http://wustat.windows.com
> http://ntservicepack.microsoft.com
>
> So if your firewall / proxy needs authentication, you will need an
> exception for your WSUS server to access the above sites anonymously
>
> b. Enable HTTP 1.1
>
> c. Open port 80 and port 443
>
> If these are already allowed then try the following on the WSUS server:
>
> - Open Internet Explorer
> - Click on Tool
> - Click on Internet Options
> - Click on Advanced Tab
> - Check Used HTTP 1.1 through Proxy Connections
> - Close all instance of Internet Explorer and test again Let me know if
> this helps.
>
> You can also try to check Allow basic authentication (password in clear
> text) in the WSUS console option. What is the result?
>
> I am looking forward to your response.
>
> Have a nice day!
>
> Best regards,
>
> Nathan Liu (MSFT)
> Microsoft CSS Online Newsgroup Support
>
> Get Secure! - www.microsoft.com/security
> ======================================================
> This newsgroup only focuses on SBS technical issues. If you have issues
> regarding other Microsoft products, you'd better post in the corresponding
> newsgroups so that they can be resolved in an efficient and timely manner.
> You can locate the newsgroup here:
> http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
>
> When opening a new thread via the web interface, we recommend you check the
> "Notify me of replies" box to receive e-mail notifications when there are
> any updates in your thread. When responding to posts via your newsreader,
> please "Reply to Group" so that others may learn and benefit from your
> issue.
>
> Microsoft engineers can only focus on one issue per thread. Although we
> provide other information for your reference, we recommend you post
> different incidents in different threads to keep the thread clean. In doing
> so, it will ensure your issues are resolved in a timely manner.
>
> For urgent issues, you may want to contact Microsoft CSS directly. Please
> check http://support.microsoft.com for regional support phone numbers.
>
> Any input or comments in this thread are highly appreciated.
> ======================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
> --------------------
> >Thread-Topic: WSUS Problems
> >thread-index: AcYSRuDu2+iFFvH9R5yQGQciefmNsg==
> >X-WBNR-Posting-Host: 165.228.3.91
> >From: "=?Utf-8?B?QnJpYW4=?=" <Brian@xxxxxxxxxxxxxxxxxxxxxxxxx>
> >Subject: WSUS Problems
> >Date: Thu, 5 Jan 2006 14:25:05 -0800
> >Lines: 32
> >Message-ID: <74206970-37A8-4E7B-817B-DCCCE6D8F9B8@xxxxxxxxxxxxx>
> >MIME-Version: 1.0
> >Content-Type: text/plain;
> > charset="Utf-8"
> >Content-Transfer-Encoding: 7bit
> >X-Newsreader: Microsoft CDO for Windows 2000
> >Content-Class: urn:content-classes:message
> >Importance: normal
> >Priority: normal
> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> >Newsgroups: microsoft.public.windows.server.sbs
> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> >Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
> >Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.sbs:234434
> >X-Tomcat-NG: microsoft.public.windows.server.sbs
> >
> >I have recently started to install WSUS on our SBS 2003 Server. It seems
> to
> >install OK and when I configure it and start it synchonise, it comes up
> with
> >the following error each time:
> >
> >_________________
> >WebException: The underlying connection was closed: Unable to connect to
> the
> >remote server. ---> System.Net.WebException: The remote server returned an
> >error: (407) Proxy Authentication Required.
> >at System.Net.HttpWebRequest.CheckFinalStatus()
> > at System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult
> asyncResult)
> > at System.Net.HttpWebRequest.GetRequestStream()
> > at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
> >methodName, Object[] parameters)
> > at
> >Microsoft.UpdateServices.ServerSyncWebServices.ServerSync.ServerSyncProxy.G
> etAuthConfig()
> > at
> >Microsoft.UpdateServices.ServerSync.ServerSyncLib.InternetGetServerAuthConf
> ig(ServerSyncProxy proxy, WebServiceCommunicationHelper webServiceHelper)
> > at
> >Microsoft.UpdateServices.ServerSync.ServerSyncLib.Authenticate(Authorizatio
> nManager
> >authorizationManager, Boolean checkExpiration, ServerSyncProxy proxy,
> Cookie
> >cookie, WebServiceCommunicationHelper webServiceHelper)
> > at
> >Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.InternalGetConfig(
> )
> > at
> >Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.CatalogSyncThreadP
> rocessReal(Boolean allowRedirect)
> >
> >___________
> >
> >I have provided the correct authentication details for our ISA 2000
> server.
> >I have openned the correct ports on both it and our router. Surely
> >Microsoft isn't asking for authentication details? Why isn't it working?
> >
> >
>
>
.



Relevant Pages

  • RE: Proxy Server in SBS 2000
    ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ... Proxy Server in SBS 2000 ...
    (microsoft.public.windows.server.sbs)
  • Re: frontpage publishing error
    ... For a Microsoft FrontPage 2000 version of this article, ... A web does not exist at 'ftp location'. ... Could not find a web server at 'ftp location'. ... that the web server name is valid and your proxy settings are set correctly. ...
    (microsoft.public.frontpage.programming)
  • RE: ISA 2004 or GPOs?
    ... configure the client to use the address of the server ... as the Proxy Server, ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • RE: unable to ping server
    ... You may need to only type the server name of SBS as IE proxy server. ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • Re: ISA Server Problems, please help
    ... Based on the rules you have listed, SecureNAT clients should only be allowed ... The All access rule for SBS Internet Users ... Web Proxy and/or Firewall Client ... > header to the publishing server instead of the actual one. ...
    (microsoft.public.windows.server.sbs)