Re: 0x80072EE7- Windowsupdate error - SBS

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



The advice still doesn't work.

I still haven't seen any postings re: which IP addresses/ IP server names we
should be connecting to.

A bit of poking around at http://www.dnsstuff.com/ seems to indicate that
the update.microsoft.com and windowsupdate.microsoft.com are getting
redirected to update.microsoft.com.nsatc.net and
windowsupdate.microsoft.com.nsatc.net (both Microsoft controlled domains).

The following is a summary of the results from a DNS Lookup on
"windowsupdate.microsoft.com" from http://www.dnsstuff.com/. The DNS
Traversal for windowsupdate.microsoft.nsatc.net seems to indicate that not
all of the ns.nsatc.net DNS servers have the same IP address for
windowsupdate.microsoft.com. BTW: My clients see windowsupdate.microsoft.com
as 207.46.225.221 within our network.

Q1: Could this be the source of some of the 0x80072EFF problems ?
Q2: Can anyone from Microsoft please respond with the official list of IP
names/addresses that Windows Update uses ???!!!


DNS Lookup: windowsupdate.microsoft.com A record
How I am searching:
Searching for windowsupdate.microsoft.com A record at f.root-servers.net
[192.5.5.241]: Got referral to K.GTLD-SERVERS.NET. [took 66 ms]
Searching for windowsupdate.microsoft.com A record at K.GTLD-SERVERS.NET.
[192.52.178.30]: Got referral to ns4.msft.net. [took 6 ms]
Searching for windowsupdate.microsoft.com A record at ns4.msft.net.
[207.46.66.75]: Got CNAME of windowsupdate.microsoft.nsatc.net. and referral
to i.root-servers.net [took 173 ms]
Searching for windowsupdate.microsoft.nsatc.net A record at
i.root-servers.net [192.36.148.17]: Got referral to C.GTLD-SERVERS.net. [took
6 ms]
Searching for windowsupdate.microsoft.nsatc.net A record at
C.GTLD-SERVERS.net. [192.26.92.30]: Got referral to j.ns.nsatc.net. [took 7
ms]
Searching for windowsupdate.microsoft.nsatc.net A record at j.ns.nsatc.net.
[210.184.108.131]: Reports windowsupdate.microsoft.nsatc.net. [took 245 ms]

Answer:


Domain Type Class TTL Answer windowsupdate.microsoft.nsatc.net. A IN 600
207.46.225.221 nsatc.net. NS IN 172800 d.ns.nsatc.net. nsatc.net. NS IN
172800 c.ns.nsatc.net. nsatc.net. NS IN 172800 a.ns.nsatc.net. nsatc.net. NS
IN 172800 us-ny-3.ns.nsatc.net. d.ns.nsatc.net. A IN 172800 66.119.70.6
c.ns.nsatc.net. A IN 172800 64.240.90.167 a.ns.nsatc.net. A IN 172800
206.25.8.69 us-ny-3.ns.nsatc.net. A IN 172800 64.152.2.44

NOTE: One or more CNAMEs were encountered. windowsupdate.microsoft.com is
really windowsupdate.microsoft.nsatc.net.


DNS Traversal for windowsupdate.microsoft.nsatc.net

Looking up at the 7 nsatc.net. parent servers:

Server Response Time
b.ns.nsatc.net [208.173.208.133] 207.46.18.94 132ms
c.ns.nsatc.net [64.240.90.167] 207.46.225.221 132ms
d.ns.nsatc.net [66.119.70.6] 207.46.18.94 132ms
e.ns.nsatc.net [212.187.253.69] 207.46.18.94 133ms
k.ns.nsatc.net [210.158.219.51] 207.46.18.94 233ms
l.ns.nsatc.net [216.206.179.6] 207.46.225.221 233ms
j.ns.nsatc.net [210.184.108.131] 207.46.18.94 342ms



"TaurArian" wrote:

> Thanks for the feed back.
> Kaylene
>
> "Ragmarvel" <Ragmarvel@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:A930B5D9-0903-4F33-8C51-67AD38D40F70@xxxxxxxxxxxxxxxx
> > Thanks TaurArian the second solution in
> > http://support.microsoft.com/?kbid=883821 worked for me.
> >
> > "TaurArian" wrote:
> >
> >> http://support.microsoft.com/?kbid=883821
> >> You may receive an error message when you search for available updates on the
> >> Windows
> >> Update Web site
> >> 0x80072EE7 error code
> >>
> >>
> >>
> >> "Simon" <Simon@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> >> news:BEDB5CE6-AB89-42E5-9F20-57643C24662A@xxxxxxxxxxxxxxxx
> >> > Hi
> >> >
> >> > I too am geting this message, but none of the remedies outlined in the link
> >> > below seem to be fixing the problem.
> >> >
> >> > Would be interested in knowing what is the cause.
> >> > Thanks
> >> > Simon
> >> >
> >> >
> >> > "MarkHunt" wrote:
> >> >
> >> >> I've been getting the same error message for the last week when building our
> >> >> HP D530S WinXP SP2 systems. (An online visit to WindowsUpdate is the last
> >> >> step in our workstation build process after an offline build).
> >> >>
> >> >> There haven't been any changes at our end, and we don't use hosts files.
> >> >> So I assume this is a downstream change. Still, I would like to confirm
> >> >> that's the case.
> >> >>
> >> >> The article
> >> >> http://v5.windowsupdate.microsoft.com/v5consumer/showarticle.aspx?articleid=22&ln=en
> >> >> didn't give me enough information to complete the troubleshooting. If we
> >> >> need to make any firewall changes then I need more detail.
> >> >>
> >> >> Q1: So what are the Windows Update or with Microsoft Update site names/IP
> >> >> addresses that I should be looking for in the hosts file or DNS cache ?
> >> >>
> >> >> Doing tracert's to the following two dns names yielded the following results:
> >> >>
> >> >> windowsupdate.microsoft.com [207.46.205.190] stops at
> >> >> po11.tuk-65ns-mcs-1a.ntwk.msn.net [207.46.224.216]
> >> >>
> >> >> update.microsoft.com [207.46.156.25] stops at
> >> >> pos1-0.iuscixtukc1202.ntwk.msn.net [207.46.155.37]
> >> >>
> >> >> Q2: Are these the correct IP addresses for the sites ?
> >> >>
> >> >> "Patti MacLeod" wrote:
> >> >>
> >> >> > Hi Small Biz guy,
> >> >> >
> >> >> > See if this information, from the Windows Update Troubleshooter, helps you
> >> >> > to resolve the problem:
> >> >> > http://v5.windowsupdate.microsoft.com/v5consumer/showarticle.aspx?articleid=22&ln=en
> >> >> >
> >> >> >
> >> >> >
> >> >> > Regards,
> >> >> >
> >> >> > --
> >> >> > Patti MacLeod
> >> >> > Microsoft MVP - Windows Shell/User
> >> >> >
> >> >> > "Small Biz guy" <Small Biz guy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> >> >> > news:ECFC38AB-4D23-48FB-8FD6-2C43F6406505@xxxxxxxxxxxxxxxx
> >> >> > > Hi
> >> >> > > I have a new installed Windows 2003 Small Business server.
> >> >> > >
> >> >> > > I can't run windows update. I get the following error in the Internet
> >> >> > > Explorer:
> >> >> > > 0x80072EE7
> >> >> > >
> >> >> > > Can anyone help? Thanks
> >> >> > >
> >> >> > >
> >> >> >
> >> >> >
> >> >> >
> >>
> >>
>
>
.



Relevant Pages

  • Issues migrating SBS 2003 domain to Server 2008 Standard
    ... We are stuck migrating our SBS 2003 domain to Server 2008. ... Fatal Error:DsGetDcName (SRV-EXCH) call failed, ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... The name.local entries are used by my apache server to implement ... change button, more button, the "Primary DNS suffix of this ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... button, more button, the "Primary DNS suffix of this computer", it should ... The Security System could not establish a secured connection with the server ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... DNS Host Name: tonyb-pc.imageproc.imageproc.com ... Testing IpConfig - pinging the DHCP Server... ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)
  • Re: Issues migrating SBS 2003 domain to Server 2008 Standard
    ... Since you have migrated to standard server 2008 you would be better served posting in a Standard server NG. ... Event String: ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)