This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

User authentication for web proxy not working from Terminal Server

I have been running for a while with Transparent mode. Recently needed to separate VIP's from Mere Mortals for Web Surfing, so thanks to Bob's excellent guide, I got AD Authentication and HTTP/S Profiles setup and enforced use of the proxy with Group Policy on the Windows 2003 Server. Using an ASG 120 with 7.509

User's from their desktops seem to be authenticating correctly (although in the web log I see something like user="Mere Mortal" Filter Action=(VIP), when it should say "Default Filter Action") but it seems to be working, Mere Mortals cannot open social media sites and VIP's can.

EXCEPT, when logging into the Terminal Server. There a VIP still cannot open Facebook. The HTTP log shows User="" so it seems like the user id is not being passed from the Terminal Server.

Is there any fix for this?

This thread was automatically locked due to age.

Parents

0 mrainey over 14 years ago

If I am logged onto a member server as Administrator, and I RDP to the TS as myself, the result is the same. The URL log shows user="" and the Default Filter Action is applied. I have opened a support ticket and hope to get a resolution. I modified the Group Policy for the TS as suggested here Advanced Proxy add-on for IPCop and SmoothWall but it did not seem to make any difference.
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 mrainey over 14 years ago

If I am logged onto a member server as Administrator, and I RDP to the TS as myself, the result is the same. The URL log shows user="" and the Default Filter Action is applied. I have opened a support ticket and hope to get a resolution. I modified the Group Policy for the TS as suggested here Advanced Proxy add-on for IPCop and SmoothWall but it did not seem to make any difference.
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data