For Carl and Satch,
I got the two handshaking last week. My original post was lacking as I only registered the "master" data file under the sa ownership.
I had to reach way back to find resources from earlier years to make the connection work. I will be posting my solutions soon. I made SnagIt captures of my steps.
As mentioned above, create a user, I used CFUSER. Create a test data file and assign ownership to CFUSER. Of course, there is much more. Until I get organized, these informative links will help get you to the final connectivity.
1) Enable Remote Connection on SQL Server 2008 Express - Linglom.com (relates to Server 2008 but needed).
2) http://www.paulsilver.co.uk/blog/2014/10/setting-up-coldfusion-sql-server-express-windows-8/
3) Enable remote connections for SQL Server Express 2012 - Stack Overflow
4) How do I configure SQL Server Express to allow remote tcp/ip connections on port 1433?
5) Configure a Server to Listen on a Specific TCP Port | Microsoft Docs
TCP/IP must be enabled. TCP dynamic ports are key: Note: the following steps are excerpted from one of the blog entries. Posting here for reference.
--------------------------
How do I configure SQL Server Express to allow remote tcp/ip connections on port 1433?
Run SQL Server Configuration Manager.
Go to SQL Server Network Configuration > Protocols for SQLEXPRESS.
Make sure TCP/IP is enabled.
So far, so good, and entirely expected. But then:
Right-click on TCP/IP and select Properties.
Verify that, under IP2, the IP Address is set to the computer's IP address on the local subnet.
Scroll down to IPAll.
Make sure that TCP Dynamic Ports is blank. (Mine was set to some 5-digit port number.)
Make sure that TCP Port is set to 1433. (Mine was blank.)
(Also, if you follow these steps, it's not necessary to enable SQL Server Browser, and you only need to allow port 1433, not 1434.)