02-18-2013 04:09 PM - edited 03-04-2019 07:03 PM
Just wanted to know if there is the possibility of creating QoS rules for Symantec Endpoint Protection so that when end devices are updating over the network, it doesnt hog the bandwidth. We are currently QoS'ing for Print and Citrix traffic. The only info i can find is that it uses TCP but this doesnt help. I also have the server port number but the destination ports are always different.
Routers have IOS from 12.2 - 15.1 and are 2801 and 881 models.
Any feedback is appreciated
Regards,
Solved! Go to Solution.
02-19-2013 02:26 AM
Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
From what you described, you could probably fairly safely identify this traffic as TCP sourced from a particular IP and source port. With this information, you could deprioritize this traffic relative to other traffic.
02-19-2013 02:26 AM
Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
From what you described, you could probably fairly safely identify this traffic as TCP sourced from a particular IP and source port. With this information, you could deprioritize this traffic relative to other traffic.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide