Windows update doesn't work through the wingate client
Nov 18 05 7:30 am
Windows update doesn't work through the wingate client, when i do a static address in IE it works fine.. what do i need to do?
Russ
Russ
Nov 18 05 8:34 pm
What error message via WGIC?
Do you have any Intercepts setup; what ports? The location to check is in the image below.
Do you have any Intercepts setup; what ports? The location to check is in the image below.
wupdate solution
Nov 23 05 2:53 pm
Hi
I spent weeks on this, theres basically 3 things you need to do
1) zone security, make sure to add windows update servers domains
in iexplorer
e.g.
If your Internet connection uses a proxy server, add the Windows Update sites to the proxy settings exceptions in Internet Settings. To do this, follow these steps:
-Open Internet Explorer.
-Click Tools, and then click Internet Options.
-Click the Connections tab, and then click LAN Settings.
-Click Advanced, and then type the following text in the Exceptions text box (all in one line):
update.microsoft.com;windowsupdate.microsoft.com;v4.windowsupdate.microsoft.com;download.windowsupdate.com
Note If you are running third-party proxy or firewall software, see your product documentation for information about how to add these sites to the exception list for those applications.
Click OK to close all Internet Options windows.
OR...
STEP 1. TRUSTED SITES vis Security TAB.
Add the Windows Update Web sites to the list of trusted sites
You may be able to resolve this issue by adding the Windows Update Web sites to the list of trusted sites. To add these Web sites to the list, follow these steps: 1. Start Microsoft Internet Explorer.
2. On the Tools menu, click Internet Options.
3. Click the Security tab.
4. Click the Trusted sites icon, and then click Sites.
5. Click to clear the Require server verification (https:) for all sites in this zone check box.
6. Add the following Web sites:
• http://Windowsupdate.microsoft.com
• http://V4.Windowsupdate.microsoft.com
• http://Download.Windowsupdate.com
• https://v4.Windowsupdate.microsoft.com
• http://V5.Windowsupdate.microsoft.com
• https://V4.Windowsupdate.microsoft.com
Note This entry uses the https prefix.
Easier to do It Appears?
http://*.windowsupdate.com
https://*.windowsupdate.com
Step2
Add the Windows Update Web sites to the list of exceptions
Add the Windows Update Web sites to the list of exceptions for proxy settings. To do this, follow these steps: 1. Start Microsoft Internet Explorer.
2. On the Tools menu, click Internet Options.
3. Click the Connections tab, and then click LAN Settings.
4. Click Advanced, and then add the following Web sites to the Exceptions list. Instead of listing each URL on a separate line, use semicolons (;) to separate the URLs as follows:
http://Windowsupdate.microsoft.com; http://V4.Windowsupdate.microsoft.com; http://Download.Windowsupdate.com; http://V5.Windowsupdate.microsoft.com
2) router MTU settings
Okay, what fixed it for me was to look at my Cisco 837 router that is hooked
to my DSL connection. On the dialer interface, I adjusted the default MTU of
1500 to 1492 as per some Cisco documentation I was reading. As soon as I made
the change, BANG, it worked. It hasn't failed again since and I have now
updated to SP2 without issue.
Microsoft, PLEASE add this to your document so that others don't have to
spend as much time as I did finding the answer.
I do not no how to make these adjustments on routers other than the Cisco,
so I am probably not much help beyond letting you know that it is something
you should look at. Your ISP may be able to help and would be a better
resource I'm sure.
3) since updater used WINHTTP you need to make sure proxycfg -u
is done to match your IE connection settings to that for winhttp !
e.g.
More Information:
Most technical people are familiar with setting up a Windows workstation to use a proxy server. There use to be only one or two settings one had to be worried about. Now, it appears, there are three. The first two are expected and should be well understood. The third setting is unexpected and does not get changed when you make adjustments to the first two.
The first setting required to set up Internet Explorer to use a proxy can be found under the Tools Menu, Internet Options menu pick. Once you have opened up the Internet Options, click on the Connections tab, then click on the LAN Settings Button. Under the Local Area Network screen, make sure the Use A Proxy check box is checked and the Address and Port fields are filled in with your Proxy Server settings.
The second type of proxy service provided by the ISA server is that provided by the ISA firewall client software (sometimes also called winsock services). The use of the firewall client is optional. The ISA firewall client services applications that ignore the IE settings for proxy services, and/or applications that contain their own proxy settings, and/or applications that do not support proxy server settings at all. If you have loaded the ISA Firewall Client, be sure you have enabled it.
The third setting apparently influences the behavior of Windows Update Control. Microsoft has Knowledgebase articles that discuss making changes but their mindset is from a standalone workstation with direct internet access and not the workstations that sit behind ISA firewalls.
Workaround / Solution:
On the XP workstation
Click on Start, and then click Run.
Type cmd in the Open box to get a DOS prompt.
Type proxycfg -u at the command prompt, and press Enter.
If you type in the proxycfg command without any options, you can see what Windows wants to do with winHTTP requests. On my machines that were having Update errors, even with Use A Proxy checked, the proxycfg command reported the following;
Current WinHTTP proxy settings under
HKEY_LOCAL_MACHINE\
SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\Connections\
WinHttpSettings :
Flags = PROXY_TYPE_DIRECT
Proxy Server = -not set-
Bypass List = -not set-
After I ran the proxycfg -u command, the proxycfg command reported:
Current WinHTTP proxy settings under
HKEY_LOCAL_MACHINE\
SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\Connections\
WinHttpSettings :
Flags = PROXY_TYPE_DIRECT | PROXY_TYPE_PROXY
Proxy Server = isa:8080
Bypass List = -not set-
For what ever reason, Windows does synchronize the proxy settings when the user makes changes to the Internet Options proxy settings. Apparently this only has significant impact on the Windows Update Control as all other Internet Enabled programs seem to work just fine even when the winHTTP proxy settings do not agree with the user entered proxy settings.
===
here is a use set of commands for a batch I use
thats sets and clears most download cache to start again
which seems to FIX most things meantioned above if you
have defined the security zones and exceptions
net.exe stop wuauserv
cd /d %windir%
rd /s softwaredistribution
REGSVR32 C:\WINDOWS\system32\wuapi.dll
REGSVR32 C:\WINDOWS\system32\wuaueng.dll
REGSVR32 C:\WINDOWS\system32\wucltui.dll
REGSVR32 C:\WINDOWS\system32\wups.dll
REGSVR32 C:\WINDOWS\system32\msxml3.dll
net.exe start wuauserv
proxycfg -u
hope that fixes your problem,
another wingate user
I spent weeks on this, theres basically 3 things you need to do
1) zone security, make sure to add windows update servers domains
in iexplorer
e.g.
If your Internet connection uses a proxy server, add the Windows Update sites to the proxy settings exceptions in Internet Settings. To do this, follow these steps:
-Open Internet Explorer.
-Click Tools, and then click Internet Options.
-Click the Connections tab, and then click LAN Settings.
-Click Advanced, and then type the following text in the Exceptions text box (all in one line):
update.microsoft.com;windowsupdate.microsoft.com;v4.windowsupdate.microsoft.com;download.windowsupdate.com
Note If you are running third-party proxy or firewall software, see your product documentation for information about how to add these sites to the exception list for those applications.
Click OK to close all Internet Options windows.
OR...
STEP 1. TRUSTED SITES vis Security TAB.
Add the Windows Update Web sites to the list of trusted sites
You may be able to resolve this issue by adding the Windows Update Web sites to the list of trusted sites. To add these Web sites to the list, follow these steps: 1. Start Microsoft Internet Explorer.
2. On the Tools menu, click Internet Options.
3. Click the Security tab.
4. Click the Trusted sites icon, and then click Sites.
5. Click to clear the Require server verification (https:) for all sites in this zone check box.
6. Add the following Web sites:
• http://Windowsupdate.microsoft.com
• http://V4.Windowsupdate.microsoft.com
• http://Download.Windowsupdate.com
• https://v4.Windowsupdate.microsoft.com
• http://V5.Windowsupdate.microsoft.com
• https://V4.Windowsupdate.microsoft.com
Note This entry uses the https prefix.
Easier to do It Appears?
http://*.windowsupdate.com
https://*.windowsupdate.com
Step2
Add the Windows Update Web sites to the list of exceptions
Add the Windows Update Web sites to the list of exceptions for proxy settings. To do this, follow these steps: 1. Start Microsoft Internet Explorer.
2. On the Tools menu, click Internet Options.
3. Click the Connections tab, and then click LAN Settings.
4. Click Advanced, and then add the following Web sites to the Exceptions list. Instead of listing each URL on a separate line, use semicolons (;) to separate the URLs as follows:
http://Windowsupdate.microsoft.com; http://V4.Windowsupdate.microsoft.com; http://Download.Windowsupdate.com; http://V5.Windowsupdate.microsoft.com
2) router MTU settings
Okay, what fixed it for me was to look at my Cisco 837 router that is hooked
to my DSL connection. On the dialer interface, I adjusted the default MTU of
1500 to 1492 as per some Cisco documentation I was reading. As soon as I made
the change, BANG, it worked. It hasn't failed again since and I have now
updated to SP2 without issue.
Microsoft, PLEASE add this to your document so that others don't have to
spend as much time as I did finding the answer.
I do not no how to make these adjustments on routers other than the Cisco,
so I am probably not much help beyond letting you know that it is something
you should look at. Your ISP may be able to help and would be a better
resource I'm sure.
3) since updater used WINHTTP you need to make sure proxycfg -u
is done to match your IE connection settings to that for winhttp !
e.g.
More Information:
Most technical people are familiar with setting up a Windows workstation to use a proxy server. There use to be only one or two settings one had to be worried about. Now, it appears, there are three. The first two are expected and should be well understood. The third setting is unexpected and does not get changed when you make adjustments to the first two.
The first setting required to set up Internet Explorer to use a proxy can be found under the Tools Menu, Internet Options menu pick. Once you have opened up the Internet Options, click on the Connections tab, then click on the LAN Settings Button. Under the Local Area Network screen, make sure the Use A Proxy check box is checked and the Address and Port fields are filled in with your Proxy Server settings.
The second type of proxy service provided by the ISA server is that provided by the ISA firewall client software (sometimes also called winsock services). The use of the firewall client is optional. The ISA firewall client services applications that ignore the IE settings for proxy services, and/or applications that contain their own proxy settings, and/or applications that do not support proxy server settings at all. If you have loaded the ISA Firewall Client, be sure you have enabled it.
The third setting apparently influences the behavior of Windows Update Control. Microsoft has Knowledgebase articles that discuss making changes but their mindset is from a standalone workstation with direct internet access and not the workstations that sit behind ISA firewalls.
Workaround / Solution:
On the XP workstation
Click on Start, and then click Run.
Type cmd in the Open box to get a DOS prompt.
Type proxycfg -u at the command prompt, and press Enter.
If you type in the proxycfg command without any options, you can see what Windows wants to do with winHTTP requests. On my machines that were having Update errors, even with Use A Proxy checked, the proxycfg command reported the following;
Current WinHTTP proxy settings under
HKEY_LOCAL_MACHINE\
SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\Connections\
WinHttpSettings :
Flags = PROXY_TYPE_DIRECT
Proxy Server = -not set-
Bypass List = -not set-
After I ran the proxycfg -u command, the proxycfg command reported:
Current WinHTTP proxy settings under
HKEY_LOCAL_MACHINE\
SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\Connections\
WinHttpSettings :
Flags = PROXY_TYPE_DIRECT | PROXY_TYPE_PROXY
Proxy Server = isa:8080
Bypass List = -not set-
For what ever reason, Windows does synchronize the proxy settings when the user makes changes to the Internet Options proxy settings. Apparently this only has significant impact on the Windows Update Control as all other Internet Enabled programs seem to work just fine even when the winHTTP proxy settings do not agree with the user entered proxy settings.
===
here is a use set of commands for a batch I use
thats sets and clears most download cache to start again
which seems to FIX most things meantioned above if you
have defined the security zones and exceptions
net.exe stop wuauserv
cd /d %windir%
rd /s softwaredistribution
REGSVR32 C:\WINDOWS\system32\wuapi.dll
REGSVR32 C:\WINDOWS\system32\wuaueng.dll
REGSVR32 C:\WINDOWS\system32\wucltui.dll
REGSVR32 C:\WINDOWS\system32\wups.dll
REGSVR32 C:\WINDOWS\system32\msxml3.dll
net.exe start wuauserv
proxycfg -u
hope that fixes your problem,
another wingate user
Re: wupdate solution
Nov 24 05 11:44 pm
Hi,
This is an interesting one.
Wingate 6.1 + KAV 2.0 unit in for faulty hardware, would not use the web based Windows Update for Win XP SP2.
What I did was to delete Win Update Client files in the %systemroot%\system32\ directory then run the update again by re opening IE and the process installed a new version of Windows installer requiring a reboot before it would even download the XP licence validation utility.
The files are:
%systemroot%\system32\wuauclt.exe
%systemroot%\system32\wuauclt1.exe
%systemroot%\system32\wupdmgr.exe
The reason I came accross this was because a notebook on the same lan also with Wingate 6.0.4 had no difficulty accessing the network gateway [Wingate 6.1] machine using the web based update system just as a comparison.
Update failure in this case is nothing to do with Wingate!
This is an interesting one.
Wingate 6.1 + KAV 2.0 unit in for faulty hardware, would not use the web based Windows Update for Win XP SP2.
What I did was to delete Win Update Client files in the %systemroot%\system32\ directory then run the update again by re opening IE and the process installed a new version of Windows installer requiring a reboot before it would even download the XP licence validation utility.
The files are:
%systemroot%\system32\wuauclt.exe
%systemroot%\system32\wuauclt1.exe
%systemroot%\system32\wupdmgr.exe
The reason I came accross this was because a notebook on the same lan also with Wingate 6.0.4 had no difficulty accessing the network gateway [Wingate 6.1] machine using the web based update system just as a comparison.
Update failure in this case is nothing to do with Wingate!
Nov 29 05 5:14 am
It works with a static connection but not with WGIC...
Nov 30 05 7:52 pm
jamesc wrote:What error message via WGIC?
Do you have any Intercepts setup; what ports?
Error: 0x80072EFD from Windows Update
Dec 08 05 6:12 am
If rubattin has the same issues as me, the error when we attempt to use Windows Update from any Windows XP or 2000 machine is 0x80072EFD. This error occurs when we click "express" after the ActiveX pops up.
When we search that error on the microsoft website, it claims that that error is a result of proxy issues and we need to open it for *.windowsupdate.microsoft.com and *.windowsupdate.com. I see no settings in Wingate and I have already tried all of jamesc's suggestions but am still unsuccessful.
Update works fine for the host machine, which is Win2K but not the WRC client machines using XP or 2K. Windows 9x/ME machines update as well. On our version of WinGate We have the proxy plug-ins and the ENS service installed, but disabled. We are just using WRC clients for everyone.
Please let me know if there is anything else to try.
Thanks,
Steve
When we search that error on the microsoft website, it claims that that error is a result of proxy issues and we need to open it for *.windowsupdate.microsoft.com and *.windowsupdate.com. I see no settings in Wingate and I have already tried all of jamesc's suggestions but am still unsuccessful.
Update works fine for the host machine, which is Win2K but not the WRC client machines using XP or 2K. Windows 9x/ME machines update as well. On our version of WinGate We have the proxy plug-ins and the ENS service installed, but disabled. We are just using WRC clients for everyone.
Please let me know if there is anything else to try.
Thanks,
Steve