Error 0x80072EE2 & MS Proxy Server

Ok, I think I've finally got some sort of handle on my error:

First, we have MS Proxy set up here, configured & filtered to restrict
access to the general user from most websites. The same box is also our
gateway NIC. WindowsUpdate is not restricted and works fine across the
board. V5 as well. All work, all fine, all good.

We have a couple machines set aside for unrestricted web browsing. We
"unrestrict" them by (shhhh) merely unchecking the "use proxy" box and just
using the proxy box ip as our gateway. Works fine, well, good. Except WU
v5.

The unrestricted machines receive the ole "Error 0x80072EE2." Note that if
we recheck the "use proxy" box then v5 works, so there is a fairly simple
workaround. Except I don't want a workaround.

The best I can come up with is there is some sort of config error on my part
in the gateway setup that is not allowing https 1.1 (which apparently v5
relies upon more heavily than v4?). Anybody have an idea what that may be,
or if I am even on the right track?

Thanks.

"Bob Wants No Spam" <> wrote in message
news:...
> access to the general user from most websites. The same box is also our
> gateway NIC.

Using the proxy as the Default gateway means nothing. Proxy2 is not a router
nor is it a NAT Device, so making it the Default Gateway means nothing.

> We have a couple machines set aside for unrestricted web browsing. We
> "unrestrict" them by (shhhh) merely unchecking the "use proxy" box and
just
> using the proxy box ip as our gateway. Works fine, well, good. Except WU
> v5.

They would have to have the WSP Client installed on the workstation with
unrestricted access or with access control simply turned off. When you
"uncheck" the box you are simply disabling the use of the Web Proxy Service
only,...this causes the Browser to "fall back" to using the Winsock Proxy
Service (via the WSP Client).

> The unrestricted machines receive the ole "Error 0x80072EE2." Note that
if
> we recheck the "use proxy" box then v5 works, so there is a fairly simple
> workaround. Except I don't want a workaround.

V5 probably works fine with the Web Proxy Service, but for some reason
cannot work with the Winsock Proxy Service. I have no answers for that. I
also know next to nothing about your topology and how your network is setup,
so there is no way I can be more specific than I am now.


--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

Thanks for restating the problem for me. Pretty much got that far myself.
Ok, current net setup is fairly simple. Think: server with 2 nics
(internal/external) & client. No internal DNS. Client points to internal
server address. TCP/IP, external DNS. Server has external connection. We
added proxy2 into this and install client software and filter for content
and destination. Clear as mud? Disabling proxy client (in any manner)
removes filtering.

And, apparently, WU v5.

WUv5 runs hand-in-hand with XPSP2 so before you ask, yes the firewall is
off. (Been trying to take this whole SP2 thing slow and steady watching for
what is going to break -- good so far, this is the biggest problem). Not
sure which network details here would be important. Near as I can tell the
only variables in this equation are SP2/WU v5 -- so that's where I'm
focusing my search. Did winsock get altered in some significant way for
SP2?

Thanks

"Phillip Windell" <@.> wrote in message
news:%235Zu%...
> "Bob Wants No Spam" <>
>> We have a couple machines set aside for unrestricted web browsing. We
>> "unrestrict" them by (shhhh) merely unchecking the "use proxy" box and
> just
>> using the proxy box ip as our gateway. Works fine, well, good. Except
>> WU
>> v5.
>
> They would have to have the WSP Client installed on the workstation with
> unrestricted access or with access control simply turned off. When you
> "uncheck" the box you are simply disabling the use of the Web Proxy
> Service
> only,...this causes the Browser to "fall back" to using the Winsock Proxy
> Service (via the WSP Client).
>
>> The unrestricted machines receive the ole "Error 0x80072EE2." Note that
> if
>> we recheck the "use proxy" box then v5 works, so there is a fairly simple
>> workaround. Except I don't want a workaround.
>
> V5 probably works fine with the Web Proxy Service, but for some reason
> cannot work with the Winsock Proxy Service. I have no answers for that. I
> also know next to nothing about your topology and how your network is
> setup,
> so there is no way I can be more specific than I am now.
>
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com

"Bob Wants No Spam" <> wrote in message
news:...
> (internal/external) & client. No internal DNS. Client points to internal
> server address. TCP/IP, external DNS. Server has external connection. We
> added proxy2 into this and install client software and filter for content
> and destination. Clear as mud? Disabling proxy client (in any manner)
> removes filtering.

Hmm..mud,..yes. I still get hung up on that "client points to internal
server address". There is no point in it. The proxy is not access in any
way by "gateway" settings. The clients could run blank gateways and still
function perfectly fine if the LAN is a single subnet LAN. It may be
something, it may be nothing,..it is just a "red flag" in my mind that is
all. Let's move on...

> WUv5 runs hand-in-hand with XPSP2 so before you ask, yes the firewall is
> off. (Been trying to take this whole SP2 thing slow and steady watching
for
> what is going to break -- good so far, this is the biggest problem).

Same here, SP2 is still in the "test bed".

> Not sure which network details here would be important.

Possibly none really. Clients find and authenticate with the Proxy based on
either the proxy settings in IE or by the WSP Client being install. The
network settings don't apply,..they just have to function properly on the
LAN that is all.

> Near as I can tell the
> only variables in this equation are SP2/WU v5 -- so that's where I'm
> focusing my search. Did winsock get altered in some significant way for
> SP2?

Ok, well,..There are differnces between HTTP1.1 and HTTP1.0. By default IE
will only use HTTP1.0 over a proxy even if it is using HTTP1.1 when on it's
own. So you want to adjust the browser (I think it is in the Advanced
settings) so that it uses "Use HTTP 1.1 through Proxy Connections". Here
are two KB articles that may apply to your situation.

Note that you must be using the Web Proxy Service (proxy settings in the
browser). If you are using only the Winsock Proxy Service (no proxy settings
in browser) the browser does not even know it is using a proxy and the
setting would not apply.

312955 - Windows Update May Not Work in Windows XP If an Authenticating Web
Proxy Is Used
http://support.microsoft.com/default...b;en-us;312955

836987 - You cannot gain access to the Windows Update Web site
http://support.microsoft.com/default...b;en-us;836987

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com