Here is another piece of information that may be helpful. When i log onto
the Windows 2008 server and try to browse the internet using IE8 or Firefox,
i am unable to. But if i open the command prompt and ping our external DNS
entries, or perform nslookups on google.com, or update.microsoft.com, those
work just fine. Could their be a built in security setting in Server 2008
that is preventing the server from sycronizing with Microsoft's Update
servers?
"Zachary" <> wrote in message
news:...
> Yeah, it's already a role. What i have done is install the admin console
> on one of our windows 2003 servers, but now when i try to run through the
> configuration wizard i get this error when trying to syncronize to an
> upstream server, which i have set to Microsoft's update servers.
>
> Attached is the error.
>
> "Dave Mills" <> wrote in message
> news:...
>> Have you tried adding it as a role
>>
>> On Mon, 27 Jul 2009 14:13:53 -0500, "Zachary" <>
>> wrote:
>>
>>>I am attempting to install WSUS on Server 2008 64bit. Everytime i do i
>>>recieve this error. I have attempted the install using the default and
>>>custom web site options. I have also tried restarting the BITS service,
>>>and
>>>running an iis reset. I have restarted the sql 2005 express instance i
>>>have
>>>created for WSUS. I am about at wits end, i have never had a WSUS
>>>install
>>>be this troublesome. Any help is greatly apprciated.
>>>
>>>Log Name: Application
>>>Source: Windows Server Update Services
>>>Date: 7/27/2009 2:03:30 PM
>>>Event ID: 7032
>>>Task Category: None
>>>Level: Warning
>>>Keywords: Classic
>>>User: N/A
>>>Computer: AGRADC2.agraind.com
>>>Description:
>>>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 -- An operation on a socket could not
>>>be
>>>performed because the system lacked sufficient buffer space or because a
>>>queue was full 10.0.1.243:8530
>>>
>>>Source
>>>System
>>>
>>>Stack Trace:
>>> at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot,
>>>SocketAddress socketAddress)
>>> at System.Net.ServicePoint.ConnectSocketInternal(Bool ean
>>> connectFailure,
>>>Socket s4, Socket s6, Socket& socket, IPAddress& address,
>>>ConnectSocketState
>>>state, IAsyncResult asyncResult, Int32 timeout, 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.AdminPr oxy.CreateUpdateServer(Object[]
>>>args)
>>> at
>>> Microsoft.UpdateServices.Administration.AdminProxy .GetUpdateServer()
>>> at
>>>Microsoft.UpdateServices.UI.AdminApiAccess.Admi nApiTools.GetUpdateServer()
>>> at
>>>Microsoft.UpdateServices.UI.SnapIn.Wizards.OOBE .OOBEWizard.get_AdminApiTools()
>>> at
>>>Microsoft.UpdateServices.UI.SnapIn.Wizards.OOBE .OOBEWizard.get_ServerState()
>>> at
>>>Microsoft.UpdateServices.UI.SnapIn.Wizards.OOBE .OOBEWizard.SetNavigationItemEnabledStates()
>>> at
>>>Microsoft.UpdateServices.UI.SnapIn.Wizards.OOBE .OOBEWizard.OOBEWizardInitialize()
>>>
>> --
>> Dave Mills
>> There are 10 types of people, those that understand binary and those that
>> don't.
>
>
>
|
Similar Threads
Linear Mode
