MECM prerequisite SQL account/TCP port errors won't clear despite being fixed

[Garacesh]

SQL Server service running account
The logon account for the SQL Server service cannot be a local user account, NT SERVICE\ or LOCAL SERVICE.  You must configure the SQL Server service to use a valid domain account, NETWORK SERVICE, or LOCAL SYSTEM.

This has been actioned and the SQL Server ($InstanceName) service is operating as a networked account.

I have even tried setting all the other SQL services to use this account, too, and even tried making that account a domain admin.

 

SQL Server Tcp Port
Configuration Manager primary site and central administration site require SQL Server Tcp is enabled and set to Static port.

In SQL Server Configuration Manager, under SQL Server Network Configuration / Protocols for $InstanceName, TCP/IP is enabled, and TCP Port is set to 1433 under the IPAll section. IPAll's Dynamic Ports option is blank.

I have event tried setting this on all of the 4 above interfaces (IP1, the fe80 ipv6 address, IP2, the server's current ipv4 address, IP3 ::1 and IP4 127.0.0.1)

 

Google tells me what I'm doing is right, but these prerequisite checks still constantly return Failed

[EddyAllen]

Are you able to check if 1433 is accessible to devices on your network? Might sound daft but that's probably a good starting point just to make sure its not an over-zealous firewall stopping 1433 traffic.

[Garacesh]

Are you able to check if 1433 is accessible to devices on your network? Might sound daft but that's probably a good starting point just to make sure its not an over-zealous firewall stopping 1433 traffic.

 

Oops, should've updated this thread.

Turns out it was a combination of that (why does the Windows Firewall warning go away, if the firewall is still blocking stuff? ) and 'Log on as a service' permissions.

 

So I'd fix one issue, it still wouldn't work, so I'd undo the fix and try something else..