Invalid wsock32.dll

Printable View

October 21st, 2003, 05:22 PM
ganzie

Invalid wsock32.dll

Hi All,
Got a wsock32.dll error message appearing everytime i startup my XP Pro SP1 sys(upgraded from 98). Since then i've been unable to have internet access. Msg says wsock32.dll is invalid or old. this all happened after i uninstalled NOD32 by eset, so i figuring this is fixable. i tried replacing wsock32.dll with fresh copy from working machine but still got error. then i installed norton antivirus and did a scan with definitions dated 8/29/2002. i saw that there are some virus/worm/trojan which effect this file after infection but there all seemed to be before my virus definitions, btw norton came up clean, no infections. I then tried resetting TCP/IP using these instructions http://support.microsoft.com/default...&Product=winxp but got the error msg "Intialization Function InithelperDLL in IPMONTR.DLL failed to start with error code 10107". I saw this thread http://forums.windrivers.com/cgi-bin...ht=wsock32.dll to use LSP-fix but not sure if it would work on XP Pro. Another thing is there a way to upodate virus defintions without internet access for Norton SW 2003? This problem i need to fix without having to reinstall, reinstall as last last resort. all help is greatly apreciated.
October 22nd, 2003, 04:53 AM
NooNoo

Part of your problem is the fact that you upgraded, when you upgrade you suddenly find out what problems the old os had you weren't aware of... sometimes its not fixable.

However, yes lspfix does work on xp - sometimes. If you have newdotnet or similar, most times its a format job I am afraid.

You can try running sfc /scannow from start run - you will need your xp cd in the driver.
October 22nd, 2003, 08:54 AM
TripleRLtd

It sounds like you didn't prepare properly for the upgrade.
That being said, we first need to determine if you do indeed have a virus like happy or mtx which can lead to these errors.
You WILL need internet access to manually download the updated virus definitions from www.symantec.com. (friends/neighbor/local friendly computer guy?).
Then let us know.https://forums.windrivers.com/
October 22nd, 2003, 09:36 AM
ganzie

Hi All,
I don't believe this to be an upgrade problem. I upgraded this pc to XP from 98 months ago, and had no problems after the upgrade. It has been working without any problems till the other day. This wsock32.dll problem started after[B] i uninstalled NOD32 Antivirus from Eset. I refuse to accept that a format c: is my only solution. I will try the sfc /scannow idea that NoNo suggested, i'm unable to get an IP address on this pc so looks like i'll be unable to update virus definitions. I have a app "WinSockXPFix.exe" which i'll give a try in an effort to "reset" my winsock & friends files.
Now if my worst fears are true, is a re-installation of XP over itself possible?? If so, what special steps or precautions are advised? All help is greatly apprecaited. Thx Noonoo and TripleR.
October 22nd, 2003, 09:43 AM
NooNoo

Yes reinstalling xp over itself is called an "in-place" install. XP has the option to do this. Boot from the cd and let the setup run all the way to the screen where it asks you which partition you wish to install it on - there will be a repair option there as it will have detected the previous install.

Your other option would be to reinstall NOD32 and see whether that returns functionality - if it does, there must be a trick to uninstalling that safely.

Oh and by the way

Quote:

Got a wsock32.dll error message appearing everytime i startup my XP Pro SP1 sys(upgraded from 98). Since then i've been unable to have internet access

Your first two sentences governed my reaction to your problem. Please try to be a little clearer next time - it saves a lot of misunderstandings.
October 22nd, 2003, 09:44 AM
TripleRLtd

Ah, it sounded like you just upgraded b4 problem surfaced.
So, now, try NooNoo SFC option first.
You can, if needed do a reinstall/repair XP installation if necessary:
No format required!!!
http://support.microsoft.com/default.aspx?scid=kb;[LN];315341
October 23rd, 2003, 04:51 PM
ganzie

Hi All,
Ok, i've fixed the problem. WinsockXPFix.exe did the trick. Ran it, backed up my registry, applied fix, rebooted and then once again I was working again with no error messages. Thx NooNoo and TripleRLtd for your comments.
October 23rd, 2003, 10:12 PM
TripleRLtd

Quote:

Originally Posted by ganzie

Hi All,
Ok, i've fixed the problem. WinsockXPFix.exe did the trick. Ran it, backed up my registry, applied fix, rebooted and then once again I was working again with no error messages. Thx NooNoo and TripleRLtd for your comments.

https://forums.windrivers.com/https://forums.windrivers.com/
NooNoo is good, isn't she???
October 24th, 2003, 08:20 AM
NooNoo

Quote:

Originally Posted by TripleRLtd

https://forums.windrivers.com/https://forums.windrivers.com/
NooNoo is good, isn't she???

Triple R - I didn't suggest he use winsockfix.exe - so yes, he fixed it himself.
October 24th, 2003, 06:03 PM
TripleRLtd

Quote:

Originally Posted by NooNoo

Triple R - I didn't suggest he use winsockfix.exe - so yes, he fixed it himself.

I had noticed, I just couldn't find the toungue in cheek smilie.https://forums.windrivers.com/
He thanked us but fixed it himself.
Good for him.