I had the same wireless issue - no problem when direct connected but wouldn't
scan on wireless. I tried all the other suggestions that came up except the
MTU cahnge. Running wireless in DCHP mode didn't give the option to change
MTU on the router, but manually setting MTU to 1452 according to this
procedure from KB 900926 instantly fixed the problem PC. (Many other options
related to manually changing MTU can be found by searching: MTU XP
registry.)
Method 3: Set the MTU size for the network interface manually
If you set the MTU size for a network interface manually, this setting
overrides the default MTU for the network interface. The MTU size is the
maximum packet size in bytes that the transport will transmit over the
underlying network.
This method affects packets sent to all destinations and may significantly
affect the performance, depending on the MTU size that you set.
To set the MTU size for the network interface, follow these steps:1. Click
Start, click Run, type regedit, and then click OK.
2. Locate the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Tcpip\Parameters\Interfaces\<ID for network interface>
3. On the Edit menu, point to New, and then click DWORD Value.
4. Type MTU, and then press ENTER.
5. On the Edit menu, click Modify.
6. In the Value data box, type the value of the MTU size, and then click OK.
7. Quit Registry Editor, and then restart the computer.
"brummer" wrote:
>
> Hi
>
> I had the same problem.
> For DNS server the ip adres of my router was filled in, i changed this to
> the ip adres of my ISP this solved the problem for me.
>
> br
> Hans Brummel
> "Oscar Lee (MS)" wrote:
>
> > Hi
> >
> > Can you send %windir%\WindowsUpdate.log (one word) from the client machine
> > that is encountering this problem?
> >
> > Thanks,
> >
> > --
> > Oscar Lee (MSFT)
> > Microsoft Corporation
> > WSUS
> >
> > (Communication using the newsgroup is preferred. Thanks!)
> >
> > =====================
> > This posting is provided "AS IS" with no warranties, and confers no rights.
> > =====================
> > "Mog" <(removeqs)> wrote in message
> > news:54AA2F01-FD92-40E4-8163-...
> > > I forgot to mention, I have tried the remedies suggested by the Windows
> > > Update troubleshooter, none of which had any effect. I also neglected to
> > > mention that I am using a fully patched Windows XP SP2.
> > >
> > > Thanks for the suggestion but no joy.
> > >
> > > "MowGreen [MVP]" wrote:
> > >
> > > > From the Windows Update v.6 Troubleshooter:
> > > >
> > > > " Problem description
> > > > This error may occur when the client PC tries to resolve a URL for the
> > > > Update site and is unable to find the correct IP address.
> > > >
> > > > Resolutions
> > >
> > > <snip>
> > >
> > > >
> > > > MowGreen [MVP 2003-2005]
> > > > ===============
> > > > *-343-* FDNY
> > > > Never Forgotten
> > > > ===============
> > > >
> > > >
> > > > Mog wrote:
> > > >
> > > > > For the past few days I have been getting 0x80072ee7 errors whenever I
> > > > > attempt to do a scan on windows update. I have discovered today that
> > if I
> > > > > connect to my ADSL router (Netgear DG834) using an ethernet cable
> > instead of
> > > > > through wireless it seems to work. Both connections are protected
> > using the
> > > > > Windows firewall and no other sites have a problem. It was working
> > until a
> > > > > few days ago over wireless and I have not changed any settings on my
> > router
> > > > > or my computer. Does anyone have any suggestions that I can try. I
> > rarely
> > > > > connect by ethernet to my router and this will probably mean that I
> > automatic
> > > > > updates will not work either.
> > > >
> >
> >
> >