Query with PowerShell and if it still fails then run wireshark on the target and capture the traffic and look at packets on TCP 135. If there's traffic then run "netstat -ano | findstr "135" on the target and get the PID of the application listening on ports 135. then take that PID and look in the task manager and see what's using that port and dissect from there. It could be as simple as a GPO preventing it from working so take a look at that as well.