Hi again from Michigan: Does anyone know the port number(s)
used by Microsoft's download manager? Works only when ipflt
is unloaded so I guess I have to add a filter or two. I
just don't know what ports it uses.

Thanks, Chris.

You mean for Windows Update?

Have a look at tip #29 at the URL below. Windows Update BITS process
does not use your IE proxy settings. Using the proxycfg command may
help you.

Craig Johnson
Novell Support Connection SysOp
*** For a current patch list, tips, handy files and books on
BorderManager, go to http://www.craigjconsulting.com ***

No. MS has a separate Download Manager for use on their
Software Assurance fulfillment site. It looks a lot like
other DL managers (like Sun's). The kind manager that can
resume from a disrupted download.

Chris



>>> On 6/24/2008 at 8:01 PM, in message
<VA.00003f5a.04a1c57e@ix.netcom.com>, Craig
Johnson<craigsj@ix.netcom.com> wrote:
> You mean for Windows Update?
>
> Have a look at tip #29 at the URL below. Windows Update
> BITS process
> does not use your IE proxy settings. Using the proxycfg
> command may
> help you.
>
> Craig Johnson
> Novell Support Connection SysOp
> *** For a current patch list, tips, handy files and
> books on
> BorderManager, go to http://www.craigjconsulting.com ***

More than likely it's using 80 or 443 and not using the proxy. If you
know the destination IP address (and hope it's not a supernetted
network), you can set up a single stateful exception to allow the
traffic to that destination. (As an experiment, you can add
www-http-st from private to public and see if that works. If so, add
the destination address as a restriction and test again. If http
doesn't work at first, try www-https-st to allow port 443 instead of
80. Might need both...)

Filter debug will tell you exactly what it is using, or pktscan.nlm on
the server, or a wireshark trace of the traffic.

Craig Johnson
Novell Support Connection SysOp
*** For a current patch list, tips, handy files and books on
BorderManager, go to http://www.craigjconsulting.com ***

Thanks, will look and see. Chris.



>>> On 6/28/2008 at 1:10 PM, in message
<VA.00003f62.17c302bb@ix.netcom.com>, Craig
Johnson<craigsj@ix.netcom.com> wrote:
> More than likely it's using 80 or 443 and not using the
> proxy. If you
> know the destination IP address (and hope it's not a
> supernetted
> network), you can set up a single stateful exception to
> allow the
> traffic to that destination. (As an experiment, you can
> add
> www-http-st from private to public and see if that works.

> If so, add
> the destination address as a restriction and test again.
> If http
> doesn't work at first, try www-https-st to allow port 443

> instead of
> 80. Might need both...)
>
> Filter debug will tell you exactly what it is using, or
> pktscan.nlm on
> the server, or a wireshark trace of the traffic.
>
> Craig Johnson
> Novell Support Connection SysOp
> *** For a current patch list, tips, handy files and
> books on
> BorderManager, go to http://www.craigjconsulting.com ***