Tech Support > Operating Systems > Auto-Update failing when behind firewall
Auto-Update failing when behind firewall
Posted by Steven Krapes on August 22nd, 2003


Within our corporate firewalled LAN, the Automatic Update feature in
XP/Win2K does not work. Using the browser on windowsupdate.microsoft.com
thru our proxy works fine. The dates in the Windows Update registry keys
indicate that our PC's are trying to connect but never get an answer. When
one of those PC's are connected directly to the internet, auto-update works
fine.

Does the Automatic Update feature (aka Windows Critical Update Notification)
use ping or some other protocol to detect that it has an Internet
connection? I saw a registry key called PingID. Uh Oh. Our firewalls
block ICMP packets. If ping is used, then what address is being pinged?
Thanks
- steve


Posted by Lucy [MS] on August 25th, 2003


Automatic Update requires a proxy that support HTTP 1.1 protocol and it
connects to the proxy listed in the following registry key.
HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\Cur rentVersion\Internet
Settings


Thanks,
Lucy [MS]

This posting is provided "AS IS" with no warranties, and confers no rights.





"Steven Krapes" <s-k-r-a-p-e-s@att.com> wrote in message
news:e71qtdLaDHA.1832@TK2MSFTNGP10.phx.gbl...


Posted by Chris Read on August 28th, 2003


I too have a problem with autoupdate not working (XP home
single computer over ADSL) though I can connect manually
without problems. I am using Zonealarm Pro. What
settings should I be seeing in this registry key?

I have one marked AutoConfigProxy with value wininet.dll

I can't see any other keys likely to be relevant.

Regards

Chris


Similar Posts