|
|
I have finally upgraded to WSUS 3.0 and basically have it going but it wont
synchronise with the Microsoft servers. My WSUS server accesses the Internet
via a Microsoft Proxy 2 box. I noted in the Readme that if you were using an
authenticating proxy (which it is) that you had to set the account password
even though it was brought over as part of the upgrade from WSUS 2.0. I have
done that but it has no effect on the sync failures. The actual error message
is as follows:-
WebException: The server committed a protocol violation.
Section=ResponseStatusLine
at System.Net.HttpWebRequest.GetReque stStream()
at System.Web.Services.Protocols.Soap HttpClientProtocol.Invoke(String
methodName, Object[] parameters)
at Microsoft.UpdateServices.ServerSyn cWebServices.ServerSync.ServerSyncÂ
Proxy.GetAuthConfig()
at Microsoft.UpdateServices.ServerSyn c.ServerSyncLib.InternetGetServerAÂ
uthConfig(ServerSyncProxy proxy, WebServiceCommunicationHelper
webServiceHelper)
at Microsoft.UpdateServices.ServerSyn c.ServerSyncLib.Authenticate(AuthoÂ
rizationManager authorizationManager, Boolean checkExpiration,
ServerSyncProxy proxy, Cookie cookie, WebServiceCommunicationHelper
webServiceHelper)
at Microsoft.UpdateServices.ServerSyn c.CatalogSyncAgentCore.SyncConfigUÂ
pdatesFromUSS()
at Microsoft.UpdateServices.ServerSyn c.CatalogSyncAgentCore.ExecuteSyncÂ
Protocol(Boolean allowRedirect)
Some error message huh!!!!!
Has anybody else seen this and know how to fix it? Apart from that the
upgrade seems to have gone well from the client side etc.
I have to say that I hate the new admin interface. It's slow and cumbersome
and of course it requires you to actually have it installed rather than
access it via a browser. WSUS 2 was a lot easier to administer.
|
|
"David Wales" <David Wales[ at ]discussions.microsoft.com> wrote in message
news:D6F1F159-20F8-4C9B-89CC-80274850C1B1[ at ]microsoft.com...
[Quoted Text] >I have finally upgraded to WSUS 3.0 and basically have it going but it wont
> synchronise with the Microsoft servers. My WSUS server accesses the
> Internet
> via a Microsoft Proxy 2 box.
!!!!!?????!!!!!!!
You *really* *really* need to upgrade that server!!!
> WebException: The server committed a protocol violation.
A "protocol violation"?
> Some error message huh!!!!!
The rest is programmer fluff... the key point is the first line.
> Has anybody else seen this and know how to fix it? Apart from that the
> upgrade seems to have gone well from the client side etc.
No.. but I can't say that I know anybody else who's running WSUS 3.0 (which
requires Windows Server 2003), and hasn't managed to upgrade their Microsoft
Proxy Server 2 to something newer than a ten year old firewall -- except
some places still running Windows NT and maybe a Windows 2000 server
somewhere.
Btw.. how secure do you feel your network is, running a ten year old
firewall?
Anyway.. I digress... as for the error.. and the "protocol violation"....
the first place to start is the old software, I'm afraid.
--
Lawrence Garvin, M.S., MCTS, MCP
Independent WSUS Evangelist
MVP-Software Distribution (2005-2007)
https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E
Everything you need for WSUS is at
http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx
And, almost everything else is at
http://wsusinfo.onsitechsolutions.com
.....
|
|
"Lawrence Garvin (MVP)" wrote:
[Quoted Text] > > via a Microsoft Proxy 2 box.
>
> !!!!!?????!!!!!!!
>
> You *really* *really* need to upgrade that server!!!
It is a very old PC running NT4 and it's only purpose in life is HTTP
proxying and website access filtering for our employees. Until now it has
done the job admirably. It worked perfectly with WSUS 2.0
> No.. but I can't say that I know anybody else who's running WSUS 3.0 (which
> requires Windows Server 2003), and hasn't managed to upgrade their Microsoft
> Proxy Server 2 to something newer than a ten year old firewall -- except
> some places still running Windows NT and maybe a Windows 2000 server
> somewhere.
All of our new servers are running Windows Server 2003 but the basic
infrastructure is still a Windows NT4 domain. It's been a classic case of
"If it aint broken don't fix it".
> Btw.. how secure do you feel your network is, running a ten year old
> firewall?
There has never been a breach that I am aware of and yes I do check. Note
that this box only does HTTP proxying so there are no other services running
on the box that are visible to the outside world that can be compromised.
> Anyway.. I digress... as for the error.. and the "protocol violation"....
> the first place to start is the old software, I'm afraid.
Upgrading the server hardware, paying for another Windows Server 2003
licence and then for something like ISA is not really an option for me at the
moment. I'm no UNIX guru either so one of the Linux type proxies isn't
really for me either.
If there is no way to make this work with MS Proxy 2 then it wont be the old
software that goes. It will be WSUS 3.0 that goes and I will move back to
WSUS 2.0.
I've asked this question in another forum as well and whilst I haven't got
an answer there are two other people with the same problem. I know that at
least one is also using MS Proxy 2. Not everybody constantly upgrades their
software just because new versions become available.
|
|
If it is only a Caching Server and not doing firewall stuff why don't you
configure the WSUS service to not use the Proxy 2.0 cache and go directly to the
Internet. I assume you have some other firewall so you may need to add a rule to
permit the WSUS server direct access on http and https.
On Fri, 1 Jun 2007 20:40:00 -0700, David Wales <David
Wales[ at ]discussions.microsoft.com> wrote:
[Quoted Text] >"Lawrence Garvin (MVP)" wrote:
>
>> > via a Microsoft Proxy 2 box.
>>
>> !!!!!?????!!!!!!!
>>
>> You *really* *really* need to upgrade that server!!!
>
>It is a very old PC running NT4 and it's only purpose in life is HTTP
>proxying and website access filtering for our employees. Until now it has
>done the job admirably. It worked perfectly with WSUS 2.0
>
>> No.. but I can't say that I know anybody else who's running WSUS 3.0 (which
>> requires Windows Server 2003), and hasn't managed to upgrade their Microsoft
>> Proxy Server 2 to something newer than a ten year old firewall -- except
>> some places still running Windows NT and maybe a Windows 2000 server
>> somewhere.
>
>All of our new servers are running Windows Server 2003 but the basic
>infrastructure is still a Windows NT4 domain. It's been a classic case of
>"If it aint broken don't fix it".
>
>> Btw.. how secure do you feel your network is, running a ten year old
>> firewall?
>
>There has never been a breach that I am aware of and yes I do check. Note
>that this box only does HTTP proxying so there are no other services running
>on the box that are visible to the outside world that can be compromised.
>
>> Anyway.. I digress... as for the error.. and the "protocol violation"....
>> the first place to start is the old software, I'm afraid.
>
>Upgrading the server hardware, paying for another Windows Server 2003
>licence and then for something like ISA is not really an option for me at the
>moment. I'm no UNIX guru either so one of the Linux type proxies isn't
>really for me either.
>
>If there is no way to make this work with MS Proxy 2 then it wont be the old
>software that goes. It will be WSUS 3.0 that goes and I will move back to
>WSUS 2.0.
>
>I've asked this question in another forum as well and whilst I haven't got
>an answer there are two other people with the same problem. I know that at
>least one is also using MS Proxy 2. Not everybody constantly upgrades their
>software just because new versions become available.
--
Dave Mills
There are 10 type of people, those that understand binary and those that don't.
|
|
"David Wales" <David Wales[ at ]discussions.microsoft.com> wrote in message
news:13E7577F-9B54-468A-BEC6-12B5A20C0A3D[ at ]microsoft.com...
[Quoted Text] > If there is no way to make this work with MS Proxy 2 then it wont be the
> old
> software that goes. It will be WSUS 3.0 that goes and I will move back to
> WSUS 2.0.
I'm not saying that it won't work with Microsoft Proxy Server v2, I'm saying
that nobody's going to be willing to help you troubleshoot that scenario.
Certainly I =cannot=.
You might as well rollback to WSUS 2.0 == if that worked. If you're not
able/willing to upgrade your =proxy= server (which is an optional component
in your network based on what you've written), then there seems to me no
real reason to worry about deploying WSUS 3.0 anyway. Of course, they're
going to pull the plug on WSUS 2 at some point in the future. Then what will
you do?
By the way ... the other solution, and the =BEST= solution as far as WSUS is
concerned is to BYPASS THE PROXY entirely!
Whyever would you want to run WSUS through a proxy server anyway????
> I've asked this question in another forum as well and whilst I haven't got
> an answer there are two other people with the same problem. I know that
> at
> least one is also using MS Proxy 2.
Well.... there's a clue for you.
> Not everybody constantly upgrades their
> software just because new versions become available.
No.. and those people usually have problems getting *new* applications to
work in their archaic environments, and generally, they find there's nobody
available to help them.
If a *client* came to me and wanted me to come onsite and troubleshoot a
problem involving Microsoft Proxy Server v2, or any other product that's
three or four revisions old, I'd price my rates so high that it would be
*cheaper* to upgrade to the latest version! That's how fanatical I am about
wasting my time working on archaic products that should have been upgraded
ten years earlier but the client was too cheap to invest in their business
when they *should* have.
--
Lawrence Garvin, M.S., MCTS, MCP
Independent WSUS Evangelist
MVP-Software Distribution (2005-2007)
https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E
Everything you need for WSUS is at
http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx
And, almost everything else is at
http://wsusinfo.onsitechsolutions.com
.....
|
|
|
|
On Jun 4, 6:15 pm, Harry Johnston <h...[ at ]scms.waikato.ac.nz> wrote:
[Quoted Text]
Are you still having the sync problem over proxy? This is the first
time I have ever posted to a group. I had the same problem and
finally got it resolved. Let me know if you have the problem and I'll
post the steps I took.
|
|
On Jun 7, 9:48 am, jenniferdh...[ at ]yahoo.com wrote:
[Quoted Text] > Are you still having the sync problem over proxy? This is the first
> time I have ever posted to a group. I had the same problem and
> finally got it resolved. Let me know if you have the problem and I'll
> post the steps I took.
Yes I am still having the problem. I tried another proxy (FreeProxy)
and it was able to successfully sync but it would not download any of
the files identified as being needed. The status just stays at
"0.00MB of X.XXMB downloaded" indefinitely. The funny thing is that
if I then change the proxy back to the MS Proxy 2 box it will
successfully download the required files. But of course the next time
it tries to sync it fails again. So at the moment I am leaving it set
to FreeProxy so it can sync and when I notice that it needs to
download files I temporarily set it back to MS Proxy 2, let it
download and switch back again. Obviously this is not ideal!!!
If you have a method of making WSUS 3.0 work with MS Proxy 2 properly
I'd love to hear about it.
|
|
|