Question : PortQuery RPC Failure: "RPC query failed (5)"

PortQuery RPC Failure: "RPC query failed (5)". We were attempting to retrieve data from the Windows Event Logs using the Eventquery.vbs script. In the midst of trying to figure out why Eventquery.vbs wouldn't run, I ran "PortQry -n -e 135" and received the message "RPC query failed (5)". In order to get the Eventqry.vbs script to run, we disabled Windows FireWall - after which Eventquery.vbs ran.

However, we continue to get the "RPC query failed (5)" message when I try to run PortQry. Does anyone know what this error message means?

We did some further testing and found the following:

(1) if we run PortQry with the firewall ON, we get the "failed" error.

(2) if we run PortQry with the firewall ON, and with Exceptions configured for File & Printer Sharing - as well as adding 135 TCP/UPD ports, we get a return of "Failed". Eventqry.vbs also fails with the error "Please check the system name, credentials, and WBEM Core".

(3) if we run PortQry with the firewall ON, and with Exceptions configured for File & Printer Sharing (only), the program returns "Filtered". Eventqry.vbs returns the same error message: "Please check the system name, credentials, and WBEM Core".


We haven't been able to find any information on the PortQry error. And there's not concise information on the Eventqry/WBEM errors, either.

Any assistance would be appreciated.

Answer : PortQuery RPC Failure: "RPC query failed (5)"

Port 135 is for the RPC end point mapper database. Are you running this against an AD DC?

If not, there is nothing to respond on 135 and will result in the RPC error.