Komodo Labs Forums
NEWT Professional => NEWT Pro Network Inventory - Support => Topic started by: richard on April 08, 2005, 02:09:57 PM
-
I am using the 10 machine licence of Newt Pro v2.0 Build 2261.
The HP Servers & PCs are in a Windows domain and I am running Newt using the domain administrator account. Some the of fields do not produce any data:
Motherboard Manufacturer - WMI:access is denied
System Model - WMI:For loop not initialized
Serial Number - WMI:access is denied
Drivers-Logical Tab is empty
RAM slots Tab is empty
Services Tab is empty
System Slots Tab is empty
Anything I can do to populate these fields?
thanks
richard
-
Hi Richard. Could there be a software firewall may be turned on for these machines?
If this is the case, please try running this file locally on one of them to open up WMI for the firewall:
http://www.komodolabs.com/OpenFireWallForWMI.zip
Please let us know if this works for you. If not, we can explore other avenues.
-
Both machines are servers running W2K with no firewall software on my PC or the servers. Also there is no hardware firewall between my PC and the servers.
-
Hello again. We apologize for the late reply.
Are you able to get most other data including Software?
-
I think the problem was DCOM related. My PC (W2K SP4) did not have DCOM enabled. Enabling it, using DCOMCNFG, seems to have fixed the problem.
Is DCOM disabled by default on W2k?
-
Hi. DCOM should actually be enabled by default in W2K. It could be that a program or another user disabled it.
Thanks for letting us know. If other users report a similar issue we\'ll be able to help them better.
-
I keep getting this on some of my machines. I am running a 500 user license and for all that I have checked the configurations of services and firewall are the same between a machine that scans ok with the ones getting the error.
Also getting network path not found on other machines, which are also configured the same, turned on and functioning on the network.
Being a new user, I suspect I am missing something. All help appreciated.
-
Also, all machines are XP, SP2 or Server 2003.
-
Hello Francine. There can be many reasons why you\'re getting these errors, most related to Windows or Windows security. We are working on a self-help system, but we\'re trying to help users on an individual basis until then.
We will contact you by email to get more information from you.