Error code #53

jordydk · Post by **jordydk** » Thu May 23, 2024 3:07 am

I have the following problem, we have two different Domain Controllers running in our infrastructure, one domain is at 172.100.x.x and the other domain is at 172.200.x.x. The domain is also different from each other. Domain 1 = domain1.companyA.local Domain 2 = domain2.companyB.com

I cannot read the CPU, OS Update, Free space, if I use the FQDN, IP address or just Hostname.

Even when I use the Passive Agent, I get error messages.

Everything I try gives me the following messages.

* Cannot connect to remote Registry. Code #53
* Error: The RPC server is unavailable
* Error: Unable to connect to the specified computer or the computer is offline.

The only test that is working is the PING command.

Hopefully you have a solution for this.

Thank you in advance.

KS-Soft · Post by **KS-Soft** » Thu May 23, 2024 4:22 am

Cannot connect to remote Registry. Code #53

This can be firewall issue

I have the following problem, we have two different Domain Controllers running in our infrastructure
.. The domain is also different from each other.

Ok, what about HostMonitor and RMA?
Where do you run HostMonitor?
- domain1?
- domain2?
- some other domain3?
- on some workstation that does not belong to any domain?
- HostMonitor is started as service application?
- HostMonitor is started under local admin account? domain account? "local system account"?
Same list of questions about RMA - where is runs, service or application mode, what account is used?

You cannot monitor both domains or just one of them?

>the only test that is working is the PING command.

Do you mean SNMP, TCP, UDP, DNS, DHCP related tests do not work? "No answer" status? Then check your firewall settings

Regards
Alex

jordydk · Post by **jordydk** » Fri May 24, 2024 8:11 am

About code #53, I will check this with the Firewall expert.

Also tried to use HM with RMA, but I don't get the connection (Status: no answer).

HM runs on Domain 1.
There is no Domain 3.

HM is running as a application and runs as admin with all possible rights.

All other servers works with HM in the same domain of stand-a-lone servers works with RMA

.

I'll will contact the Firewall expert for this problem.

KS-Soft · Post by **KS-Soft** » Fri May 24, 2024 8:57 am

Sorry, I do not understand.

Do you mean HostMonitor started in Domain1 can monitor all systems within domain1 and CAN connect to RMA started in the same domain1?

But HostMonitor (domain1) CANNOT connect to another RMA started on some system in domain2?
And HostMonitor cannot monitor systems in domain2 directly (without RMA), including tests like SNMP, TCP, UDP, DNS, DHCP?

Then you should check firewall settings.

Regards
Alex

jordydk · Post by **jordydk** » Mon May 27, 2024 1:17 am

KS-Soft wrote:Sorry, I do not understand.

Do you mean HostMonitor started in Domain1 can monitor all systems within domain1 and CAN connect to RMA started in the same domain1?
Yes that is working

But HostMonitor (domain1) CANNOT connect to another RMA started on some system in domain2?
And HostMonitor cannot monitor systems in domain2 directly (without RMA), including tests like SNMP, TCP, UDP, DNS, DHCP?
Also with RMA, I can't use the tests, only the Ping commando

Then you should check firewall settings.

Regards
Alex

KS-Soft · Post by **KS-Soft** » Mon May 27, 2024 1:43 am

So, have you checked firewall settings?

Also with RMA, I can't use the tests,

We are going back and forth and I still do not understand what are you saying

What exactly means "I can't use the test"? What exactly error do you see?
The same errors that are displayed when tests performed by HostMonitor
- Cannot connect to remote Registry. Code #53
- Error: The RPC server is unavailable
This means HostMonitor can connect to the agent, agent cannot connect to the target system. Are you sure RPC service is running, ports are not blocked?

or you see different error? Like "RMA: Connection error"?
This means HostMonitor cannot connect to the agent and you should check RMA, HostMonitor and firewall settings.

Regards
Alex

jordydk · Post by **jordydk** » Mon May 27, 2024 2:53 am

This is the message what I get, from the RMA that I have installed on the server in domain 2.

KS-Soft · Post by **KS-Soft** » Mon May 27, 2024 4:09 am

Are you sure RPC service is running, ports are not blocked?

Regards
Alex

jordydk · Post by **jordydk** » Mon May 27, 2024 4:47 am

I think indeed that the port is blocked. Ill check this with the network engineer.

jordydk · Post by **jordydk** » Tue May 28, 2024 6:57 am

Problem solved, the local firewall was enabled.