Skip to main content
sethadrian
New Member
October 12, 2016
Question

Bandwidth is consumed and not recovering when windows update is triggered.

  • October 12, 2016
  • 16 replies
  • 28933 views

Hi Guys,

 

Need your help on this.  I have a FG100D with two ISP connections configured to perform LLB.  Firewall is working okay except at point when servers and allowed PCs are doing windows update.  It seems that the Bandwidth is exhausted even if the windows update app control is shaped to 1Mbps.  Worst part is even if the update is already downloaded, the bandwidth does not recover and continuously exhausts resulting to slow internet connection.  also I am seeing a session clash log under system events.  Anyone have fix on this? need help.

 

Regards,

Seth

    16 replies

    retrotech
    New Member
    October 14, 2016

    You didnt specify what version of Windows you are running, but if you are running Windows 10 (especially combined with the newest office), it could be the culprit. The updates may be downloading (and pushing out to others on the Internet) via P2P. This is the default setting (which can be changed). On top of this, the updates are fairly large. The updates will download whenever it feels like it if you are in a non-domain setup like us (we're a small business with no need for the extra complexity and cost). Rather than increase bandwidth, we setup policies to block Windows and Mac OS updates plus Office updates via app control an hour before and up to an hour after work hours and then allow those connections on nights/weekends. We also segmented a few static IPs to use for I.T. staff to do manual windows updates during the work day if needed. So far its been working well. This may or may not work in other situations, but works for us. We'd also like to hear others solutions if anyone else has any.

    sethadrian
    New Member
    October 15, 2016

    Hi retrotech,

    thank you for your reply.  you are right it is a windows 10.  regarding your suggestions to create scheduled policies for windows updates, it can be done there is no problem with that.  The only thing that i am concerned about is that how come that even after the windows already finishes the updates and is in idle already, the bandwidth does not recover and still it consumes the entire allocation?  Have you encountered those instances?

     

    retrotech
    New Member
    October 17, 2016

    Sorry, we didnt pay that close attention when it was happening. Makes me think it's something with the way Windows 10 does P2P update sharing? If thats the case, maybe the "Choose how updates are delivered" setting might affect that? (Or maybe not?) If anyone has any solid or confirmed information i'd be interested to know as well.

    sethadrian
    New Member
    October 18, 2016

    tanr,

     

    this is good stuff you just gave me.  I have one question though, if in case the P2P update sharing on network is enabled, should it be internal network's bandwidth that should be consumed and not the bandwidth that is going to the internet?  seconde question, assuming that PC A have already received the windows update and is ready to share these updates outside of internal network and send it who ever receives it,  should it be the upload BW that should be consumed and not the download BW? analyze further on your response.

    tanr
    New Member
    October 18, 2016

    Hi Seth,

     

    I believe the default Windows 10 setting gets updates from and sends updates to PCs on both the local network and PCs outside your network.  So I would expect it to effect your bandwidth going to the internet.

     

    You make a good point in your second question.  If all your local PCs are fully updated, I wouldn't expect them to be actively downloading more.  Hopefully they're not downloading updates that your local PCs don't need but that other PCs in your area are requesting.  Or getting inundated by requests from those other PCs.

     

    Thought Leadership Security Summit. Outpace New Threats with AI - enhanced defense. Tuesday, Septmeber 15, 8:30 AM - 2:30 PM PT. The Golf Club at Newcastle, WA.
    Fortinet Flag the Hack. Wednesday, August 26, 9:00 AM - 5:00 PM ET, COSM, Atlanta, GA.