Re: Reporting show IP instead of username or computername



thanks Edgardo and Philip for the valuable advice....

1) Yes. i need to turn on web proxy just for showing username in
reporting.....
2) Some how this citrix is a web site in https.. when signing in they will
pop-up another windows showing 'loading Thin components'.. i not sure what is
loading too... but is will eventually timeout... i get this will my access
rule for http/https are 'Authenticated users' (ad users). But if i change to
'all users', the 'loading Thin components' will go thru and go into the
citrix server.. all connection is via https....

"Edgardo B." wrote:

Hello Windows fan:

"Phillip Windell" <@.> wrote in message
news:ubM34wXDHHA.4024@xxxxxxxxxxxxxxxxxxxxxxx
"Windows Fans" <WindowsFans@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6155BFCA-32CD-4E4C-8DD7-CC556372B287@xxxxxxxxxxxxxxxx
1) On the client, Can i specify the gateway as ISA and also specify the
the
proxy in IE?

You just do it. But why? What is the point in the ISA being the Default
Gateway if the client is not a SecureNAT Client?

If you are using ISA as default gateway, it is certainly possible to also
specify ISA as the proxy. To get your logs to show usernames instead of
anonymous, ensure you perform what Phillip mentioned before:
"1. Stop allowing "All Users""

Try, "All Authenticated Users" group instead under the "Users" Tab in ISA
Management when creating an Access Rule. After you have verified that
usernames are appearing, you can further restrict users as necessary and use
another group besides, "All Authenticated Users."


2) i have tried to create custom group for my AD users. But end up when
they
initiate a citrix session in the USA via https. But if i change to all
users
then is working...

I have no idea what you are asking there.


I'll try to guess what you are attempting to indicate =)

When you use a custom group for your AD users Citrix doesn't work? Like my
previous suggestion, give the 'All Authenticated Users' group access (Remove
'all users' as well), to confirm you have authentication able to function.
Verify you are using accounts from the domain and not creating new local
accounts on the ISA machine.

All these are giving headache..... i appreciate your help

I have found the documentation at
http://www.microsoft.com/isaserver/default.mspx a good resource for
alleviating ISA related headaches.


Goodbye!
Edgardo



.



Relevant Pages

  • Re: ISA server 2004 and Bluecoat proxy
    ... i want to mention that we have configured a backup rout (backup bluecoat ... i want to ask about event 14130 that related to web proxy chain fauilire. ... If you were able to work around the upstream proxy server, ... upstream ISA Server, you might want to change it back. ...
    (microsoft.public.isa.configuration)
  • Re: Site2Site VPN - Web page requests returns FWX_E_TERMINATING
    ... have?Firewall client or Web proxy clients?If you are using FWC is normal ... to use proxy locally and create an exception for your web site. ... in them,...this causes them to be interpreted by Internet ... Understanding the ISA 2004 Access Rule Processing ...
    (microsoft.public.isa.vpn)
  • Re: Site2Site VPN - Web page requests returns FWX_E_TERMINATING
    ... The browser has a proxy deny rule to point allow all mab.intra traffic to go ... bypass the proxy within the ISA server. ... them,...this causes them to be interpreted by Internet ... Troubleshooting Client Authentication on Access Rules in ISA Server 2004 ...
    (microsoft.public.isa.vpn)
  • Re: access only to one external site
    ... In the same page that contains the checkbox above, make sure that ISA ... Microsoft Firewall service and Microsoft Web Proxy service are started. ... On a test client, login using the test user account, make sure that IE ... destination set, he should access them normally, any other sites should ...
    (microsoft.public.isa.configuration)
  • Re: HTTPS Using Web Proxy
    ... The ISA log displays the following on the error. ... HTTP Method = ... I created a HTPPS 444 protocol set to TCP port 444 and assigned it to my ... At first I was getting a error code: 502 Proxy Error and fixed that by ...
    (microsoft.public.isa)

Loading