Yes we are using RealSecure Network Sensor 7.0 updated to latest XPU, it
does not see Microsoft Windows Messenger 4.7 traffic that is on our
network in any zone it is happening. We are running it internal only so
all users have to talk to the exchange server.

Jeff

-----Original Message-----
From: Palmer, Paul (ISSAtlanta) [mailto:[EMAIL PROTECTED]
Sent: Monday, December 01, 2003 11:48 AM
To: Jones, Jeff; [EMAIL PROTECTED]
Subject: RE: [ISSForum] How to add Windows Messenger traffic on a
different port


Jeff,

You do not mention it, but I assume you are using RealSecure Network
Sensor version 7.0. If so, and you have a relatively recent XPU (within
the last few months), the sensor will automatically recognize Microsoft
Messenger traffic regardless of the port it uses. This works even if the
traffic is tunneled over port 80 as HTTP traffic or if it is routed
through an HTTP proxy. However, if your sensor is positioned on the
inside of a SOCKS proxy, it will not currently be able to recognize the
Microsoft Messenger traffic. The workaround is to position your sensor
outside (on the Internet side) of the SOCKS proxy.

Paul

-----Original Message-----
From: [EMAIL PROTECTED] On Behalf Of Jones, Jeff
Sent: Monday, December 01, 2003 10:44 AM
To: [EMAIL PROTECTED]
Subject: [ISSForum] How to add Windows Messenger traffic on a different
port




  Has anyone tried this? is it working? I did what Technical Support
told me to do, but I see no traffic reporting for the ports we have
assigned to messenger traffic.

Jeff

------------------------------------------------------------------------
-------------
This e-mail is the exclusive, private and confidential property of the
sender. The information contained in it is intended solely for the use
of the sender and the intended recipient. If you are not the intended
recipient you are hereby advised that any unauthorized disclosure,
copying, distribution or the taking of any action in reliance on the
contents of this message is strictly prohibited. If you have received
this e-mail in error, please notify us immediately by telephone (call
the USF Corporation Technical Support Center at 1-800-753-4563) and then
destroy this document and any copies in any form immediately.  Finally,
the recipient should check this email and any attachments for the
presence of viruses. USF Corporation accepts no liability for any damage
caused by any virus transmitted by this email.
------------------------------------------------------------------------
-------------

_______________________________________________
ISSForum mailing list
[EMAIL PROTECTED]

TO UNSUBSCRIBE OR CHANGE YOUR SUBSCRIPTION, go to
https://atla-mm1.iss.net/mailman/listinfo

-------------------------------------------------------------------------------------
This e-mail is the exclusive, private and confidential property of the sender. The
information contained in it is intended solely for the use of the sender and the
intended recipient. If you are not the intended recipient you are hereby advised that
any unauthorized disclosure, copying, distribution or the taking of any action in
reliance on the contents of this message is strictly prohibited. If you have received
this e-mail in error, please notify us immediately by telephone (call the USF
Corporation Technical Support Center at 1-800-753-4563) and then destroy this
document and any copies in any form immediately.  Finally, the recipient should
check this email and any attachments for the presence of viruses. USF Corporation
accepts no liability for any damage caused by any virus transmitted by this email.
-------------------------------------------------------------------------------------

_______________________________________________
ISSForum mailing list
[EMAIL PROTECTED]

TO UNSUBSCRIBE OR CHANGE YOUR SUBSCRIPTION, go to 
https://atla-mm1.iss.net/mailman/listinfo

Reply via email to