I am in the process of setting up a small 2016 lab for dev/testing. I have build a set VM's with a Domain Controller, AD FS, SQL and SCOM and in test domain. All servers are running 2016. This is not a production environment.
I am trying to get the SCOM server to communicate with the SQL server over the default 1433 MS-SQL port. I feel like I am missing something easy, but here are the things that I have checked:
1. Servers are on the same subnet (same vm host at that), no hardware firewall
2. Servers can ping eachother. I did create a Windows firewall rule to allow ICMP between the hosts. I also created one for the SQL server (1433)
3. Confirmed named pipes are enabled in SQL Configuration Manager
4. I set "IP3" to "Enabled" on the TCP/IP protocol network properites on Configuration Manager - IP3 is my private routable IP interface
5. Confirmed remote access was enabled under Connections in Management Studio on the local SQL server
6. Running a wireshark on the SQL server while trying to access the SQL server from the SCOM (either by ODBC setup or using Management Server on SCOM server) - I see inbound packets from the SCOM server (both over 1433 and ICMP) but the SQL server never sends back a packet.
7. PortQry results in a FILTERED message
It seems as though the SQL server is ignoring the requests. I would assume this is a security setting that I am missing.
: Forgot to mention - I've tried connecting with both the FQDN and IP address. Connecting wiht Windows Authentication. I am going to enable/setup a local SA account for testing