Posts: 14
Threads: 6
Joined: Oct 2018
Reputation:
0
I know, simple application, but I was wondering if there is a manual available for download with more detailed steps/configuration help?
I guess I have 2 questions:
Im trying to install ASG2018 onto a newly built 2016 server, with local SQLExpress install. (windows firewall off)
I have 2 test connections (Vnc with public creds to access) ,locally it works fine when Im logged in as Domain\User1
But when I launch the client on a PC, I get to adding the database connection and I get a message 'A connection was successfully established with the server, but then an error occurred during the login process.
(Provider SSL provider, error : 0 - The client and server cannot communication , because they do not possess a common algorithm.)"
Im trying to determine what TLS settings need to be changed or enabled on the server and client.
Posts: 11,205
Threads: 101
Joined: Aug 2006
Reputation:
205
The help you can access by pressing F1 inside ASGRD.
Do you have all Windows updates installed? Normally that should not be an issue
Regards/Gruss
Oliver
Posts: 11,205
Threads: 101
Joined: Aug 2006
Reputation:
205
It should be used the newest TLS protocol on the supported .NET framework - so if you client is fully updated this should not be a problem
Did you install SQLExpress yourself or by using ASGRD and the option "Install new database including SQLExpress"? Perhaps in your SQL Configuration the TCP/IP is not enabled? Did you check the security settings for the database? Because it seems that the connection can be established but not the call of the first stored proc?!? But the error message is strange if both client and server are fully updated...
Regards/Gruss
Oliver
Posts: 14
Threads: 6
Joined: Oct 2018
Reputation:
0
12-11-2018, 11:55 PM
(This post was last modified: 13-11-2018, 12:05 AM by dbwillis.)
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?
Posts: 11,205
Threads: 101
Joined: Aug 2006
Reputation:
205
I'm not sure - but perhaps you can check if you have installed all patches for the SQL (Express) instance - the TLS 1.2 should be used automatically when using the newest .NET - and the app uses the newest .NET framework! So it should be the SQL express that comes with this error
If you have an SQL cluster available you should try to use it instead of the SQL Express to see if it still happens or not
Regards/Gruss
Oliver
Posts: 14
Threads: 6
Joined: Oct 2018
Reputation:
0
AH !
I was missing (KB4022619), installed that and I was able to connect, all the FAQ indicated that SQL2014 was tls 1.2 from the get go, I can connect now !
THanks everyone
