cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
736
Views
0
Helpful
2
Replies

how to add custom agents - Windows Live Messenger

angfeglandagan
Level 1
Level 1

hi, i am having trouble with windows live messenger.

I used only 1 IDENTITY in my WSA via LDAP.
my ldap queries work fine across 3 LDAP servers.

I created multiple access policies and associate the IDENTITY with it...

My problem is;

Yahoo messenger, aol, meebo run pretty smoothly across users associated with my access policy except for the WINDOWS LIVE MESSENGER.

I have downloaded the windows live messenger...i can access it without the proxy..

I already allowed the CHAT category, INSTANT MESSAGING.

Any suggestions on how i am going to make it work?

im thinkin of customizing a url then associate with the policy.

the problem is, what are the specific sites that messenger is using..

as per ironport cisco web category - live.com is categorized as COMPUTING / INTERNET which is already allowed in my url categories.

need your input on this..

im running 6.0 version of asyncos

2 Replies 2

jowolfer
Level 1
Level 1

I recommend grepping the accesslogs to see what action the WSA is taking for this traffic.

It may be that you are inadvertently blocking it. Or it might be that your auth policies are causing it to break, since it may not be configured to send credentials.

To grep the access logs for this entry, run the following from the CLI:
------------------------------------------
1. Grep
2. Enter the number of the log you wish to grep: 1 (for accesslogs)
3. Enter the regular expression to grep: .*
4. Do you want this search to be case insensitive?: Y
5. Do you want to paginate the output?: N
------------------------------------------

angfeglandagan
Level 1
Level 1

hi josh, i already performed those steps before.on the logs i saw different categories..

it seemed that when i do associate my identities to the access logs..

with chat being allowed it didnt work..the policy was being hit and the url categories too...

i read about version 6.3..does this solve the problem? or categorization?

im running version 6.0 so i believe cisco web content will be used?