baggage1854
Junior Member
Posts: 9
Registered: 2-6-2006
Member Is Offline
|
![[*]](./images/xpsilver/default_icon.gif) posted on 2-6-2006 at 10:55 AM |
|
|
WMI: The RPC server is unavailable (fixed as of v2.5)
When scanning machine for Chassis Type and Serial Number, I receive WMI: The RPC server is unavailable. When scanning for System Model, I receive
WMI: For loop not initialized. Every other field scans properly.
|
|
|
Komodo Support
Super Administrator
Posts: 491
Registered: 3-17-2002
Location: Springboro, Ohio, USA
Member Is Offline
Mood: Helpful
|
| posted on 2-6-2006 at 01:22 PM |
|
|
Hi, are you getting information for Domain Role and drive letters under Logical Drives?
Also, is this error happening on some machines or all?
|
|
|
baggage1854
Junior Member
Posts: 9
Registered: 2-6-2006
Member Is Offline
|
| posted on 2-6-2006 at 04:46 PM |
|
|
I get the same "WMI: THe RPV serve is unavailable" message under Domain Role, and I do not see any drive letters. This only happens to a few
machines in my Domain.
|
|
|
baggage1854
Junior Member
Posts: 9
Registered: 2-6-2006
Member Is Offline
|
| posted on 2-6-2006 at 04:47 PM |
|
|
Also, is there a way to disable the pop-up tampering messages in Symantec AntiVirus Corporate Edition on the machines that I scan?
|
|
|
Komodo Support
Super Administrator
Posts: 491
Registered: 3-17-2002
Location: Springboro, Ohio, USA
Member Is Offline
Mood: Helpful
|
| posted on 2-6-2006 at 10:30 PM |
|
|
Are these all Windows XP SP2 machines you're getting this error on?
| Quote: | Originally posted by baggage1854
I get the same "WMI: THe RPV serve is unavailable" message under Domain Role, and I do not see any drive letters. This only happens to a few
machines in my Domain. |
|
|
|
Komodo Support
Super Administrator
Posts: 491
Registered: 3-17-2002
Location: Springboro, Ohio, USA
Member Is Offline
Mood: Helpful
|
| posted on 2-6-2006 at 10:31 PM |
|
|
May we ask what version of Corp. Edition you're using first?
| Quote: | Originally posted by baggage1854
Also, is there a way to disable the pop-up tampering messages in Symantec AntiVirus Corporate Edition on the machines that I scan?
|
|
|
|
baggage1854
Junior Member
Posts: 9
Registered: 2-6-2006
Member Is Offline
|
| posted on 2-6-2006 at 10:33 PM |
|
|
These machines are running XP SP2, and ports 135 and 445 are not blocked by the Windows Firewall.
Symantec Corp. Edition 10
|
|
|
Komodo Support
Super Administrator
Posts: 491
Registered: 3-17-2002
Location: Springboro, Ohio, USA
Member Is Offline
Mood: Helpful
|
| posted on 2-9-2006 at 01:49 PM |
|
|
Hello again, we apologize for the delayed reply, but we wanted to research this some first.
Could you check your Group Policy Editor and see if "Allow remote administration exception" is enabled?
It can be found in the following path:
Administrative Templates\Network\Network Connections\Windows Firewall\Domain Profile
As for Symantec, we are looking into this issue now.
|
|
|
baggage1854
Junior Member
Posts: 9
Registered: 2-6-2006
Member Is Offline
|
| posted on 3-1-2006 at 07:48 AM |
|
|
Group policy is allowing remote administration. I'm still looking for a solution for this and the Symantec issue.
|
|
|
Komodo Support
Super Administrator
Posts: 491
Registered: 3-17-2002
Location: Springboro, Ohio, USA
Member Is Offline
Mood: Helpful
|
| posted on 3-1-2006 at 11:07 PM |
|
|
We've reproduced this issue and will be in communication with Symantec about adding our software to their list of allowed services.
Are you still receiving WMI errors?
|
|
|
baggage1854
Junior Member
Posts: 9
Registered: 2-6-2006
Member Is Offline
|
| posted on 3-2-2006 at 07:44 AM |
|
|
yes
|
|
|
baggage1854
Junior Member
Posts: 9
Registered: 2-6-2006
Member Is Offline
|
| posted on 3-31-2006 at 09:05 AM |
|
|
These issues is still unresolved.
|
|
|
Komodo Support
Super Administrator
Posts: 491
Registered: 3-17-2002
Location: Springboro, Ohio, USA
Member Is Offline
Mood: Helpful
|
| posted on 3-31-2006 at 09:16 AM |
|
|
We apologize, this message slipped through.
Could you send us a copy of the scan with machines showing this error? Please email it to support@komodolabs.com.
|
|
|
baggage1854
Junior Member
Posts: 9
Registered: 2-6-2006
Member Is Offline
|
| posted on 3-31-2006 at 10:09 AM |
|
|
I'm more concerned about the Symantec issue. I won't run a scan on all of my machines because my users will see the Symantec alert. Find a
sloution for that, and I can do a full scan again.
|
|
|
Komodo Support
Super Administrator
Posts: 491
Registered: 3-17-2002
Location: Springboro, Ohio, USA
Member Is Offline
Mood: Helpful
|
| posted on 3-31-2006 at 10:14 AM |
|
|
Symantec is not particularly quick at adding allowed software to their list, but we will contact you as soon as this has been ironed out.
|
|
|
baggage1854
Junior Member
Posts: 9
Registered: 2-6-2006
Member Is Offline
|
| posted on 5-22-2006 at 11:56 AM |
|
|
It doesn't look like Komodo Labs is particularly quick about ironing this out.
|
|
|
Komodo Support
Super Administrator
Posts: 491
Registered: 3-17-2002
Location: Springboro, Ohio, USA
Member Is Offline
Mood: Helpful
|
| posted on 5-22-2006 at 05:51 PM |
|
|
We apologize again. In all honesty we've been concentrating a significant amount of resources to the next generation of NEWT Pro, but we promise to
get the ball rolling this week on the Symantec issue.
We'll post the progress here.
|
|
|
Komodo Support
Super Administrator
Posts: 491
Registered: 3-17-2002
Location: Springboro, Ohio, USA
Member Is Offline
Mood: Helpful
|
| posted on 5-29-2006 at 10:49 PM |
|
|
We'd wanted to let you know we have an email into Symantec, so the process has begun. We will continue to post the progress.
|
|
|
Komodo Support
Super Administrator
Posts: 491
Registered: 3-17-2002
Location: Springboro, Ohio, USA
Member Is Offline
Mood: Helpful
|
| posted on 5-31-2006 at 01:46 PM |
|
|
After speaking with Symantec, we found that we might be able to solve the problem on our end. We are working on this now.
|
|
|
Komodo Support
Super Administrator
Posts: 491
Registered: 3-17-2002
Location: Springboro, Ohio, USA
Member Is Offline
Mood: Helpful
|
| posted on 10-29-2006 at 02:37 PM |
|
|
Issue resolved
This issue was fixed in July 2006 with version 2.0, build 2308.
|
|
|
