MBSA - Computer not found -or- Could not resolve the computer name....
I receive the following error messages when running MBSA "Computer not found -or- Could not resolve the computer name...."
The details are;
latest MBSA
I'm doing a domain search using the NETBIOS domain name
All IP address are static.
All Patches are up to date
GP turns off firewalls and ICS
NBTSTAT returns -
Local Area Connection:
Node IpAddress: [192.168.6.104] Scope Id: []
NetBIOS Remote Machine Name Table
Name Type Status
--------------------------
TAZ <00> UNIQUE Registered
HOODVIEW <00> GROUP Registered
TAZ <20> UNIQUE Registered
HOODVIEW <1E> GROUP Registered
MAC Address = 00-0B-CD-0C-47-31
Except for machine name, IP address etc. All machines return same information.
I've checked DNS and reverse DNS to ensure consistant data. I do not run WINS.
On this run I got over 20 computers out of about 120 and these involve both servers and workstaions.
I've also read the solution concerning MBSA but it was about Dynamic IP's.
That's about all the info I can think of at this time
The details are;
latest MBSA
I'm doing a domain search using the NETBIOS domain name
All IP address are static.
All Patches are up to date
GP turns off firewalls and ICS
NBTSTAT returns -
Local Area Connection:
Node IpAddress: [192.168.6.104] Scope Id: []
NetBIOS Remote Machine Name Table
Name Type Status
--------------------------
TAZ <00> UNIQUE Registered
HOODVIEW <00> GROUP Registered
TAZ <20> UNIQUE Registered
HOODVIEW <1E> GROUP Registered
MAC Address = 00-0B-CD-0C-47-31
Except for machine name, IP address etc. All machines return same information.
I've checked DNS and reverse DNS to ensure consistant data. I do not run WINS.
On this run I got over 20 computers out of about 120 and these involve both servers and workstaions.
I've also read the solution concerning MBSA but it was about Dynamic IP's.
That's about all the info I can think of at this time
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
OK, went through and used the suggestions given by speshalyst and reading the microsoft bulletin on a couple of systems without success. Systems will scan correctly if I do them one at a time but it seems that there is a problem when scanning a domain. Most systems scan ok it is just around 20 that won't. The systems that don't scan are located at different branches around the area (different subnet). It really doesn't pass the make sense test.
ASKER
As nobody else had any solutions I'm awarding all points to speshalyst. However his answer was the same as what I had found in the knowledge base and I needed further help. As it is I'll do some workarounds. Thanks.
ASKER