Welcome to Q&A Forum; this is a great place to get support, answers, and tips.
Thank you for posting your query; I'll be more than glad to help you out.
You said you'd followed the instructions... so why did you open TCP/1433 for the SQL Server? ;-)
Set up firewall rules so that the DPM server can communicate with the SQL Server computer:
- Ensure TCP/IP is enabled with default failure audit and enable password policy checking.
- To allow TCP on port 80, configure an incoming exception for sqlservr.exe for the DPM instance of SQL Server. The report server listens for HTTP requests on port 80.
- Enable RPC on the remote SQL Server.
- The default instance of the database engine listens on TCP port 1443. This setting can be modified. To use the SQL Server Browser service to connect to instances that don't listen on the default 1433 port, you'll need UDP port 1434.
- Named instance of SQL Server uses Dynamic ports by default. This setting can be modified.
- You can see the current port number used by the database engine in the SQL Server error log. You can view the error logs by using SQL Server Management Studio and connecting to the named instance. You can view the current log under the Management - SQL Server Logs in the entry Server is listening on ['any' <ipv4> port_number].
The instructions say... TCP/1443
Maybe you check on this little detail ;-) Or change the port on your SQL Server instance to "whatever you want" or back to 1433...
I hope my answer is helpful to you,
If the reply was helpful, please upvote and/or accept it as an answer, as this helps others in the community with similar questions. Thanks!