Adding the LDAP Account Unit worked also without errors, but during the AD Query activation it failed again to connect like before. I also tried to add a LDAP Account Unit before activating the Identity Awareness blade, so that you can choose it from the dropdown within the configuration wizard. ![]() A secure remote access solution promotes collaboration by connecting global virtual teams at headquarters, branch offices, remote locations, or mobile users on the go. I did a packet capture on the AD server to check if there is any traffic from the security gateway to the AD server during the activation of AD Query within the Wizard, but there are no packets arrived on the AD server. Remote Access VPN ensures that the connections between corporate networks and remote and mobile devices are secure and can be accessed virtually anywhere users are located. ![]() I also activated Browser-based Authentication which I could test successfully from my test client. I moved on with checking the box "Ignore the errors and continue to configure the LDAP account" and put in the login DN which worked fine. I can connect to the AD server without any error from the cli on my security gateway using " test_ad_connectivity" and "ldapsearch" but from SmartDashboard it does not work. ![]() I did several troubleshooting things like mentioned on the link below: "SmartDashboard could not connect to x.x.x.x - Could not communicate with server." I tried to test the Identity Awareness Blade on my lab and connect to a AD server but always got the error message on SmartDashboard (R80.30):
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |