Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Remote domain question

jfu

Hello,

I have a special domain for remote users in my infrastructure, is it possible to run scan and audit the users?

I think I need a collector installed on the concerned Domain controller?

Thanks for your help.

Jerome

Find more posts tagged with

Accepted answers

All comments

armexpert

Hi Jerome,

you answer yourself you need a collector manually on the remote user domain. Be sure that you open the firewall port 55555 on ARM server as well on ARM collector or if you have windows firewall:

Server Firewall:
1. Port 55555 inbound
2. Port 5671 inbound (if you are using alerts)
3. application rule for pnServer.exe
4. application rule forpnJob.exe
5. application rule forpnTracer.exe
6. application rule forpnAlert.exe
Collector Firewall:
1. Port 55555 inbound
2. application rule for pnCollector.exe
3. application rule forpnJob.exe
4. application rule forpnTracer.exe

Then open the ARM Configuration and click on Collectors and add the collector via typing the name.of the machine (1). Then press "plus" (2)

After that it should connect automatically and you can go to the scan configuration and add domain be sure that you enter a name from the "remote users domain"

After that you select the domain and now you are able to scan and manage your external domain.

Hope that helps.

Cheers

Mike

jfu

Hi Mike,

Thanks for your answer,

Ports are opened on both servers, I test with a browser and telnet, but the collector is unable to connect the server

armexpert

Hi jfu,

thry this:

1.) open the internet explorer on the server as well as on Collector

2.) Type https://CollectorServerName:55555

3.) Type https://ARMSERVERNAME:55555

If you got similar results, FW ist off. But if not then you still have FW issues.

In your case, it might be helping if you restart on the collector the ARM service and try manually reconnect from ARM Server.

It is black if the connector is not connected.

What you can else do is check on the "collector" if the Process PID is toggling from pnCollector.exe

if that is not stable then the connection will never establish. In that case, you need to open a ticket and send the pnCollector*.log from "C:\ProgramData\protected-networks.com\8MAN\log" on the collector. Maybe you can analyze by yourself the problem or if you like post it here.

Cheers

Mike

jfu

Hi Mike,

I solved the issue, I add the FQDN from both servers to the hosts files and now it works

Thanks for your help

Jerome

armexpert

Hi Jerome,

sounds good. That I'm doing just in my DEMO environment, but when it helps, perfect. Have a nice day.

best regards

Mike