RPC is unavail...

[hasayeret]

Windows FW is off
Port 135 is opened
WMI service has started
Getting these errors when I use the connector to test...

"Scanning WMI..
The RPC server is unavailable.

The RPC server is unavailable.

The RPC server is unavailable.

Checking \\drutil02\Admin$ Access
Connection: FAILURE. Error: Logon Failure: The target account name is incorrect

The RPC server is unavailable.

Warning: 2 Kerberos errors:
Category: 0
ComputerName: UTIL01.rosenberg.local
EventCode: 3
EventIdentifier: 2147483651
EventType: 1
InsertionStrings: ; ; 21:11:51.0000 5/9/2016 Z; 0x29; KRB_AP_ERR_MODIFIED; ; ; ; ROSENBERG.LOCAL; drutil02$; ; ; 3; 576
Logfile: System
Message: A Kerberos Error Message was received: on logon session Client Time: Server Time: 21:11:51.0000 5/9/2016 Z Error Code: 0x29 KRB_AP_ERR_MODIFIED Extended Error: Client Realm: Client Name: Server Realm: ROSENBERG.LOCAL Server Name: drutil02$ Target Name: Error Text: File: 3 Line: 576 Error Data is in record data.
RecordNumber: 1089171
SourceName: Microsoft-Windows-Security-Kerberos
TimeGenerated: 20160509211151.000000-000
TimeWritten: 20160509211151.000000-000
Type: Error

Category: 0
ComputerName: UTIL01.rosenberg.local
Data: System.Byte[]
EventCode: 3
EventIdentifier: 2147483651
EventType: 1
InsertionStrings: ROSENBERG.LOCAL\raadmin; ; 21:11:51.0000 5/9/2016 Z; 0x19; KDC_ERR_PREAUTH_REQUIRED; ; ; ; rosenberg; krbtgt/rosenberg; krbtgt/rosenberg@rosenberg; ; e; a05
Logfile: System
Message: A Kerberos Error Message was received: on logon session ROSENBERG.LOCAL\raadmin Client Time: Server Time: 21:11:51.0000 5/9/2016 Z Error Code: 0x19 KDC_ERR_PREAUTH_REQUIRED Extended Error: Client Realm: Client Name: Server Realm: rosenberg Server Name: krbtgt/rosenberg Target Name: krbtgt/rosenberg@rosenberg Error Text: File: e Line: a05 Error Data is in record data.
RecordNumber: 1089170
SourceName: Microsoft-Windows-Security-Kerberos
TimeGenerated: 20160509211151.000000-000
TimeWritten: 20160509211151.000000-000
Type: Error

Done.

Any idea???

[Nick_VDB · Accepted solution]

You need to ensure that all WMI traffic is allowed through your firewalls. RPC errors usually point to firewall issues, but could be caused by DCOM or other incorrect settings as well. DCOM is used to establish the initial connection to the client machine. We recommend:
 

• Double-checking that *all* WMI traffic is allowed through your firewalls.In Windows Firewall, there is a "remote administration" exception you can enable to allow all WMI traffic, as documented here. For third-party firewalls, you will need to consult your firewall documentation.
• If you haven't already, running this script (as administrator) on one problem client machine as a test, to ensure DCOM and other settings are correct.
• Checking the other troubleshooting steps on RPC errors in this knowledge base article as well.

[joan_letarte]

same problem

[Kgribbe]

I'm having the same problem for some of our devices!