Koozali.org: home of the SME Server

Bizzare Windows Update problem with SME 5.6

paulmancan2

Bizzare Windows Update problem with SME 5.6
« on: November 07, 2004, 10:15:59 AM »
I cannot figure out what in the world is going on here. Windows update fails when I am behind the e-smith box but if I connect directly it is fine.

What is most bizzare is that the WU log has the following entry in it and a LONG time ago I was indeed using e-smith with DYNDNS and that hostname. I have changed the hostname to no avail.

SendRequest failed with hr = 80072efd. Proxy List used: <proxy.mytestbox.mine.nu:3128>

Thanks for any help!

Offline Reinhold

  • *
  • 517
  • +0/-0
    • http://127.0.0.1
Bizzare Windows Update problem with SME 5.6
« Reply #1 on: November 07, 2004, 12:23:15 PM »
paul,

There is little, better NO, relation between any dyndns settings and WU...
You seem to have a problem in IE proxy settings.
Try to use Internet Explorer directly when you need to access the Windows Update site. One solution is to bypass the desktop icon to get to Windows Update and instead just launch Internet Explorer and type in the address manually (http://windowsupdate.microsoft.com). If the problem still occurs when you try to access the site in this fashion, then you’ll need to update the WUPDMGR.EXE file.
You do not describe which Windows you are using but in any case make sure you have "no proxy" in your Internet Settings (Note: SME internal proxy works transparently)

Regards
Reinhold
............

paulmancan2

Bizzare Windows Update problem with SME 5.6
« Reply #2 on: November 07, 2004, 08:02:01 PM »
My friend thank you for your reply. I know that this sounds like it may not have anything to do with SME, but yes it does!

I booted from an LRP floppy and WU works fine!

a) The problem is occuring on any machine I put behind e-smith, including one that is a fresh XP installation!

b) I had a similar problem with a workstation behind another SME box a few months ago. It was not using DYNDNS. The WU log referred to a proxy that was a PREVIOUS hostname of that SME box! I do not recall how this was resolved.

c) I am not using proxy/squid

d) I have cleared XP proxy cache, it was empty anyway. It has never been set to use a proxy.

So this is absolutely BIZZARRE!

Where is MS getting proxy.myoldhostname.y.z from? The SME box MUST be sending this info somehow!?

I am going to install 6.0.1 and see what happens, BUT as per the next thread I am about to post, I can't seem to install it using a boot floppy!

Thanks!

Offline Appesteijn

  • ***
  • 62
  • +0/-0
Bizzare Windows Update problem with SME 5.6
« Reply #3 on: November 10, 2004, 11:13:57 AM »
My fresh installed WinXP also didn't want to use WU until i gave it (my WinXP box) a fixed IP adres (so no DHCP) and also filled in the DNS-servers from my ISP. Maybe it will help your in case.
............

Offline monrovia

  • 4
  • +0/-0
Bizzare Windows Update problem with SME 5.6
« Reply #4 on: November 11, 2004, 07:37:51 AM »
Quote from: "Appesteijn"
My fresh installed WinXP also didn't want to use WU until i gave it (my WinXP box) a fixed IP adres (so no DHCP) and also filled in the DNS-servers from my ISP. Maybe it will help your in case.


Ditto. Manually entering IP worked for me too. (same subnet, same gateway, same dns server - just manually entered)

Previously winupdate failed with Error 0x80072EFD for an XP machine behind 5.6 SME gateway/server. Problem started around the time MS updated windowsupate site which coincided with release of SP2 I think.

Something to do with dhcpd.conf settings?

Offline NickCritten

  • *
  • 245
  • +0/-0
Bizzare Windows Update problem with SME 5.6
« Reply #5 on: November 11, 2004, 04:35:10 PM »
The windowsupdate v5 is insane methinks.

I had LOADS of problems updating an SP2 machine on one site, but then I did 4 or five from my home network, which is behind an SME6.0, and they were fine.

Try setting your IE proxy to the IP of the SME, can't remember what port though... Try 3128, 80 & 8080
...
Nick

"No good deed goes unpunished." :-x...

Nitrolic

Bizzare Windows Update problem with SME 5.6
« Reply #6 on: January 21, 2005, 09:13:20 PM »
Has anyone figured out how to fix this problem?

I'm having the exact same problem.  I have SME 5.6, and Windows Update does NOT want to work, however it works fine at home, or directly connected to the internet.

I tried setting my IE proxy to the IP of the SME, on the ports 3128, 80 & 8080, and neither of them work, they just seem to fail at any attempt to connect to any web site.  Is there a certain port I should try?

KelvinLee

Bizzare Windows Update problem with SME 5.6
« Reply #7 on: January 22, 2005, 04:42:05 AM »
I have not confirmed this yet, but I believe it's a problem with Bind (DNS server inside SME 5.6). There has been confirmed problems with bind not resolving certain domain names.

As a simple test, if I pinged windowsupdate.microsoft.com from SME 5.6, I get a different IP address than when I pinged it from behind a hardware router.

A workaround to this problem could be to set the Master DNS of SME to your ISP's DNS server through SME configuration screens.

Kelvin

KelvinLee

Bizzare Windows Update problem with SME 5.6
« Reply #8 on: January 22, 2005, 04:50:10 AM »
Sorry, just came across another posting on this issue :-

http://forums.contribs.org/index.php?topic=25293.0

It could be a transparent proxy issue. At some sites, I have to disable transparent proxy on SME or the workstations cannot reliably access certain websites, externally hosted CMS systems, etc. Highly repeatable :- enable transparent proxy, the problems come back, disable transparent proxy, problems go away.

Try disabling transparent proxy and see if you can run Windows update now.

Kelvin

Nitrolic

Bizzare Windows Update problem with SME 5.6
« Reply #9 on: January 22, 2005, 05:48:48 AM »
Not sure what you mean by "transparent proxy"

How would I go about disabling this?

KelvinLee

Bizzare Windows Update problem with SME 5.6
« Reply #10 on: January 23, 2005, 07:17:01 AM »
SME 5.6 has transparent proxy on by default, ie. any web requests through an SME 5.6 gateway goes through Squid. If everything works as they should, this is a good thing as any requests to a page that is already in the Squid cache does not need to be fetched from the 'net again. However, there are times when this actually interferes with the way some things work.

A search of the forums will yield more information about transparent proxy. To disable it, have a look at this thread :-

http://forums.contribs.org/index.php?topic=16756.msg64882#msg64882

Kelvin