We've got some W2K servers that need to run Windows Update and auto-download
patches etc.

We have SSL authentication enabled in Bordermanager that works fine in the
browsers on the W2K servers, but the Windows Update only works if you first
authenticate *manually* through the Bordermanager SSL authentication screen,
then run auto update. However as we have a 30 minute idle time disconnection
in SSL when the W2K next tries to perform a Windows Update it fails.

Windows Update setup includes a section to define the address of a proxy
server with an id and password etc, but this always fails if the
authentication isn't made first as above. Is there no way to get
Bordermanager to accept an id and password for SSL authentication in this

(Our BM server only proxies and has no active firewall function).


Steve Law