Winsock will not initialize

[bos200]

Hi

How do you tell if ethier winsock.dll or
wsock32.dll are corrupt.

 

[gbiello]

The easy way is to replace them with copies from a known good machine and see if your problem goes away.

The hard way is to compare them byte by byte to a known good copy.

If you give us more details on the problem (assuming there is one), we may be able to help more.

-gbiello

 

[gbiello]

...You could also remove the IP stack. Reboot. Reinstall the IP stack. Reboot.

 

[bos200]

Hi Gbiello:

thank you for your answers,we have check your first option
and found all as well. On your second option if you mean unload the whole protocol stack,well we did that to and
did a re-install, nothing happens. we allso found that
WS2_32.DLL does the actual start of the initialization, and
even though I have admin rights it would not let me copy
the module to thier respectif folders(dirs). I even tried
romote console and the reply was access denied. Maybe their
is some software out thier that lets you check the credability
of each DLL lib(module). bos200

 

[gbiello]

> is some software out thier that lets you check the credability of each DLL lib(module)?

Not that I am aware of.

Can you give more info? Operating system? Event logs errors? Exact error message and how/when it appears.

There is some info on this problem in the M$ knowledgebase.

-gbiello