Search results

  1. PCI Scan Fail - tcp5001 supports SSLv3 and TLS1.0

    Tried this this morning, and it worked ! Caveat - You do need to make 2 entries in the registry even if you are running 4.6.2 (at least in my experience). [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319] "SchUseStrongCrypto"=dword:00000001...

  2. PCI Scan Fail - tcp5001 supports SSLv3 and TLS1.0

    Awesome. I will try this tomorrow and report back. Being able to give the boss presence detail on his Smartphone, and still keeping the PCI compliance will make everyone very happy ;) Thanks !

  3. PCI Scan Fail - tcp5001 supports SSLv3 and TLS1.0

    The VPN solution is workable, and my firewalls support it - but it seems silly to have to jump through all these hoops to solve what should be a simple update to the windows client to support TLS 1.2. The Android and Iphone clients already do, and NGINX certainly does. The client appears to use...

  4. 3CX Management Console Service will not Start

    I had this problem when I first installed, and it was the C++ 2015 runtime wasn't completely installed. If it has been running already, maybe something else deleted or corrupted one of the runtimes ?

  5. Dell sonicwall woes, unmatched mapping.

    No problem - hopefully it gives you enough to get it working :)

  6. PCI Scan Fail - tcp5001 supports SSLv3 and TLS1.0

    Still hoping for something here ;)

  7. Dell sonicwall woes, unmatched mapping.

    Ok, lets see how this works ;) First I made sure the upgrade worked properly, and I was on the right firmware : Attachment_1 Next, I created all the ports I needed in Firewall-Service Objects Attachment_2 Then I added the ports to a Service Group to make life easier. Attachment_3 I then...

  8. Dell sonicwall woes, unmatched mapping.

    PM Sent - although it seems to be sat in the outbox...

  9. Dell sonicwall woes, unmatched mapping.

    I can confirm 5.9.1.7-2o works fine. There is an addition setting you have to set tho. On the OUTBOUND rule, under the ADVANCED tab, you should have the 'Disable Source Port Remap' option checked. If that doesn't help, PM me and I'll shoot you some screenshots from my own setup that works fine...

  10. PCI Scan Fail - tcp5001 supports SSLv3 and TLS1.0

    1. SSLv3 is a mistake on my part - the original report I had stated both TLS1.0 and SSLv3 2. My Admin port runs on 5001, not 443, and SSLLabs won't let me test on 5001 and I already have a site on 443. However, a number of other test sites all indicate that TLS1.0 is supported via port 5001...

  11. PCI Scan Fail - tcp5001 supports SSLv3 and TLS1.0

    Figures...fix one thing, break another. Is it just remote Windows clients that break, or local-subnet ones too (I'm working remote today, so I cant easily check in the office where I'm testing!!)

  12. PCI Scan Fail - tcp5001 supports SSLv3 and TLS1.0

    I'd even be happy if I could separate registration/presence functions and the admin console. I'm kinda suprised those use the same port, seems like that should be a simple matter of running a second web instance for the two functions internally.

  13. Firewall Test Fails - unmatched mapping (4029) (On 5060)

    We had this on our Sonicwalls. The latest Firmware upgrade on the firewall fixed it. Not sure what your setup is, but look for 'Source Port Remap' or a similar option in your NAT/Port Forward rules and disable it.

  14. PCI Scan Fail - tcp5001 supports SSLv3 and TLS1.0

    Having got our 3CX PBX running for a trial period, we have run into one problem with our external PCI Vulnerability scan. Apparently, the HTTPS Webserver integrated with the 3CX PBX supports SSLv3 and TLS1.0, which are automatic fails now with the new PCI DSS 3.1 standard. I can request an...
View older results
3CX Logo Footer Copyright © Sitemap Privacy
Top Bottom