Discovery error - RPC server is unavailable

Ravish Shetty
Tera Guru

‎08-01-2019 01:10 PM

hi all,

I tried to do telnet to the IP from the VM which hosts the MID server and I don't see any issues.

is this error credentials related? seems unlikely as we are using a Windows domain admin. Not sure if the machine is not on the domain.

 

find_real_file.png

 

on a side note: we have SCCM integration enabled and I see a network adapter entry in the system with the same IP

 

find_real_file.png

Preview file
50 KB
Preview file
52 KB
Preview file
74 KB
0 Helpfuls
  • 1,383 Views
2 REPLIES 2

Ravish Shetty
Tera Guru

‎08-02-2019 09:04 AM

bump

0 Helpfuls

Alexey7
Mega Sage

‎08-02-2019 10:41 AM

Hi,

make sure that inbound network traffic allowed not only for port 135 but also for dynamic/private port range. When an incoming request from a mid is received by the RPC on port 135, the service assigns a dynamic port number to the request and replies back using that number. The mid then sends a packet to that new port number and not to the 135 port.

 

Please mark this answer as helpful or correct, if it solves your problem.

 

Regards,

Alexey