Will Microsoft sort this mess out

I have followed all the recommended routines to fix this problem(s) with no
joy. I have just received 3 new Dell laptops and they have they same problem
updated from the windows update, surely these new machines cannot be at
fault, it must be a Microsoft's end. I believe most people have tight
deadlines to meet and at this stage they must be bald.

You didn't mention what problem(s) you are referring to.

"Fed up" <Fed > wrote in message
news:E5D61A4B-07AF-4FC3-B9EF-...
|I have followed all the recommended routines to fix this problem(s) with no
| joy. I have just received 3 new Dell laptops and they have they same
problem
| updated from the windows update, surely these new machines cannot be at
| fault, it must be a Microsoft's end. I believe most people have tight
| deadlines to meet and at this stage they must be bald.

Fed up wrote:
> I have followed all the recommended routines to fix this problem(s) with no
> joy. I have just received 3 new Dell laptops and they have they same problem
> updated from the windows update, surely these new machines cannot be at
> fault, it must be a Microsoft's end. I believe most people have tight
> deadlines to meet and at this stage they must be bald.

Might help if you told us what problems you're having.

Alias

Just cannot connect via my network to V6 of MS Updates, I have found a work
around using V4 of MS updates
The main error I get is 0x80072F76 on about 10 machines that I have tried.
I don't if it is the combination of the following that causes the problem,
but it has only just started to happen since Tuesday of this week
(08/01/2006)
Netscreen F/W
McAfee Virus Scan
Websense
Regards

"Tom Willett" wrote:

> You didn't mention what problem(s) you are referring to.
>
> "Fed up" <Fed > wrote in message
> news:E5D61A4B-07AF-4FC3-B9EF-...
> |I have followed all the recommended routines to fix this problem(s) with no
> | joy. I have just received 3 new Dell laptops and they have they same
> problem
> | updated from the windows update, surely these new machines cannot be at
> | fault, it must be a Microsoft's end. I believe most people have tight
> | deadlines to meet and at this stage they must be bald.
>
>
>

I seem to be havig a similar problem mine stem from msoe.dll won't load after
upgrading from 2000 to xp I have followed the recommended fix with no result
have you heard any other ideas.

"Tom Willett" wrote:

> You didn't mention what problem(s) you are referring to.
>
> "Fed up" <Fed > wrote in message
> news:E5D61A4B-07AF-4FC3-B9EF-...
> |I have followed all the recommended routines to fix this problem(s) with no
> | joy. I have just received 3 new Dell laptops and they have they same
> problem
> | updated from the windows update, surely these new machines cannot be at
> | fault, it must be a Microsoft's end. I believe most people have tight
> | deadlines to meet and at this stage they must be bald.
>
>
>

Alias
Please view post 3

"--Alias--" wrote:

> Fed up wrote:
> > I have followed all the recommended routines to fix this problem(s) with no
> > joy. I have just received 3 new Dell laptops and they have they same problem
> > updated from the windows update, surely these new machines cannot be at
> > fault, it must be a Microsoft's end. I believe most people have tight
> > deadlines to meet and at this stage they must be bald.
>
> Might help if you told us what problems you're having.
>
> Alias
>

Fed up wrote:
> Alias
> Please view post 3

http://www.google.com/search?hl=en&q...=Google+Search

Alias
>
> "--Alias--" wrote:
>
>> Fed up wrote:
>>> I have followed all the recommended routines to fix this problem(s) with no
>>> joy. I have just received 3 new Dell laptops and they have they same problem
>>> updated from the windows update, surely these new machines cannot be at
>>> fault, it must be a Microsoft's end. I believe most people have tight
>>> deadlines to meet and at this stage they must be bald.
>> Might help if you told us what problems you're having.
>>
>> Alias
>>

Fed up <> wrote:

> Just cannot connect via my network to V6 of MS Updates, I have found
> a work around using V4 of MS updates
> The main error I get is 0x80072F76 on about 10 machines that I have
> tried. I don't if it is the combination of the following that causes
> the problem, but it has only just started to happen since Tuesday of
> this week (08/01/2006)
> Netscreen F/W
> McAfee Virus Scan
> Websense

When there are millions of Windows users world-wide successfully using
Windows Update, and nothing works on your particular network with Windows
Update, statistics might suggest that the problem lies with your network,
rather than with Microsoft.

You are running Websense and Netscreen, and either of those could obstruct
the correct operation of Windows Update, and the chances are that is
precisely what is happening.

The Windows Update world-wide network uses a pool of slave servers that can
change from time to time: maybe you have Websense/Netscreen configured to
allow access to last week's slave servers, and not this week's.

Some packet sniffing would show you exactly what was going on inside your
network when the HTTP requests fail.

See http://support.microsoft.com/kb/836941 for generic advice on error code
80072f76.

--
Robin Walker [MVP Networking]

"Robin Walker [MVP]" wrote:

> Fed up <> wrote:
>
> > Just cannot connect via my network to V6 of MS Updates, I have found
> > a work around using V4 of MS updates
> > The main error I get is 0x80072F76 on about 10 machines that I have
> > tried. I don't if it is the combination of the following that causes
> > the problem, but it has only just started to happen since Tuesday of
> > this week (08/01/2006)
> > Netscreen F/W
> > McAfee Virus Scan
> > Websense
>
> When there are millions of Windows users world-wide successfully using
> Windows Update, and nothing works on your particular network with Windows
> Update, statistics might suggest that the problem lies with your network,
> rather than with Microsoft.
>
> You are running Websense and Netscreen, and either of those could obstruct
> the correct operation of Windows Update, and the chances are that is
> precisely what is happening.
>
> The Windows Update world-wide network uses a pool of slave servers that can
> change from time to time: maybe you have Websense/Netscreen configured to
> allow access to last week's slave servers, and not this week's.
>
> Some packet sniffing would show you exactly what was going on inside your
> network when the HTTP requests fail.
>
> See http://support.microsoft.com/kb/836941 for generic advice on error code
> 80072f76.
>
> --
> Robin Walker [MVP Networking]
>
>
>
I have not changed any setting on the netscreen. I have made 1 adjustment on
the websense to allow an exe file through on Websense, this, after I started
to get these annoying messages from windowsupdate. It looks like (following
other posts and your replies) that I am not the only NetAdmin "Suffering"
with this problem. I asked a consultant who visited my site and he logged on
with his laptop, he got the same messages. But it does not happen to him from
his office. I will go down the packet sniffing route to see what I can find
out. But I still think this is a microsoft problem. Thanks for your honest
answer.

Let me get this straight. Someone brought there machine to your office, and
they had the same problem as your clients, but their machine works fine at
their Office. Plus you are running internet security filtering software that
is blocking access. I would think the security software companines would
have the proper configuration settings to use with MS Update Sites to allow
the updates through.

Maybe you should open up the filters to one device, and create a WSUS server
and your clients can download from your local WSUS server.

"Fed up" wrote:

> I asked a consultant who visited my site and he logged on with his laptop,
> he got the same messages. But it does not happen to him from his office.
> I will go down the packet sniffing route to see what I can fnd out. But I still think
> this is a Microsoft problem. Thanks for your honest answer.