With CONNECTION Client, we receive "The Proxy server isn't responding". It shows that the correct proxy server/port ARE being used. However, we use an automatic proxy configuration script, which seems to be not supported or incompatible with the CONNECTION Client implementation. Is that so?
Thanks,
Bruce
Regards,
Tamicca SellarsMicroStation Product Manager
I've looked at the FAQ, and I see this note:
***Please note that this option only works if you're using the online SELECTserver. If you're using an in-house SELECTserver you'll need to create an exception on the proxy server for traffic originating from the CONNECTION Client.***
which is my case. Can you provide the details needed as part of "create an exception on the proxy server for traffic originating from the CONNECTION client"? What specifically should this exception contain?
As a a-side, when I installed CONNECT Update 4, the CONNECTION Client seemed to work UNTIL I rebooted, so I wonder what got changed once the reboot happened...
Thanks for the specifics, but something else is going on. After installing CONNECT Update 4, and one time since, upon rebooting my PC, I did get the login for CONNECTION Client. Usually all I get is this:
So, since it *has* worked (rarely) in the past, something else MUST be going on. Now, the time it worked, once I signed in, it showed there was an update to CONNECTION Client available. I was not able to download it via the CONNECTION Client (probably blocked by the firewall) but I did download and install the update from the Software Fulfillment Center.