ndClick 1.3 fails to connect on a multi-user environment for all users.
No errors are recorded to the ndClick Support Logging which indicates this is running on port 60500 successfully for all users. In a normal scenario, that is not possible as only one port binding per IP is permitted.
Browser Console shows errors connecting to all ports 60500 to 60550.
Figure 1. Example Chrome Console during NetDocuments logon
In this case, the Customer uses Palo Alto Terminal Services Client and this was not configured to allow ndClick to run.
This software client requires you to set the ports that users can access in multi-user environments.
Troubleshooting with running netstat -aob at an elevated command prompt on the server (or equivalent commands like PowerShell Get-NetTCPConnection ) revealed ndClickWinTray.exe wasn't binding to a port range we recognized and was binding to 20001-39999 range instead.
Figure 2. The incorrect port binding was seen in netstat -aob command (the output of this command is large and this is an excerpt.)
TCP 127.0.0.1:25281 SERVERNAME:0 LISTENING 12980
Figure 3. An example of binding that does work bound to 60500 as we expect.
TCP 0.0.0.0:60500 SERVERNAME:0 LISTENING 22472
You must configure the Palo Alto software to allow for port range 60500 - 60550 used by ndClick.
Please refer to this guide from Palo Alto.
once configured, ndClick will be allowed to access its port range.