Thanks for the reply.
The DNS server isn't the problem I'm afraid. On line 336, you get the system_name from WMI:
[code]Set colItems = objWMIService.ExecQuery("Select * from Win32_ComputerSystem",,48) For Each objItem in colItems system_name = objItem.Name domain = objItem.Domain Next[/code]
Under certain error conditions, the value returned by WMI is an empty string. When that empty string is passed to the nslookup function on line 359:
[code]ns_ip = NSlookup(system_name)[/code]
The nslookup program stops at it's command prompt because it was not given a system name. I imagine this isn't a problem for everybody, but we audit approximately 4000 PC's and it manages to occur at least a few times on every pass of the domain. This takes up a few of the "threads" each pass until all 20 spawned audits that we allow are tied up waiting for nslookup to return.
Seems like a check for a blank name or a check for an error should be added before running the nslookup.
Let me know if you need further info.
-Randy
|