Could you expand a bit on this BITS dns bug that you've been told about?

What was your source for this information?

I'm not aware of any such bugs, nor am I aware of any need to be making
entries in the hosts file in order to get to a regional windowsupdate site.


"Lude" <Lude@discussions.microsoft.com> wrote in message
news:0D227016-7074-4FF2-92E2-F5E70F439505@microsoft.com...
>I found out what the problem is. I had to install the latest version of the
> windows upate client from
> http://download.windowsupdate.com/v6...gent20-x86.exe
>
> And then I had to make this entry in my hosts file:
> 207.46.245.220 au.download.windowsupdate.com because bits 2.0 has a dns bug.
> Thanks for all your help and I hope this will help anyone with the same type
> of problem.
>
> Thanks!
>
> "Lawrence Garvin [MVP]" wrote:
>
>>
>> "Lude" <Lude@discussions.microsoft.com> wrote in message
>> news:8FE1EAB9-4E68-4E74-9157-2A5DA4F33168@microsoft.com...
>> > Some more info: I'm not using a WSUS server and am using a automatic
>> > configuration script that points to a proxy. Maybe bits can't use the
>> > config
>> > script?
>>
>> This could be the issue.
>>
>> While the auto config script may properly configure IE, it will not
>> configure
>> WinHTTP.
>>
>> You should try the command 'proxycfg -u' to replicate your IE proxy
>> settings
>> to WinHTTP, and then try AU again.
>>
>> Alternatively, run the Client Diagnostic Tool on the client, and review the
>> output. Post the output if you'd like assistance interpreting the results.
>>
>>
>>

I got this info on bits from:
http://www.archivum.info/microsoft.p.../msg00067.html

"Lawrence Garvin [MVP]" wrote:

>
> Could you expand a bit on this BITS dns bug that you've been told about?
>
> What was your source for this information?
>
> I'm not aware of any such bugs, nor am I aware of any need to be making
> entries in the hosts file in order to get to a regional windowsupdate site.
>
>
> "Lude" <Lude@discussions.microsoft.com> wrote in message
> news:0D227016-7074-4FF2-92E2-F5E70F439505@microsoft.com...
> >I found out what the problem is. I had to install the latest version of the
> > windows upate client from
> > http://download.windowsupdate.com/v6...gent20-x86.exe
> >
> > And then I had to make this entry in my hosts file:
> > 207.46.245.220 au.download.windowsupdate.com because bits 2.0 has a dns bug.
> > Thanks for all your help and I hope this will help anyone with the same type
> > of problem.
> >
> > Thanks!
> >
> > "Lawrence Garvin [MVP]" wrote:
> >
> >>
> >> "Lude" <Lude@discussions.microsoft.com> wrote in message
> >> news:8FE1EAB9-4E68-4E74-9157-2A5DA4F33168@microsoft.com...
> >> > Some more info: I'm not using a WSUS server and am using a automatic
> >> > configuration script that points to a proxy. Maybe bits can't use the
> >> > config
> >> > script?
> >>
> >> This could be the issue.
> >>
> >> While the auto config script may properly configure IE, it will not
> >> configure
> >> WinHTTP.
> >>
> >> You should try the command 'proxycfg -u' to replicate your IE proxy
> >> settings
> >> to WinHTTP, and then try AU again.
> >>
> >> Alternatively, run the Client Diagnostic Tool on the client, and review the
> >> output. Post the output if you'd like assistance interpreting the results.
> >>
> >>
> >>
>
>
>

Well... that link was totally unreadable.... there seems to be some incredible
corruption in the databases at this site..

Any chance you have a Google Groups link?

Or could /post/ the text that you're working from?


"Lude" <Lude@discussions.microsoft.com> wrote in message
news:F1D70E4D-96B3-484C-B708-8B1752A60B2D@microsoft.com...
>I got this info on bits from:
> http://www.archivum.info/microsoft.p.../msg00067.html
>
> "Lawrence Garvin [MVP]" wrote:
>
>>
>> Could you expand a bit on this BITS dns bug that you've been told about?
>>
>> What was your source for this information?
>>
>> I'm not aware of any such bugs, nor am I aware of any need to be making
>> entries in the hosts file in order to get to a regional windowsupdate site.
>>
>>
>> "Lude" <Lude@discussions.microsoft.com> wrote in message
>> news:0D227016-7074-4FF2-92E2-F5E70F439505@microsoft.com...
>> >I found out what the problem is. I had to install the latest version of
>> >the
>> > windows upate client from
>> > http://download.windowsupdate.com/v6...gent20-x86.exe
>> >
>> > And then I had to make this entry in my hosts file:
>> > 207.46.245.220 au.download.windowsupdate.com because bits 2.0 has a dns
>> > bug.
>> > Thanks for all your help and I hope this will help anyone with the same
>> > type
>> > of problem.
>> >
>> > Thanks!
>> >
>> > "Lawrence Garvin [MVP]" wrote:
>> >
>> >>
>> >> "Lude" <Lude@discussions.microsoft.com> wrote in message
>> >> news:8FE1EAB9-4E68-4E74-9157-2A5DA4F33168@microsoft.com...
>> >> > Some more info: I'm not using a WSUS server and am using a automatic
>> >> > configuration script that points to a proxy. Maybe bits can't use the
>> >> > config
>> >> > script?
>> >>
>> >> This could be the issue.
>> >>
>> >> While the auto config script may properly configure IE, it will not
>> >> configure
>> >> WinHTTP.
>> >>
>> >> You should try the command 'proxycfg -u' to replicate your IE proxy
>> >> settings
>> >> to WinHTTP, and then try AU again.
>> >>
>> >> Alternatively, run the Client Diagnostic Tool on the client, and review
>> >> the
>> >> output. Post the output if you'd like assistance interpreting the
>> >> results.
>> >>
>> >>
>> >>
>>
>>
>>

Hi,

Google Groups link:
http://groups.google.com/group/micro...59999e68e88b62



Lawrence Garvin [MVP] wrote:

> Well... that link was totally unreadable.... there seems to be some incredible
> corruption in the databases at this site..
>
> Any chance you have a Google Groups link?
>
> Or could /post/ the text that you're working from?
>
>
> "Lude" <Lude@discussions.microsoft.com> wrote in message
> news:F1D70E4D-96B3-484C-B708-8B1752A60B2D@microsoft.com...
>
>>I got this info on bits from:
>>http://www.archivum.info/microsoft.p.../msg00067.html
>>
>>"Lawrence Garvin [MVP]" wrote:
>>
>>
>>>Could you expand a bit on this BITS dns bug that you've been told about?
>>>
>>>What was your source for this information?
>>>
>>>I'm not aware of any such bugs, nor am I aware of any need to be making
>>>entries in the hosts file in order to get to a regional windowsupdate site.
>>>
>>>
>>>"Lude" <Lude@discussions.microsoft.com> wrote in message
>>>news:0D227016-7074-4FF2-92E2-F5E70F439505@microsoft.com...
>>>
>>>>I found out what the problem is. I had to install the latest version of
>>>>the
>>>>windows upate client from
>>>>http://download.windowsupdate.com/v6...gent20-x86.exe
>>>>
>>>>And then I had to make this entry in my hosts file:
>>>>207.46.245.220 au.download.windowsupdate.com because bits 2.0 has a dns
>>>>bug.
>>>>Thanks for all your help and I hope this will help anyone with the same
>>>>type
>>>>of problem.
>>>>
>>>>Thanks!
>>>>



--
torgeir, Microsoft MVP Scripting, Porsgrunn Norway
Administration scripting examples and an ONLINE version of
the 1328 page Scripting Guide:
http://www.microsoft.com/technet/scr...r/default.mspx

"Torgeir Bakken (MVP)" <Torgeir.Bakken-spam@hydro.com> wrote in message
news:uoqUdTC7FHA.1484@tk2msftngp13.phx.gbl...
> Hi,
>
> Google Groups link:
> http://groups.google.com/group/micro...59999e68e88b62


I don't know what Lawrence's problem with Lude's link was
but I'm glad you posted a link to the whole thread.
The following reply from Narayana Mahankali [MSFT]
documents some diagnostic possibilities I wasn't aware of.


Thanks.

Robert Aldwinckle
---

Thank you Torgeir.


Now, Lude, let's talk about the reality of this thread you've cited.

1. Rene Zimmerman reported that his system was sitting behind a NetCache proxy
server, which Scott White [MSFT] had previously reported is causing problems
by stripping the RPHs that BITS requires in order to download update content.

2. Rene Zimmerman reported that /he/ looked at the BITS queue and discovered
that he was receiving an 0x80072afa error code trying to download updates.
Which the BITS output reports is "usually a temporary error during hostname
resolution and means that the local server did not receive a response from an
authoritative server."

a. BITS reports this is "usually" the reason for the '2afa' error. (But it
is not the /only/ cause.)
b. Rene already acknowledge he's using a proxy server with /known/ issues
processing RPHs.
c. Rene acknowledged that he was able to access the URL via Internet
Explorer, but NOT via BITS and WSUS.
d.

3. Thirty minutes later Rene posted that he 'fixed' his problem by adding an
entry to the HOSTS file for 'au.windowsupdate.microsoft.com', restarted the
server, and WSUS began downloading the updates. And (erroneously) then
concluded there must be a BUG in BITS 2.0 -- even after being told there was a
/known/ issue in the proxy server (NetCache) that was directly interfering
with this problem.

4. Narayana Manankali [MSFT] posted in response and asked several valid
questions with respect to Rene's reported isuse. Rene never posted back.

Rene's response is NOT authoritative. Rene is most likely incorrect in his
'assumption' that his problem was caused by a "bug" in BITS. There is no such
evidence that any such bug exists, but there is conclusive evidence that
Rene's proxy server -- NetCache -- was most likely involved in the problem.

Furthermore, the assumption that the problem was a DNS problem is also flawed.
BITS reports the "usual" cause for the '2afa' error, but it is not the ONLY
cause. BITS thinks the problem is because it cannot get a valid resolution to
a host name, but the actual problem, as demonstrated in Rene's scenario, and
may well be the case in Lude's scenario, is that the proxy server is
non-compliant and stripping Range Protocol Headers.

The original post by Lude very definitely suggested this was a /proxy/
problem, yet no factual investigation of the proxy server has ever been
conducted. So.. while adding an entry to the hosts table may be a 'workaround'
for the real problem, in the case of Rene, or Lude -- it is not the resolution
to the /problem/ -- nor is it evidence that any BUG exists in BITS.

The BUG exists in the PROXY server (definitely in the case of Rene's NetCache
proxy, and most likely in the case of Lude's -- as yet unknown brand -- proxy
server.)

"Torgeir Bakken (MVP)" <Torgeir.Bakken-spam@hydro.com> wrote in message
news:uoqUdTC7FHA.1484@tk2msftngp13.phx.gbl...
> Hi,
>
> Google Groups link:
> http://groups.google.com/group/micro...59999e68e88b62
>
>
>
> Lawrence Garvin [MVP] wrote:
>
>> Well... that link was totally unreadable.... there seems to be some
>> incredible corruption in the databases at this site..
>>
>> Any chance you have a Google Groups link?
>>
>> Or could /post/ the text that you're working from?
>>
>>
>> "Lude" <Lude@discussions.microsoft.com> wrote in message
>> news:F1D70E4D-96B3-484C-B708-8B1752A60B2D@microsoft.com...
>>
>>>I got this info on bits from:
>>>http://www.archivum.info/microsoft.p.../msg00067.html
>>>
>>>"Lawrence Garvin [MVP]" wrote:
>>>
>>>
>>>>Could you expand a bit on this BITS dns bug that you've been told about?
>>>>
>>>>What was your source for this information?
>>>>
>>>>I'm not aware of any such bugs, nor am I aware of any need to be making
>>>>entries in the hosts file in order to get to a regional windowsupdate
>>>>site.
>>>>
>>>>
>>>>"Lude" <Lude@discussions.microsoft.com> wrote in message
>>>>news:0D227016-7074-4FF2-92E2-F5E70F439505@microsoft.com...
>>>>
>>>>>I found out what the problem is. I had to install the latest version of
>>>>>the
>>>>>windows upate client from
>>>>>http://download.windowsupdate.com/v6...gent20-x86.exe
>>>>>
>>>>>And then I had to make this entry in my hosts file:
>>>>>207.46.245.220 au.download.windowsupdate.com because bits 2.0 has a dns
>>>>>bug.
>>>>>Thanks for all your help and I hope this will help anyone with the same
>>>>>type
>>>>>of problem.
>>>>>
>>>>>Thanks!
>>>>>
>
>
>
> --
> torgeir, Microsoft MVP Scripting, Porsgrunn Norway
> Administration scripting examples and an ONLINE version of
> the 1328 page Scripting Guide:
> http://www.microsoft.com/technet/scr...r/default.mspx

And just to get that information here, to be archived with /this/ thread in
Google, and discount the erroneous assumption that this is a bug in BITS, when
most likely it is caused by the proxy server in use, I'm citing the actual
diagnostics from Narayana's post:

When you tried the URL with IE did you set the same proxy? I would like to see
BITS logs to find out more about this problem. Please run the following
instructions from a command prompt:
set BitsRegKey=HKLM\Software\Microsoft\Windows\Current Version\BITS
reg add %BitsRegKey% /v LogFileFlags /t REG_DWORD /d 0xfbcf /f
reg add %BitsRegKey% /v LogFileSize /t REG_DWORD /d 0x100 /f
reg add %BitsRegKey% /v LogFileMinMemory /t REG_DWORD /d 0x30 /f
net stop bits
net start bits

After this reproduce the problem. Once you get the error stop the BITS service
using the following command
net stop bits


[Review or post] the following files %windir%\system32\bits.log and
%windir%\system32\bits.bak (if it exists).

I would be interested in seeing any bits.log or bits.bak that results from
such diagnostics.





"Robert Aldwinckle" <robald@techemail.com> wrote in message
news:Ou38aAG7FHA.476@TK2MSFTNGP15.phx.gbl...
> "Torgeir Bakken (MVP)" <Torgeir.Bakken-spam@hydro.com> wrote in message
> news:uoqUdTC7FHA.1484@tk2msftngp13.phx.gbl...
>> Hi,
>>
>> Google Groups link:
>> http://groups.google.com/group/micro...59999e68e88b62
>
>
> I don't know what Lawrence's problem with Lude's link was
> but I'm glad you posted a link to the whole thread.
> The following reply from Narayana Mahankali [MSFT]
> documents some diagnostic possibilities I wasn't aware of.
>
>
> Thanks.
>
> Robert Aldwinckle
> ---
>
>