On Fri, Jun 19, 2009 at 4:07 PM, David Lum <[email protected]> wrote: > I have a file/print/WSUS server that was using a lot of bandwidth > across my WAN. I stopped WSUS and Automatic Updates and > that had no effect, Stopping BITS did kill the traffic.
Makes sense. WSUS and AU tell BITS what to download. They don't actually do the downloading themselves. BITS notifies its clients (WSUS and AU) once the download jobs are finished. > Weird thing is 4 minutes alter the BITS process was started > by SYSTEM 9but the traffic did flood not resume), BITS doesn't start downloading right away. It tries to gauge Internet activity, bandwidth, and usage, and only use idle bandwidth. It doesn't always guess right, especially for WAN links in a corporate network. I seem to recall that BITS has some options to manually adjust its behavior, which can be used in situations like this. Check around in the MSKB. > Is there any way to find out what > process *IS* starting that service? I'm don't know, but if there, I would expect it to be in a log file. http://www.google.com/search?q=bits+log -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
