Comments
-
on Release Note 6.5.4.7 a see GEN6-1268 as DPI-SSL problems. Are you sure ?
-
Have you got visibility about my problem ? GEN6-1803
-
Thanks, I got it! Is it possible to have more information on this error GEN6-1417 ?
-
I saw firmware 6.5.4.7 is out. I would like a detail on this problem solved "GEN6-1417 NetExtender slow performance" (I have users who also complain about this problem). 6.5.4.7 solved mobile client problem GEN6-1285 Thanks
-
support inform me: We have received and update from the backend team. Please go ahead and make these changes and let me know if you are still facing issues. Looks like its busy in sorting IP. Please disable IP report under appflow>settings and system>diagnostics>Tech-support report and monitor
-
I don't know if it might interest you. In the ACL (LAN-WAN) I set in the advanced tab: For traffic from an unauthenticated user: For users who are not identified via SSO, don't redirect to log in
-
what is meaning of JIRA ?
-
today support send me notification: Created JIRA GEN6-1803 for the Core 0 issues
-
I update firewall to hotfix SonicOS Enhanced 6.5.4.6-79n--HFGEN6-1249-2n but i see a lot of cpu consume of processi tawss3client My ticket is 43455656 Do you have visibility about this problems ? Or for SonicWALL is not a problem ? We have nothing configured about AWS (vpn, log, ecc)
-
I want know if you see which problems i related to this fix sw_nsa-6600_eng_6.5.4.6-79n--HFGEN6-1249-2n_6.5.4_release_6_5_4_6_2n_1244505 or something about "JIRA GEN6-1721"
-
Thank you. I wanted to know if you have visibility of my ticket "43455656" in your position. I have serious problems after updating to the latest release. In my opinion related to the management of AWS. Have you heard anything about this? Do you think there is a firmware in development?
-
Hi, today they made me make a change. Removed the following value: csc_report_cloud_fqdn = csc-report-bucket.s3.amazonaws.com
-
This is for example the uptime of the machine and the seconds of the AWS process. We don't use AWS. Time consumption seems anomalous. And when it consumes time it sends the core 0 to 100%
-
thanks for your support. support send me: "I went through my end the AWS task should not still present when the settings are not configured."