Hello,
Thank you for your response.
I attempted to connect via Test-Connect from that screen, but the connection failed.
The issue is that it's difficult to determine where the communication is being obstructed using Wireshark.
Embarrassingly, our company has weak network maintenance along the route.
I would like to at least confirm where along the route the problem lies,
so it would have been helpful if this test connection had a feature similar to traceroute.
Internet - Firewall - CATO Socket - Network devices ... Network devices - LDAP Server
Cato EmployeeHey HD,
We do have a traceroute and ping functionality within the socket that you can run from the UI of the socket -https://support.catonetworks.com/hc/en-us/articles/4413273496209-Managing-Sockets#heading-8 which you can send WAN or LAN.
Unfortunately, nothing similar when using the LDAP test functionality.
What I could suggest is maybe running a tracroute or pathping from your LDAP server to the socket LAN interface (to first confirm it can indeed reach the socket), then you could run the same but this time from LDAP server to the IPs which I shared with you.
At the same time, running a PCAP on the socket and possibly your switches in your LAN.
