Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Does anyone know where the profile should be located for this?We currently have a 'Profiles' folder in the same location as the .msi installation package.Within that folder there is a 'vpn' folder which contains our regular profile containing server ...
Last URL Filtering Update: 2019-07-21 23:14:51 As above, we've had no updates since late yesterday, and getting health monitor alerts today for it.Severity: criticalModule: URL Filtering MonitorDescription: URL Filtering download failure Have tried a...
Hi, Hoping someone can help. I'm currently working through a pxe boot and automated computer building setup.Once the OS is built and joins the domain, it is unable to authenticate without a reboot some 15mins later. This appears to be because the com...
Just had the Cisco Notification Alert email and this was listed: hostscan_4.7.00136-k9.pkg
However, directly below it is a new 4.6 version and this 4.7 version is marked as obsolete in that notification.
Was there something wrong with it, is it no ...
Appears to be quite a backward step to me.
This doesn't seem ready enough to replace the previous automatic installation option.
Apart from the Automatic Provisioning being made a secondary option to downloading the client, and this requiring user ...
answering my own question;I just found the patch removes the JndiLookup class from the classpath, which also satisfies the fix in 2.17 for CVE-2021-45046No need to patch again, yet
I see the patch for ISE 2.4 was released on 17th December. But looking at the timeline in the advisory, log4j version 2.16 has since been disclosed as vulnerable on 18th December. Anyone know if this means we are waiting for another patch to be relea...
Same here, but I am told that the issue is intermittent.Any help much appreciated, debugs I can use, etc.C2960X 15.2(6)EISE 2.4 Patch 5 ISE live logs says the dacl was sent to the switch successfully."show ip access-list interface gix/x/x" shows a de...
I have LDAP configured with LDAPS over 636 and that works fine, and can communicate securely. However, using the AD Connector there are no option for SSL, and I can see it is using LDAP over port 389 through our firewalls. As mentioned, LDAP and AD C...
I am also seeing this behavior in 2.4 as well as 2.6 patch 3My firewall logs are showing the connections to the Active Directory join point using 389 and there are no settings anywhere for changing to 636 and therefore SSL. Could do with some advice ...
