About eddiet82_

eddiet82_ · ‎07-14-2014

where are pages pulling these temples variables from? eg <title><% title FILTER verbatim %></title> <% welcome FILTER verbatim %> <% portal FILTER verbatim %> I imagine these would be defined in the system somewhere but cant find where, no doco and googling didnt find any answers i'm starting think these are hardcoded in juniper os? [edit] found them in http://www.juniper.net/techpubs/software/ive/admin/530-029895-01-CSPSolutionGuide.pdf was initially searching for the 'title' variable in that doco which doesn't appear. but the other 2 appear. in any case, it appears the default values are hardcoded. [/edit]

eddiet82_ · ‎11-11-2012

I've just upgraded my SA2500 to 7.3 and now the new terminal service client fails to connect via a proxy pac (attached excerpt of the proxy pac file "proxy.pac"). NC has the same problem. The SSH client is able to connect though. These workstations get the error "failed to resolve proxyHost" ( (attached file "notworking_debug.log"). Some workstations can connect (attached file "working_debug.log"). The notable differences in workstations (working vs not working) are: IE6 vs IE8 no AV vs SEP All workstations receive the same proxy pac file. Has anybody else got this problem? The current workaround is to specify the proxy statically, though this is not workable in all situations since some users are non-admins and are restricted by group policies from seeing the proxy settings. We were running 6.4 and everything was working fine. Is it possible to push down the older clients (eg 6.4) to users and keep the IVE version at 7.3? I noticed that JTAC recommends 7.2Rx for the SA2500...any ideas whether the clients are still working? Edit: On workstations with IE6 that was able to connect, I've upgraded to IE8 and now having the same problem: "failed to resolve proxyHost"

Re: Custom SignIn Page - Changing Text

failed to resolve proxyHost