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
Store

SAM Cross Domain Node Discovery, Port Requirements

Hi all,

I have just installed SAM on one of our Dev servers. I am looking to implement an agentless solution for monitoring our infrastructure. Apologies if this question has already been answered but I could not find an answer to my problem. If an answer has been posted, please point me to the link.

My issue is as below:

My SAM is installed on a Windows 2012 server in Domain A. I am able to add any machine from domain A using admin credentials without a hitch.

However, when I try to add a node from Domain B using admin credentials, it cannot find any machines to add in wizard mode. If I try and add a single node, it still fails. When I click to test credentials, it fails the validation. I have opened port 135 through firewall on Domain B. I am able to Telnet from SAM to Domain B server. Is there anything that I am missing.

Thanks for your help.

Find more posts tagged with

sam.

Accepted answers

All comments

orioncrack

You will need much more than 135 open.

SAM port requirements

leigham_martin

Also to note,

if Domain A & Domain B are separated by firewalls then you have another issue....

As your not using an agent in this instance then i assume you will be using WMI in which has a dynamic port range of thousands.

This means you would need to open up a lot of ports on your firewall to monitor anything windows via WMI..

However, if your like me and are destined to use WMI then the below URL will help you out, youll be able to monitor via WMI over 1 single port which minimizes the risk on your firewall

Setting Up a Fixed Port for WMI (Windows)

Im using this kind of setup for my DMZ area whereby i want to monitor specific servers via WMI without opening 65000 ports.

as orioncrack stated you will need more than 135!

Off the top of my head i believe the reason for your credential failures in general is because i believe it uses 445 (SMB) to go in and check?

You'll also need other ports opening depending on what your looking to monitor in Domain B

Also, you should probably use DomainB\AdminUser when doing your discoveries or adding nodes to eliminate a domain or user issue.

Can Domain A see Domain B? (DNS Etc?)

Regards,

salamm

Thanks for you replies guys.

Leigham, I am using an admin user. Infact tried with multiple admin users. Also, when you say Domain A can see Domain B, do you mean like it can ping it? Could you please explain.

Kind regards,

Mustafa

leigham_martin

Mustafa,

As you mentioned you are running SAM in Domain A and you want to add a node that sits in Domain B. Are you using a local admin account on the node in Domain B?

Or are you using an admin account to add the node in? (Domain A or B Account)

I would definitely make sure you have port 445 and 135 open as a minimum to prove that your SAM box in Domain A can actually test whatever credentials your using against the node in Domain B

I have a similar setup however i dont have a Domain B, i have a DMZ in which the servers do not have a domain, they are all local authentication.

If you are using a local admin account to install the agent on the Node in Domain B ensure the "LOCAL" admin account is actually in the administrators group as it does not do this by default.

Kind Regards,