My Vesion of the TunaBoy57 Problem: MS Download 3

[bcastner]

I have a site with a small network of mixed Win clients, mostly XP.

I have no issues with Windows Updates, hyperlinks, IE or other applications except for this:

I cannot download from the MS Windows Download site. The logs show that the session times out. The Windows Update site works perfectly well, I have no problems on any other secured site I can think of.

But from clients I have tested I cannot initiate a download from the MS Download site.

I manually set the MTU of both client workstations I tested to 1492, and confirmed the Linksys router was set to 1492 (WRT54G, latest firmware) for DSL. I Tweak Tested both through http:\\

http://www.broadbandreports.com

This is not a firewall issue. Nor a virus, trojan, or HOSTS issue.

Does anyone have a clue what is different about the MS Download site from every other secured and non-secure site I can think of to download something from? The session starts, no activity occurs, and then ends. The logs show that the session timed-out.

I called MS and confirmed both XP licenses are valid. All are current in terms of service packs and hotfixes. One is a wired client, the other wireless. I have no other problems at the site. Unfortunately I cannot test a Win98 client as that one is nearly always in use, but I have quickly tried other XP clients with the same result.

?

 

[linney]

What is the url for the "MS Windows Download site" you refer to?

 

[bcastner]

http://www.microsoft.com/downloads/

 

[linney]

Most of my information on this problem was written by you! I wouldn't presume or dare to repost it. Can't help you much, sorry.

I checked the url and there is no problem downloading at this end.

I didn't see mention of Temporary Internet Files in your post. Perhaps a clean out of them might help. Before you do, you mentioned logfile, was this an error log from within the Temporary Internet Files folder as per this suggestion "you can get a bit more information as to why you can't download a file by going into your temporary internet files and searching for any files that start with
?CodeDownloadErrorLog (sort by name and they will all be right at the top b/c of the ? in the begining) drag some of these files to the desktop and open them. there will be a "code download error" at the top which may give a clue as to why the files are not downloading"?

Also the ordinary Temp files should be deleted. Now we come to the "flying by the seat of his pants stuff". Delete the Cookies, History and Temporary Internet Files folders incase there is any corruption involved with Index.dat files. Windows will replace them all after you have deleted and rebooted.

Any help here, probably not as most seems related to downloading updates or secure site connection, but you never know.?

http://groups.google.com/groups?sou...=UTF-8&q="download+hang"+site+hang+windows+xp

329802 - BUG: Proxy Authentication Through IAuthenticate May Fail on Secure URL

http://support.microsoft.com/default.aspx?scid=kb;EN-US;329802

Troubleshoot Situations Where You Cannot Connect to Secure Web Sites by Using Internet Explorer in Windows XP

http://support.microsoft.com/default.aspx?scid=kb;en-us;813444

This site also has some good thoughts on the issue:

http://www.mvps.org/inetexplorer/answers2.htm#secure_sites

I couldn't resist this last idea.

Try System Restore to get back to when everything worked.

 

[jonlog]

Just for information...

I have XP Pro installed on two computers and I have no problems accessing MS Windows update site and downloading any updates. It all works as expected and is very fast with my DSL setup.

Since the Windows XP update site works as it is suppose to then the only conclusion is the problem is at your end.

 

[bcastner]

jonlog,

Thank you for your response. I believe you absolutely it is a problem on my end, but am baffled as to what exactly is the problem on my end.

Perhaps the logs will help:

From the %windir%\Windows Update

2003-07-10 23:57:00 03:57:00 Success IUENGINE Determining machine configuration
2003-07-10 23:57:01 03:57:01 Success IUENGINE Querying software update catalog from

https://v4.windowsupdate.microsoft.com/consumerdrivers/getmanifest.asp

2003-07-10 23:57:28 03:57:28 Success IUENGINE Querying software update catalog from

https://v4.windowsupdate.microsoft.com/getmanifest.asp

2003-07-10 23:57:33 03:57:33 Success IUENGINE Asynchronous Download started
2003-07-10 23:57:33 03:57:33 Success IUENGINE Download destination root folder is: D:\WUTemp
2003-07-10 23:57:54 03:57:54 Error IUENGINE Library download error and timed out (21000 ms). Will not retry. (Error 0x80072EE2)
2003-07-10 23:57:54 03:57:54 Error IUENGINE Downloading file

http://download.windowsupdate.com/m...D3ADFECA5D27B538BFB5243DBF39A9034F2A5019.exe,

skipping remaining files for this Item (Error 0x80072EE2)
2003-07-10 23:58:16 03:58:16 Error IUENGINE Library download error and timed out (21282 ms). Will not retry. (Error 0x80072EE2)


And the iuhist.xml:

temID=&quot;winxp.windowsxp.ver_platform_win32_nt.5.1.x86.en.ver_nt_workstation..2600...com_microsoft.windows error reporting recommended update windows xp.&quot; name=&quot;Windows Error Reporting Recommended Update Windows XP&quot;><publisherName>com_microsoft</publisherName><language>en</language></identity><description hidden=&quot;0&quot;><descriptionText><title>Windows Error Reporting: Recommended Update (Windows XP)</title><eula href=&quot;/msdownload/update/v3/static/eula/en/eula.htm&quot;/><details href=&quot;

http://go.microsoft.com/fwlink/?LinkId=16979&quot;/></descriptionText></description><platform

name=&quot;ver_platform_win32_nt&quot;><processorArchitecture>x86</processorArchitecture><version major=&quot;5&quot; minor=&quot;1&quot; build=&quot;2600&quot; servicePackMajor=&quot;&quot; servicePackMinor=&quot;&quot;/></platform><downloadStatus value=&quot;FAILED&quot; errorCode=&quot;-2147012894&quot;/><downloadPath>D:\WUTemp\com_microsoft.Windows Error Reporting Recommended Update Windows XP</downloadPath><client>IU_Site</client></itemStatus><itemStatus xmlns=&quot;&quot; timestamp=&quot;2003-07-10T23:58:16&quot;>

I suspect there might be a protocol that was introduced I am not passing through my router to satisfy the download server. The router in this case is a Linksys WRT54G and I have problems both with wired and wireless clients. It has the newest firmware. The clients have the newest driver set. The pure Windows Update side of things seems to work fine. I just had notification of updates available, and they downloaded and installed without error on several machines on this site.

It is just the voluntary Windows Download site, and the voluntary Windows Catalogue site where one can pick a specific driver. Then I get the timeout errors.

I had an odd situation that seems similar recently where all of the sudden clients could not send mail through the Verizon mail account, but had no problem receiving mail. This turned out to be an issue where Verizon had adopted a protocol change require IGMP registration by the client at service level 2. My packet trace shows no odd protocol demands from the Microsoft site, just that the session times out.

Please jonlog give your advice as to how to correct this issue on my side.

Best.
Bill

 

[Freestone]

Look for section Initialization Error 0x80072EE2 at this link:

http://v4.windowsupdate.microsoft.com/troubleshoot/

Perhaps it's related to your problem.

 

[Freestone]

And this link has a few ideas, again perhaps related:

http://groups.google.com/groups?hl=...1c2c363%247d34b4e0%248df82ecf%40TK2MSFTNGXA02

 

[bcastner]

Freestone,

Thank you.

A variation on your Google link to add these sites to the Trusted Zone under IE seems to work:

http://windowsupdate.microsoft.com

http://V4.windowsupdate.microsoft.com

http://download.windowsupdate.com

I was prompted in each case to enter the sites as https instad of http sites, so I did so.

It appears to work now without issue.

I will try this on other clients and report back. In addition to adding these to the IE Secure Zone I also disabled and then re-enabled the HTTP 1.1 settings. Then did a clean re-boot of the machine.

The logs are now clear. I will experiment a bit more, but the difference in Windows Update site was immediate and very clear that the update would succeed where previously it would fail.

I want to test this on a few other clients, so give me a little bit of time. On the client that it the hpps:// registration for the sites I also had removed the Windows hotfix for WPA, and would feel happier if this was not an issue or when the wired clients respond the same way.

A very definite star to you friend.

This wireless notebook is very happily downloading from all the MS sites now. Please note the change from the Link site, you need to register the MS sites as hpps:\\, and I did an un-tick apply, re-tick apply for HTTP1 under that section of Internet Options, Advanced.

Will post further when I try this on a few differnt clients, but you earned a star.

 

[bcastner]

I will edit the solution in a little while when I feel slightly more comfortable with it as a general hint. And the links above should be three links, not two, for the Microsoft sites. My apologies. I want to test how generic a solution this is, and possibly trace it to a recent Hotfix.

Bill

 

[bcastner]

jonlog essentially said in an earlier post that it was a problem on my end.

freestone provided some links that led to me making specific https entries for the problematic site, and this did work.

But jonlog's point still bothered me. jonlog's point was this is not an OS or site issue, but something is wacked on my site end.

So I did a dead cold restart of the Linksys WRT54G router, (held the reset button until the red diag lite came on, all the lites flashed, red diag lite whent off, and then on. Unplugged the router for a full 30 Mississippi count, and plugged it back in. Restored all router settings and applied them.

Now all the clients work with the problematic site. I could make one client work with the suggestions from Freestone, but it seemed tedious to do so for all the clients. Somehow the clean hard reboot of the router solved whatever protocol issue I was facing.

Best to all for helping, with special note to jonlog, Linney, and especially Freestone.

Lesson: it does not matter if the router works, it matters if it works perfectly.

Lesson: hard reset the router after a firmware change. In fact, hard reset it more than once. Then put in your settings.

Lesson: If you a problem that IE settings can help, you likely have other problems.

Bill

 

[battmain]

Lesson: it does not matter if the router works, it matters if it works perfectly.

Lesson: hard reset the router after a firmware change. In fact, hard reset it more than once. Then put in your settings.

Lesson: If you a problem that IE settings can help, you likely have other problems.

Interesting findings as I've also run into this. Rebooted the router and same results. Made no sense and did it as a last resort but in my case, the firmware wasn't changed. Wonder if the problem occurs because the router doesn't pass the packets properly. Anyone have any ideas?