C:\Admin\Util>err 0x80072ee2

# as an HRESULT: Severity: FAILURE (1), Facility: 0x7, Code 0x2ee2

# for hex 0x2ee2 / decimal 12002 :

  ERROR_INTERNET_TIMEOUT
inetmsg.h

  ERROR_INTERNET_TIMEOUT
wininet.h

# 2 matches found for "0x80072ee2"

 

Your best friend is probably the newsgroups monitored by the MS
employees. Google that error and it's fairly common.

 

>From a NG post by one of the main MBSA dudes at MS-

 

Since any error reported by MBSA 2.0 in the format "0xNNNNNNNN" is
actually    

a WSUS/Microsoft Update error code, you may want to examine Windows
Update    

to ensure it is working as expected.  The following links may be
helpful:  

  

http://support.microsoft.com/default.aspx?scid=kb;en-us;836941  

  

http://update.microsoft.com/windowsupdate/v6/showarticle.aspx?articleid=
32&ln=en&IsMu=False  

  

http://update.microsoft.com/windowsupdate/v6/showarticle.aspx?articleid=
48&ln=en&IsMu=False  

  

http://www.updatexp.com/0x80072ee2.html  

  

http://www.updatexp.com/0x8007007E.html  

  

 

Doug Neal [MSFT]  

  

[email protected]  

 

 

 

From: Haralson, Joe (GE Comm Fin, non-GE) [mailto:[email protected]] 
Sent: Thursday, July 09, 2009 11:06 AM
To: NT System Admin Issues
Subject: RE: MSBA 2.1

 

Thanks. I have File/Print sharing on . Now receiving the following
error:

 

An error occurred while scanning for security updates. (0x80072ee2)

 

________________________________

From: Free, Bob [mailto:[email protected]] 
Sent: Thursday, July 09, 2009 10:16 AM
To: NT System Admin Issues
Subject: RE: MSBA 2.1

>From what I've seen online in the past- File/Print sharing off (no
server or workstation service) probably most likely culprit. Also seen
it attributed to firewall or other "hardening" configs. 

 

From-  http://technet.microsoft.com/en-us/security/cc184922.aspx  MBSA
2.1 Frequently Asked Questions

 

 

 

       Q: Why am I seeing error "Could not resolve the computer name:
name. Please specify computer name, domain\computer, or an IP address."?


      

This error is common when scanning based on an IP address range. This is
because MBSA will convert the range into a list of specific IP addresses
for that range and attempt to resolve each IP address into the
associated NetBIOS computer name. When that name resolution cannot be
performed because the computer is switched off, or the IP address is not
in use, this error will be returned.

The error can also happen when using a domain name of domain members are
not accessible on the network, such as a laptop computer roaming outside
the wireless network, or a desktop computer that has been shut down.

If you specify a DNS fully qualified domain name (FQDN) as the domain to
be scanned, you will also see these errors. In that case, you need to
use the NetBIOS compatible domain name.

 

 

 

 

From: Haralson, Joe (GE Comm Fin, non-GE) [mailto:[email protected]] 
Sent: Wednesday, July 08, 2009 8:23 PM
To: NT System Admin Issues
Subject: MSBA 2.1

 

I'm attempting to use MSBA 2.1 but keep getting errors concerning name
resolution. Has anyone ran into this issue? I'm using an account that
has admin rights but when trying to scan a range of addresses I receive
name resolution errors. Any suggestions? We are having no DNS issues on
domain. Nslookup works just fine.

 

Thanks' 
Joe Haralson 

 

 

 

 

 

 

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

<<image003.png>>

Reply via email to