Sorry for the delay in getting back, rebuilt my work PC and couldnt get the ASG forum password reset.
Yep, I did the 2018 install and then created the SQLExpress DB during setup.
I finally figure out to add the 'Microsoft SQL Server Management Studio 17' on the server, then add the 'users' with permissions to the DB.
TCP/IP is enabled.
From my testing, Ive determined the block.
On the server (2016 Server, fully patched) SSL 2.0+3.0, TLS 1.0+1.1 are set to disabled in the registry via "DisabledByDefault" (this is forced by our parent company)
On the clients (mix of Win7 and Win10, all 64bit) SSL 2.0+3.0, TLS 1.0+1.1 are also set to disabled in the registry via "DisabledByDefault"
On both, TLS 1.2 is enabled in the registry
I cannot connect a client to the server, I get the error mentioned in the first post.
IF I enable SSL 3.0 in the registry, then launch ASG 2018, I get the prompt about no database is set yet, I go to add the DB, hit test connection, then I can connect.
All machines have .Net 4.7.2 with any and all updates
Is there a way to test TLS 1.2?
Is the TLS setting coming from teh SQLExpress install? Im wonderin if this will be a non issue if the actual DB is on our SQL cluster?
Yep, I did the 2018 install and then created the SQLExpress DB during setup.
I finally figure out to add the 'Microsoft SQL Server Management Studio 17' on the server, then add the 'users' with permissions to the DB.
TCP/IP is enabled.
From my testing, Ive determined the block.
On the server (2016 Server, fully patched) SSL 2.0+3.0, TLS 1.0+1.1 are set to disabled in the registry via "DisabledByDefault" (this is forced by our parent company)
On the clients (mix of Win7 and Win10, all 64bit) SSL 2.0+3.0, TLS 1.0+1.1 are also set to disabled in the registry via "DisabledByDefault"
On both, TLS 1.2 is enabled in the registry
I cannot connect a client to the server, I get the error mentioned in the first post.
IF I enable SSL 3.0 in the registry, then launch ASG 2018, I get the prompt about no database is set yet, I go to add the DB, hit test connection, then I can connect.
All machines have .Net 4.7.2 with any and all updates
Is there a way to test TLS 1.2?
Is the TLS setting coming from teh SQLExpress install? Im wonderin if this will be a non issue if the actual DB is on our SQL cluster?