Windows XP automatic Update

[probinson]

I use an older version of the Wingate Client on my network.
Microsoft recently updated the Windows XP Update Process/Client and now it fails work properly giving an error code which is well documented but not specifically for Wingate issues.

Dispite WGIC not working, if I disable it and set Iexplorer to use the Wingate WWW.Proxy server instead, Windows Update works fine.

Can anybody suggest a reason why WGIC suddenly wont work with the new Windows Update Process/Client?

[jamesc]

What error code do you get?

What version of WinGate are you using?
Is it the same as the WinGate Internet Cleints?

(Are you also aware that your older version license will still work with our latest release? WinGate 6.0.4. Only features that were bought with your wingate license will be available though, which means any fixes that we have done, to the features you have already bought, will be supplied free of charge.)

[probinson]

The Windows update error code is 0e80072EFD.

I am using a Wingate 6.x professional licence on version 6.0.4 build 1025 of Wingate (and Gatekeeper).

I am using the WGIC supplied with WGSetup ver 4.3 because it does not require interaction with the Wingate engine before providing 'local' access only to applications (that's another story)

As I said this configuration worked fine for updates until microsoft upgraded it's 'Windows update' software in the past month or so.

[jamesc]

Have you tried disabling the WindowsUpdate page from caching?

Caching --> What to Cache
Select Specify which requests will be cached
Add Filter, Add Critereon
This critereon is "NOT" met if
HTTP URL "CONTAINS" windowsupdate

[probinson]

Hi James,

Thanks for the suggestion, I'm afraid it didn't work, I tried a number of variations of the windows update string, I even turned 'caching' off.

I suspect it migh be to do with the applications 'ban lists' I have set up in the Winsock redirector service.

It's so damn typical of Microsoft to upgrade software that then fails to work on otherwise perfectly functional proceedures!

Have you managed to reproduce the error?

Regards

Pete