RMA 301: Network path not found
RMA 301: Network path not found
Hello!
I'm using Host Monitor 12.00.
Trying to setup Windows Process check test to retrieve Process list, but receive 301 error - network path not found.
Using Passive RMA on remote host scheme. Other tests, like Disk free space, or Services list are working fine.
Whats wrong with Process list?
I'm using Host Monitor 12.00.
Trying to setup Windows Process check test to retrieve Process list, but receive 301 error - network path not found.
Using Passive RMA on remote host scheme. Other tests, like Disk free space, or Services list are working fine.
Whats wrong with Process list?
You can assign any port you want.
But according to error message (301 error - network path not found) there are no problems related to HostMonitor <-> RMA communication.
HostMonitor (systemA) -> RMA (systemB) -> target system (systemC) - this is your scenario, right?
RMA cannot get processes list from target system, this means problem related to target system (or something between RMA and target system).
Disk free space, Service tests work fine, so its should be local problem.
May be you just specified wrong IP/hostname? Try to set FQDN name or IP address instead of hostname.
Have you enabled Remote Registry service?
Regards
Alex
But according to error message (301 error - network path not found) there are no problems related to HostMonitor <-> RMA communication.
HostMonitor (systemA) -> RMA (systemB) -> target system (systemC) - this is your scenario, right?
RMA cannot get processes list from target system, this means problem related to target system (or something between RMA and target system).
Disk free space, Service tests work fine, so its should be local problem.
May be you just specified wrong IP/hostname? Try to set FQDN name or IP address instead of hostname.
Have you enabled Remote Registry service?
Regards
Alex
My scenario is HostMonitor (System A) - RMA and target system (system B) - simplest one.
Though that is RMA is started on target system directly with Admin rights - it's all is needed to go.
So, enabled RRS, and now can receive f list of processes on target system, thank you a lot!
Though that is RMA is started on target system directly with Admin rights - it's all is needed to go.
So, enabled RRS, and now can receive f list of processes on target system, thank you a lot!
Last edited by rawyan on Tue Jan 28, 2020 8:51 am, edited 1 time in total.
When test performed by agent then hostnames, IP addresses processed by RMA system, not HostMonitor system.
E.g. you may have "mainserver" host in HostMonitor LAN and host with the same name "mainserver" in RMA LAN. RMA will connect to its local "mainserver", it knows nothing about HostMonitor LAN.
On other words - yes, localhost is localhost, its system where test starte
d (localhost==HostMonitor system when test performed by HostMonitor; localhost==RMA system if test performed by RMA)
Regards
Alex
E.g. you may have "mainserver" host in HostMonitor LAN and host with the same name "mainserver" in RMA LAN. RMA will connect to its local "mainserver", it knows nothing about HostMonitor LAN.
On other words - yes, localhost is localhost, its system where test starte
d (localhost==HostMonitor system when test performed by HostMonitor; localhost==RMA system if test performed by RMA)
Regards
Alex