I've noticed an issue with the 7.3IVE releases R1 and R2. When using Terminal Server Resource Profiles and a client that uses an auto configuration proxy file (pac) tries to connect the Terminal Server wrapper ignores the proxy pac file and tries to connect directly without going via the proxy as specified in the file.
It does work if the browser is configured with a static proxy entry though, just not when using the auto configuration files.
Anybody else seeing this issue?
Not sure what you mean by type of proxy.
The users browsers can't access the internet directly from the corporate network and have to use the proxy that is specified within the pac file. The pac file is configured in the browser via the proxy auto-configuration file settings to point to an internal server http://server.domain.com/proxy.pac, this then specifies the various exceptions and specific proxies for certain resources and should nothing match provides the proxy.company.com:8080 for clients to access the internet. The actual proxy is a BlueCoat.
If while the RDP profile is trying to connect I can see from a packet capture and netstat that the connection is attempted directly and not going via the proxy, hence is fails.
I was testing this on the DTE release before considering an upgrade to a production system as also looking at the IPv6 capabilities.
The proxy uses no authentication it is simply for filtering inappropriate content.
On the IVE for testing I'm using local username and password.
I've finally had a chance to look at the client debug logs and can see it detects that it should use the correct proxy but then get the following error before it tries to connect to the gateway directly.
00168,09 2013/02/28 14:33:11.420 1 <USERNAME> dsTermServ.exe dsTermServProxy p9436 t958 ncp.cpp:488 - 'ncp' getaddrinfo failed to resolve proxyHost proxy.intra.domain.com, err 10109
Which is strange as the machine can resolve and use the proxy server fine.
do you have the proxy set as static or PAC?
can you confirm you don't have "auto detect settings" enabled?
your best bet may be to open a case in order to have a JTAC rep review the entire log
Just wondering if anything was done to resolve this issue or a workaround put in place?
I have the same issue where a proxy pac is configured on client machines and trying to uses the juniper terminal services client.
Autodetect not enabled
Agree I also may need to log with JTAC but just curios if that was doen for this case to save some time.
I believe the issue was fixed in release 7.4R3 and equivalent updates in the different release versions. Although I can't see it listed as an issue or fix in the release notes.