Update Failed - Can't find an internet connection !!

[CH@OS]

Everyhting runs and works fine except when I try to
update. I get "Update Failed - Can't find an internet
connection" error. IE & Outlook Express both open and
work fine, I even tried the: (run "netsh winsock reset").

No Good, any suggestions.

Thanks
CH@OS

 

[Engel]

Hello CH@OS

For the Internet connectivity issue,(for XP) please go to
a command prompt and type:
netsh winsock reset
and hit enter.
You can read about the causes of this issue and more about
the fix here:
http://support.microsoft.com/kb/892350


Ensure that Internet Explorer or Outlook Express is
working online, open IE,from the File menu, ensure
that "Work Offline is not checked.

Good luck

Engel

 

[avanabs]

I've posted this one twice already, as have others, but
microsoft doesn't seem to have addressed it. It's the one
and only program out of more than a dozen that I
routinely use with auto-update that fails to work. I've
tried dozens of things, including disabling firewall,
turning off IE security, turning off other Anti-Spyware
packages, etc.

Unfortunately, it makes an otherwise pretty interesting
product useless. I've un-installed and goen back to
SpywareBegone and Spy Sweeper, both of which update just
fine and seem to find everything that Microsoft finds.

 

[Bill Sanderson]

This error is nearly opaque to me.

About all that I can see about it is that any problem with connectivity to
the update site will apparently result in this error. So--see if you can
tracert spynet.com.

There are some hosts files that block spynet.com

The same error apparently happens due to actual host/server issues. Other
users have found that this error is transient, and can go away on its own
with no change they are aware of on their systems.

It can be caused by IE or OE being set to work offline. I haven't messed
with proxy settings in IE in regards to this error, but I'd bet that they
could also cause it.

--

 

[plun]

Bill Sanderson explained :

spynet.com

Strange problem ?!?

- Double firewall ? , common problem for SP2 users

- Behind a corporate proxy or ISP proxy ?

- MSAS blocked within firewall ?

- Tracert do not work within ms network.
traceroute to spynet.com (216.32.240.29), 30 hops max, 40 byte packets
1 213-133-98-129.clients.your-server.de (213.133.98.129) 0.348 ms
0.494 ms 0.637 ms
2 et-2-2.RS86001.RZ3.hetzner.de (213.133.96.193) 2.197 ms 2.322 ms
2.414 ms
3 gi-upl.lambdanet.hetzner.de (213.239.240.195) 2.591 ms 2.710 ms
0.638 ms
4 nbg.de.lambdanet.net (213.133.96.234) 3.704 ms 3.819 ms 3.909
ms
5 FRA-2-eth100.de.lambdanet.net (217.71.105.13) 5.584 ms 5.621 ms
6.181 ms
6 PAR-4-pos200.fr.lambdanet.net (82.197.144.22) 16.325 ms 16.284
ms 16.520 ms
7 LON-2-pos100.uk.lambdanet.net (82.197.136.33) 21.598 ms 21.508
ms 21.750 ms
8 ASH-1-pos000.us.lambdanet.net (81.209.156.30) 94.747 ms 94.887
ms 94.811 ms
9 MSN.us.lambdanet.net (81.209.156.130) 94.833 ms 94.819 ms
95.189 ms
10 gig1-2.core2.ash1.ntwk.msn.net (207.46.34.49) 95.416 ms 95.536
ms 95.378 ms
11 pos3-1.tuk-76cb-1a.ntwk.msn.net (207.46.34.53) 162.646 ms
162.773 ms 162.524 ms
12 ten2-3.tuk-76c-1b.ntwk.msn.net (207.46.35.77) 160.105 ms 160.440
ms 160.747 ms
13 * * *

 

[Bill Sanderson]

My tracert looked just like yours (well, making adjustments...) meaning that
it quit at hop 13. That's enough to tell that it is working, though, I
think--and a more useful result than a ping.

--

 

[plun]

on 2005-06-17, Bill Sanderson supposed :

Okidok, then we have these ?

 

[Bill Sanderson]

Gotta be more than that, and I'm not convinced about the double-firewall
theory. I guess that makes some sense--having the Windows firewall running
may mask the executable name asking to talk out, so that the third-party
firewall doesn't recognize what app it is--but why would Microsoft
Antispyware be the first app to show up this issue?

--

 

[plun]

Bill Sanderson formulated the question :

Gotta be more than that, and I'm not convinced about the double-firewall
theory. I guess that makes some sense--having the Windows firewall running
may mask the executable name asking to talk out, so that the third-party
firewall doesn't recognize what app it is--but why would Microsoft
Antispyware be the first app to show up this issue?

And this app is strange with 3 connections when updating.

GIANTAntiSpywareMain.exe:3992 TCP www.spynet.com:80 ESTABLISHED
GIANTAntiSpywareMain.exe:3992 UDP *:*
GIANTAntiSpywareMain.exe:3992 TCP 207.46.236.25:80 ESTABLISHED

Compare it to my TrendMicro:
pcclient.exe:3512 TCP a195-54-99-225.deploy.akamaitechnologies.com:80 ESTABLISHED


Challenge... but MS have not adressed anything about this so maybe
they have the answer ?

 

[Bill Sanderson]

Bill Sanderson formulated the question :

And this app is strange with 3 connections when updating.

GIANTAntiSpywareMain.exe:3992 TCP www.spynet.com:80 ESTABLISHED
GIANTAntiSpywareMain.exe:3992 UDP *:*
GIANTAntiSpywareMain.exe:3992 TCP 207.46.236.25:80 ESTABLISHED

That is wierd. I can see the UDP and the TCP, but why the third one?

I've been assuming that most details about the UI of the product are not
worth worrying about because they will change with beta2. What I don't know
is what other behavioral issues are worth making loud noises about--I'm
clear that they know about the issues with being able to define proxies,
including those that require authentication. What I don't know is what else
is likely to be redone radically--I hope the scheduling mechanisms, but I
also hope the update mechanism.

 

[Bullwinkle. J. Moose]

I had the same problem. I removed the program completely and then
reinstalled it. The auto update or manual update works fine.

 

[Steve Dodson [MSFT]]

I want to dig into this if it is not resolved by the next release. Let me
know if this still happens when we release the next build.

--
-steve

Steve Dodson [MSFT]
MCSE, CISSP
PSS Security
http://blogs.technet.com/stevedod
--

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.