The new certificate is a 2048 bit certificate and uses a secure Verisign certificate. (new IP 204.212.170.143)
![\"Image\"](\"https:\/\/sonicwall.rightanswers.com\/portal\/app\/portlets\/results\/onsitehypermedia\/090170808773073.png?linkToken=eyJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJzb25pY3dhbGwiLCJleHAiOjE2Mzc0NTM1NzEsImlhdCI6MTYwNTkxNzU3MX0.Opv40RfPeZ6JA8X7tB9xFIwxs6ywQLJO17OPDggfeO0\")
<\/p>\n\n\n\nDESCRIPTION:<\/p>\n\n\n\n
Older firmware versions are not able to contact to the new HTTPS License server due to an updated certificate on our backend.
The new certificate is a 2048 bit certificate and uses a secure Verisign certificate. (new IP 204.212.170.143)<\/p>\n\n\n\n
RESOLUTION:<\/p>\n\n\n\n
Resolution A<\/strong><\/p>\n\n\n\n Resolution B (workaround) in the case you prefer not upgrading the firmware:<\/strong><\/p>\n\n\n\n Step 1: Create a DNS entry on your internal DNS server to resolve to the OLD License manager IP 204.212.170.35 1. Navigate to the System | Certificates<\/strong> page. TIP: The certificate can be obtained by copy-pasting the following PEM encoded text into a text editor and saving it as SonicWallFirewallDPI-SSL.pem (with .pem extension). <\/p>\n\n\n\n OR <\/p>\n\n\n\n the certificate can be exported by accessing Https:\/\/204.212.170.35 from any Internet browser, here is an example on exporting the SonicWall Firewall DPI-SSL certificate using the latest FireFox browser.<\/p>\n\n\n\n 1) First test is to check if the SonicWall resolves to the old licensemanager ip. or… REF: https:\/\/www.sonicwall.com\/support\/knowledge-base\/error-message-ssl-negotiation-with-license-manager-server-has-failed\/170505570663153\/<\/p>\n","protected":false},"excerpt":{"rendered":" DESCRIPTION: Older firmware versions are not able to contact to the new HTTPS License server due to an updated certificate on our backend.The new certificate is a 2048 bit certificate and uses a secure Verisign certificate. (new IP 204.212.170.143) RESOLUTION: Resolution A Upgrade at least to the latest General Release (i.e. 6.2.5.3, 6.2.7.1, 5.9.1.7) Resolution B (workaround) in Read More<\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_bbp_topic_count":0,"_bbp_reply_count":0,"_bbp_total_topic_count":0,"_bbp_total_reply_count":0,"_bbp_voice_count":0,"_bbp_anonymous_reply_count":0,"_bbp_topic_count_hidden":0,"_bbp_reply_count_hidden":0,"_bbp_forum_subforum_count":0,"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"footnotes":""},"categories":[13,52,9],"tags":[435,437],"class_list":["post-2632","post","type-post","status-publish","format-standard","hentry","category-firewalls","category-hardware","category-networks","tag-register-a-old-sonicwall","tag-ssl-negotiation-with-license-manager-server-has-failed"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\t![\"\"](\"https:\/\/sonicwall.rightanswers.com\/portal\/app\/images\/content_caution.gif\")
CAUTION:<\/strong> This workaround may not work. The firmware upgrade is always<\/strong> the suggested solution to this issue as there might be certificate or TLS incompatibilities with old firmware versions.<\/p>\n\n\n\n
Screenshot below shows an example server 192.168.168.101 (DNS Server) which has an entry for licensemanager.sonicwall.com
It resolves to the old IP 204.212.170.35 (old SonicWall Licenseserver which accepts old root certificates from old firmware versions)![\"Image\"](\"https:\/\/sonicwall.rightanswers.com\/portal\/app\/portlets\/results\/onsitehypermedia\/090170808474986.png?linkToken=eyJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJzb25pY3dhbGwiLCJleHAiOjE2Mzc0NTM1NzEsImlhdCI6MTYwNTkxNzU3MX0.Opv40RfPeZ6JA8X7tB9xFIwxs6ywQLJO17OPDggfeO0\")
Step 2: Put the internal DNS as the first choice in the firewall Network | DNS | Settings<\/strong> .
Let’s say the internal DNS server is 192.168.168.101, then put 192.168.168.101 in the first field (first choice)
Step 3: Import the certificate from the https:\/\/204.212.170.35 webpage.
You can use, for example, Firefox to download the certificate. If this does not work, you can also carry out the following steps to import the certificate.<\/p>\n\n\n\n
2. Under Additional CA Certificates, import the SonicWall Firewall DPI-SSL root certificate. <\/p>\n\n\n\n
—–BEGIN CERTIFICATE—–
MIIC6zCCAlSgAwIBAgIJAMCocw7Ocp2\/MA0GCSqGSIb3DQEBBQUAMFgxCzAJBgNV
BAYTAlVTMQswCQYDVQQIEwJDQTEXMBUGA1UEChMOU29uaWNXQUxMIEluYy4xIzAh
BgNVBAMTGlNvbmljV0FMTCBGaXJld2FsbCBEUEktU1NMMB4XDTA5MDMwOTIxMzky
MFoXDTI5MDMwNDIxMzkyMFowWDELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAkNBMRcw
FQYDVQQKEw5Tb25pY1dBTEwgSW5jLjEjMCEGA1UEAxMaU29uaWNXQUxMIEZpcmV3
YWxsIERQSS1TU0wwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAM9Sr0ViM9Uf
QDPE1110vQpZkbBMJdUWTGcomx8lk\/8je38O+GjrS1zEbww7JJ9GEM8PYnPxN9pA
mChtSNy5bviQdNqXfAMhSxRHICg4lFcsa95bzoRm1UzD09jXqsJQO8BR6bmLE+XZ
YnA\/QF+W7ain589WkCS3ER9gptwuw683AgMBAAGjgbwwgbkwHQYDVR0OBBYEFFdA
z3naeZEhRpUg4MfD2Dg93nmoMIGJBgNVHSMEgYEwf4AUV0DPedp5kSFGlSDgx8PY
OD3eeaihXKRaMFgxCzAJBgNVBAYTAlVTMQswCQYDVQQIEwJDQTEXMBUGA1UEChMO
U29uaWNXQUxMIEluYy4xIzAhBgNVBAMTGlNvbmljV0FMTCBGaXJld2FsbCBEUEkt
U1NMggkAwKhzDs5ynb8wDAYDVR0TBAUwAwEB\/zANBgkqhkiG9w0BAQUFAAOBgQCm
kgRiH8A1r6in0u3iAqFBuiNDdkqefVOZAULEplx00\/kETR5m3IOurG+pKln4SmNp
lZgxA6\/ldr+wPgXQD72mbXUHDLIaSernjMhNC1MxhVGiXTGLyYL2ULv52mk8EIzY
Qxk7DWfLJqCuUyZ59+spkQu40uTZX14Dc\/uM142bJg==
—–END CERTIFICATE—– <\/p>\n\n\n\n![\"Image\"](\"https:\/\/sonicwall.rightanswers.com\/portal\/app\/portlets\/results\/onsitehypermedia\/090170808328165.png?linkToken=eyJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJzb25pY3dhbGwiLCJleHAiOjE2Mzc0NTM1NzEsImlhdCI6MTYwNTkxNzU3MX0.Opv40RfPeZ6JA8X7tB9xFIwxs6ywQLJO17OPDggfeO0\")
How to Test:<\/strong><\/p>\n\n\n\n
Go to System | Diagnostic<\/strong> and then check if the name licensemanager.sonicwall.com resolves to 204.212.170.143, and check if the first (the internal DNS) is being used.![\"Image\"](\"https:\/\/sonicwall.rightanswers.com\/portal\/app\/portlets\/results\/onsitehypermedia\/090170808895721.png?linkToken=eyJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJzb25pY3dhbGwiLCJleHAiOjE2Mzc0NTM1NzEsImlhdCI6MTYwNTkxNzU3MX0.Opv40RfPeZ6JA8X7tB9xFIwxs6ywQLJO17OPDggfeO0\")
2) Then go to System | Certificate<\/strong> and check if you see the new imported certificate![\"Image\"](\"https:\/\/sonicwall.rightanswers.com\/portal\/app\/portlets\/results\/onsitehypermedia\/090170808956401.png?linkToken=eyJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJzb25pY3dhbGwiLCJleHAiOjE2Mzc0NTM1NzEsImlhdCI6MTYwNTkxNzU3MX0.Opv40RfPeZ6JA8X7tB9xFIwxs6ywQLJO17OPDggfeO0\")
3a) Go the System | Registration<\/strong> and click on Registration<\/strong>. If you are redirected to a Login Page then the workaround works
Login with your mysonicwall.com credentials with your Username and Password
(the same Password which you use for your mysonicwall.com account)<\/p>\n\n\n\n
3b) You can also go to System | Licenses | License renew<\/strong> (below the Synchronize button). If you click on this link, then it redirects you as well to the mySonicWall account . You should see here a Login Page as well![\"Image\"](\"https:\/\/sonicwall.rightanswers.com\/portal\/app\/portlets\/results\/onsitehypermedia\/090170808607611.png?linkToken=eyJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJzb25pY3dhbGwiLCJleHAiOjE2Mzc0NTM1NzEsImlhdCI6MTYwNTkxNzU3MX0.Opv40RfPeZ6JA8X7tB9xFIwxs6ywQLJO17OPDggfeO0\")
<\/p>\n\n\n\n