WARNING !!! MS&spyware killed my TCP/IP !!!

[Marco]

Hello ...

I figured out how MS wants to get rid of their spyware
problem, symply kill TCP/IP and you can't get on the
internet anymore.

Unless some one comes up with a solution, I will have to
use a clean install to get it fixed. A windows repair
didn't work.

- Marco.

 

[cliff johnson]

You are not alone!!! At least now I know what happened to
my system and you are correct.... System Restore no longer
works. I too am hoping for a quick resolution to this
issue.
Cliff

 

[Rob]

Or you could try just reinstalling the TCP/IP stack?

I am curious however if it killed your stack when did it
happen? Was it when you installed it? or did it find
some Spyware and you clicked uninstall? Did you create a
restore point? Oh and if it killed your internet
connection how did you get here?

 

[Jon G]

You can't lay blame with a beta. Obviously something like
will be fixed and it's actually a good thing that it
happened to you now. Consider it you doing everyone else
a service If you can't get on the web anymore it's
likely that you were infected with spyware that attached
itself to the winsock that broke when it was removed. If
you have SP2 try:

Start - Run - netsh int ip reset resetlog.txt (resets
TCP/IP stack)

and

Start - Run - netsh winsock reset (resets winsock)

A Windows repair install is not likely to fix the
problems you mention but rather carry them over.

-Jon

 

[Marco]

IPX Netbios is still working, I can connect to another
computer that I am using to write this message with

Just before Christmas, I was infected with an explorer
popup shittyware. After I came back (1 week), Ad-Aware
(updated) detected 24 spywares, but didn't detect or
clean them all because the popups kept coming back.

Yesterday I tried MSAS, and it detected 64!!!

After clean-up, it asked for a reboot, and after the
reboot ... no internet connection.

"ipconfig /all" indicates that there is no TCP/IP, and no
DHCP local address. The computer I am using right now has
DHCP configurations.

I checked if the DHCP service was running, and that's on.

I am not a technical expert, what is a stack?

- Marco.

 

[Tycoon]

I had that problem as well. However, all i had to do was
shutdown IE and reopen it again and it was fine. I
restarted my computer just to be sure and it was fine. I
am running XP Pro SP2.

 

[Guest]

IPX and TCP/IP are two separate and different protocols

The TCP/IP stack: http://en.wikipedia.org/wiki/TCP/IP

-Jon

 

[Marco]

It's a windows 2000 computer that I am using for years,
so I really don't want a clean install. If I need a clean
install, I will throw it out and buy a Mac.

I reinstalled TCP/IP, but still the same problem.

I tried "ipconfig /renew" but is says:
"operation was attempted on something that's not a socket"

So, I guess there is a socket problem, because
"ipconfig /renew" works fine on my other (XP) computer.

But what is a socket?

- Marco.

 

[seagal]

don't say stupidities!!!

 

[Jon G]

The problem you have, as i suspected is winsock corruption which is obvious
from the message you've shown us. I am not entirely sure how to fix this up
on a 2k machine. I'm not sure if similar steps to a manual XP fix can be
applied here. In the case of XP you could delete winsock and winsock2 keys
from registry and then reinstall TCP/IP. Anyone?

-Jon

 

[Guest]

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

 

[Robert Belon]

Marco,

Have a look at the following article on the Microsoft
Support site.

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

The document is titled: "You receive an - An operation was
attempted on something that is not a socket" error message
when you try to connect to a network" this article should
be useful for more than a handful of novice beta users. Be
carefull when using any registry editing tool, use at your
own risk.

It cannot be overemphasized ... BETA at your own risk.
Alpha's are often times very, very brutal but Beta's can
be just as brutal. The testing process is necessary, but
you do not have to participate.

My personal standard for any beta testing is real simple.
Image the drive(s) prior to installation, restoring is
clean, and fast. I restore in 15 minutes what it took
months to perfect. My $$$ investment is $279.00 but my
time is worth far more; what precious little I can spare.

I sure hope that helps you out buddy. And not to worry,
even the most anal people have or will make the very same
mistake you made. I hope you have gotten more from this
message than just a quick fix, knowledge is where the real
power lies.

Bob

 

[Marco.]

This is for Windows 2000 ...

* Uninstall TCP/IP.
* Make a Registry backup, just in case.

In Registry Editor kill these groups:
-
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsoc
k
-
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsoc
k2

* Reboot
* Reinstall TCP/IP.

Is there anyway for MSAS to check if any of the
shittywares changed the TCP/IP/Socket settings in the
registry (or whatever you call it)?

- Marco.

 

[Jon G]

Thanks Robert,

That was the fix i mentioned and as shown it does apply to 2k as well. Good
job.

-Jon

 

[Jim Byrd]

Hi Marco and Jon (for a WinK2 source) - FYI from one of my "standard" posts:


#########IMPORTANT#########
Before you try to remove spyware using any of the programs below, download
both a copy of LSPFIX here:

http://www.cexx.org/lspfix.htm

AND a copy of Winsockfix for W95, W98, and ME
http://www.tacktech.com/pub/winsockfix/WinsockFix.zip
Directions here: http://www.tacktech.com/display.cfm?ttid=257

or here for Win2k/XP http://files.webattack.com/localdl834/WinsockxpFix.exe
Info here: http://www.spychecker.com/program/winsockxpfix.html
Directions here: http://www.iup.edu/house/resnet/winfix.shtm

The process of removing certain malware may kill your internet connection.
If this should occur, these programs, LSPFIX and WINSOCKFIX, will enable you
to regain your connection.

NOTE: It is reported that in XP SP2, the Run command netsh winsock reset
will fix this problem without the need for these programs. (You can also
try this if you're on XP SP1. There has also been one, as yet unconfirmed,
report that this also works there.) Also, one MS technician suggested the
following sequence:

netsh int reset all
ipconfig /flushdns

See also: http://windowsxp.mvps.org/winsock.htm for additional XPSP2
info/approaches using the netsh command.
#########IMPORTANT#########


--
Please respond in the same thread.
Regards, Jim Byrd, MS-MVP



In

 

[Guest]

I have followed your instuctions and still can not conect
to the internet. Can you suggest anything else I can try!?

 

[Jon G]

What OS are you running?

-Jon

I have followed your instuctions and still can not conect
to the internet. Can you suggest anything else I can try!?

 

[cliff johnson]

Jon, it seems that you are one busy guy!!!
I have followed your instuctions and still can not conect
to the internet. Can you suggest anything else I can try!?

 

[Jon G]

What OS are you running?

-Jon

Jon, it seems that you are one busy guy!!!
I have followed your instuctions and still can not conect
to the internet. Can you suggest anything else I can try!?

 

[Mark L. Ferguson]

This is for Windows 2000 ...

* Uninstall TCP/IP.
* Make a Registry backup, just in case.

In Registry Editor kill these groups:
-
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsoc
k
-
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsoc
k2

* Reboot
* Reinstall TCP/IP.

<end quote>