Closed gdubya closed 11 years ago
PS Thank you for your hard work! :)
I can't reproduce this problem. According to the documentation for my version of NC, the -P option specifies the remote port to connect to and indeed that's how it works for me. In fact, since we don't send a URI to the ncsvc command but just a hostname, without specifying the port the ncsvc command has no way to know that we're using HTTPS vs. HTTP. Are you sure you didn't fill in the proxy settings fields by accident?
Can you run ~/.juniper_networks/network_connect/ncsvc -v and copy the results here? Maybe there's a difference between different versions of NetworkConnect?
Hm. I might be wrong. The -P option is documented as assigning the "service port". That port might indeed be some local port used by the system and not the remote port we connect to. Unfortunately I have no way to test this. I'll make a change to the UI to allow it to be set separately.
I believe you're right about the -P option. I removed it from the UI (so it's not set by having a port on the server name, etc.) However now there's no way to add this value from the UI. I can't find any documentation about what it does, so I'll leave it like this until/unless someone reports they need it.
The host for our VPN is on HTTPS, so the msjnc profile has set the "port" property to 443. This is passed to the ncsvc client command as the "-P 443" option, however I don't think this works as intended as the ncsvc client appears to try and bind to my local port 443 rather than the remote vpn host. My local 443 is already in use by VMWare workstation server.
I have seen this same problem reported somewhere on ubuntuforums.
Editing my local msjnc profile to remove the value for "port" fixes the problem.