Sonicwall Directory Connector Please Check the Server Connection and Try Again
Troubleshooting Single Sign-on (SSO) related errors
12/06/2021 
2,050 People found this article helpful 
113,399 Views
Description
This article guides you to significantly reduce and troubleshoot Single Sign-On (SSO) agent related errors reported nether Logs and TSR (Tech Support Report).
Resolution
Beneath is a screenshot of the Enforcement tab on the SSO configuration properties dialog box. Is accessed from Manage| Users |Settings| Configure SSO.
- Nether Enforcement in SSO Featherbed y'all tin featherbed SSO and allow services, hosts, networks or range of IPs to send their traffic through the SonicWall without having to go through user hallmark via SSO. This is vital for devices who do not require user authentication via SSO such as Macintosh Apple Computers, iPads, Printers and Smart phones or Servers that practise not run with a logged in user.
Troubleshooting Errors:
One of the kickoff step in getting down to reducing the SSO Errors and connection issues is to pull a TSR and accept a look at the IPs that are giving errors.
EXAMPLES:
- Probing failed: This is typically caused by Windows firewall or another third political party firewall or anything that would be blocking as the probe is coming from the SonicWall itself to check if the ports are open up for selected query blazon before sending information technology to the SSO Agent.
- Amanuensis did not respond: This error is self-explanatory, the SSO Agent did not respond to the SonicWall query for information on the IP.
- Confirm agent is not installed on the Advertizing server every bit typically Advertizement has to process other requests and could pb to performance issues. With this error you may desire to consider calculation another Agent depending on the corporeality of users beingness queried for SSO Authentication.
- SSO agent reported: OS Error -21477217406: This fault is typically caused past a WMI failure.
When no user bone logged in, WMI gets a response as "getFields failed" which is represented by SonicOS as a negative number.- This is not indicative of a user identification failure. NetAPI alone can exist used in this scenario to avoid this mistake.
- Mistake: Error(51) Unknown Error: This error commonly means the IP accost is a Windows machine, but access to TCP 445 (part of File & Print sharing) is blocked.
- Normally error 51 is caused past Windows firewall or another 3rd party firewall or anything that would exist blocking File and Impress Sharing.
- Agent reported error - OS error [53] Network path not constitute: This error could be due to:
- the unit of measurement is not a Windows PC
- If the IP showing this error is a Windows PC then:
- cheque if whatever Windows Firewall, Defender or any Anti-virus software may be blocking the query.
- Confirm that File and Print Sharing is enabled on the Windows PC.
- Amanuensis reported error - OS error [five]: Access denied: This is oft an SSO agent service error every bit information technology may not be running nether domain admin or practise non have the admin rights.
This can happens if the countersign was gear up to expire on the account that is running these services, and the countersign has expired).
To troubleshoot error 5 on the SSO amanuensis, bank check the post-obit:- Check the SSO agent service logon business relationship. This must be a domain administrator, and it must have countersign never expired enabled and excluded from any countersign policy
- Logon to the agent automobile equally the domain administrator account assigned to the SSO service and run a net view \IP from control prompt of the auto you are trying to authenticate. If no fault displays, then it means the SSO amanuensis is resolving the proper name properly.
- If the above two steps did not pb you to whatever resolution, check the target figurer for software firewalls in the anti-virus programs.
For example, Trend Micro has a software firewall that volition cause this specific error rather than error 51.
TIP: SSO Agent and Ports: NetAPI Ports = 445 and 139 & WMI = 1726 and 135 SSO Agent Default Port = 2258 & TSA Agent Default Port = 2259.
NOTE: Error 51, 53, 21477217406 are ordinarily client related errors and need to be troubleshooted on the clients. Error 5 may be a SSO Agent Service mistake and it may need to be troubleshooted on the Server on which the SSO Service is running.
Related Articles
- How to Revert the GUI back to UI7 on Gen7 firewalls?
- Configure probe monitoring for WAN Failover and load balancing
- How to change admin password using CLI in SonicWall Firewall?
Categories
- Firewalls > TZ Series > User Login
- Firewalls > SonicWall SuperMassive 9000 Serial > User Login
- Firewalls > NSa Series > User Login
- Firewalls > NSv Series > User Login
Was This Article Helpful?
Yep
NO
campbelloffam1958.blogspot.com
Source: https://www.sonicwall.com/support/knowledge-base/troubleshooting-single-sign-on-sso-related-errors/170503257427051/
0 Response to "Sonicwall Directory Connector Please Check the Server Connection and Try Again"
Post a Comment