Jump to content

Recommended Posts

Posted

We operate our Smoothwall filtering box in transparent/inline mode, so no users have a proxy address in their browser.

 

But sometimes users connect into a Citrix server (multiple sessions on one server) and Smoothwall can't determine individual sessions on the same box in transparent mode (and the vb script that runs).

 

Smoothwall have suggested pushing out the proxy address when users logon to Citrix, in this way Smoothwall can see each session as coming from a individual user, even though they are all logged onto the same host. They have also setup the config of Smoothwall to ignore Kerberos packets from the Citrix host (which I assume get sent by the script I mentioned).

 

But we don't want to push out the proxy address at the user level, as we don't want it accidentally remain in their profile when they logon to desktops, so I would prefer to push out the proxy at the machine level, so any users logging onto the Citrix host go out via the proxy, but it never gets added to their profile.

 

Does anyone have any experience of this or have any advice?

 

Kind Regards,

 

Bruce.

Posted
If the Citrix desktops are in a specific OU Loopback processing is your friend with this. There are 2 different settings in there just determine which one is right for your setup.
Posted
How about using netsh winhttp in a startup script?

netsh winhttp set proxy myproxyaddress:port

 

winhttp isn't the same setting as browser proxy setting though, right?

Posted
It's for the machine, which I take he wants to apply to his one Citrix host. I'm not saying it's the only way to do it, I'm just throwing another option out there :)

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...