I run into network/firewall folks that love to turn off ICMP but it wreaks havoc on GPOs. It is a big step forward having NLA in Vista/2008 and removing the requirement on ICMP for GPO processing.
From: Don Guyer [mailto:don.gu...@prufoxroach.com] Sent: Thursday, July 09, 2009 8:27 AM To: NT System Admin Issues Subject: RE: MSBA 2.1 We ran into something like this with our a/v management console (which relies on resolution to work properly). Found out ICMP is blocked by default in W2k8 in those cases and firewall being on in other cases, that caused the issue. Don Guyer Systems Engineer - Information Services Prudential, Fox & Roach/Trident Group 431 W. Lancaster Avenue Devon, PA 19333 Direct: (610) 993-3299 Fax: (610) 650-5306 don.gu...@prufoxroach.com <mailto:don.gu...@prufoxroach.com> From: Free, Bob [mailto:r...@pge.com] Sent: Thursday, July 09, 2009 11: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:joe.haral...@ge.com] 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/> ~
<<image001.gif>>
