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

Application mis identified

We have had problems at a number of locations where GroupWise traffic (tcp port 1677) is misidentified as Winny traffic and dropped due to application filters.

I wonder whether this would be possible/difficult to correct?

All are Astaro 8.3 with current signature files

This thread was automatically locked due to age.

0 towens over 13 years ago

I had the same problem, with the same application identified, with LDAP traffic from my Exchange server on a different subnet to a DC behind the ASG.
Cancel
Vote Up 0 Vote Down

Cancel
0 BrucekConvergent over 13 years ago in reply to towens

Your best bet in this case is to start an official support case with Astaro/Sophos support (if you have Standard or Premium Support) --- they will likely need to look at the traffic in question, in-depth, to correct the traffic awareness engine.

CTO, Convergent Information Security Solutions, LLC

https://www.convergesecurity.com

Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries. Use the advice given at your own risk.
Cancel
Vote Up 0 Vote Down

Cancel
0 BangkokBob over 13 years ago

I've opened a support case and I'll advise when resolved.
Cancel
Vote Up 0 Vote Down

Cancel
0 ceihelpdesk over 13 years ago

Have the except same thing happen. Groupwise clients over VPN are dropping randomly. Any luck on your end? I've just disable the application control for now.
Cancel
Vote Up 0 Vote Down

Cancel