UNSOLVED

metal01a

updated

23 years ago

M

metal01a

1 Rookie

•

5 Posts

0

66731

March 5th, 2004 15:00

windows socket error 10048 on api bind

I just started receiving this error today.  I found a troubleshooting recommendation to look for shellapi.exe in the registry but it was not there.  Any other ideas for stopping this problem.

 

Tks,

Dave

  • osprey4

    6 Operator

    •

    34230 Posts

    3437

    0

    Posted March 5th, 2004 17:00

    Unless you are running a server on your computer, you should not be seeing this message. I would suspect some sort of trojan. Are your virus signatures up to date?
  • metal01a

    1 Rookie

    •

    5 Posts

    3437

    0

    Posted March 5th, 2004 21:00

    Not sure my system would be considered a server set up.  My brother and I are networked with Linksys Router and Cable Modem with my PC the "main" one.

     

    How do I check on virus signatures?

     

    Appreciate the help.

  • osprey4

    6 Operator

    •

    34230 Posts

    3437

    0

    Posted March 5th, 2004 23:00

    Your anti-virus software should have a way to check and update to the most recent signatures. Post back with the AV software you're running and I'll check for you.

  • metal01a

    1 Rookie

    •

    5 Posts

    3437

    0

    Posted March 6th, 2004 00:00

    Norton Anit-Virus 2001.  I just finished running a virus scan and it did not find anything.  I also ran Spybot but that did not help either.
  • osprey4

    6 Operator

    •

    34230 Posts

    3437

    0

    Posted March 6th, 2004 17:00

    Ok, the next thing to do is rebuild your Winsock. Go here, download the fix and run it:

    http://www.bu.edu/pcsc/internetaccess/winsock2fix.html

  • metal01a

    1 Rookie

    •

    5 Posts

    3437

    0

    Posted March 6th, 2004 18:00

    I just finished running an application called THE CLEANER that I found on another post dealing with this same message.  It seems to have worked.  It identified 8 trojans and deleted them.  The error seems to have stopped.  WOOHOO! LOL.  If it starts again I will do the Winsock fix.

    Thanks much, I really appreciate your input on this.

  • osprey4

    6 Operator

    •

    34230 Posts

    3437

    0

    Posted March 6th, 2004 19:00

    That's cool!!

    Do you have a link for that program you used? It might benefit others.

  • metal01a

    1 Rookie

    •

    5 Posts

    3437

    0

    Posted March 6th, 2004 22:00

    I will look for it and post it here.
  • 3437

    0

    Posted March 16th, 2004 06:00

    HI there,

    this is a winsock error and we need to do a winsock fix. it is very easy but a little long if done for the first time. all we need to do is to delete the winsock registry keys mentioned in the article

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

    after deleting the keys, uncheck dial up networking from the add/remove programs (dont restart the computer now!) and remove everything EXCEPT the network card from the network -> configuration tab. now restart the computer and recheck the dial up networking in the add/remove programs . everything will come automatically in the network stack so we dont need to do anything there. restart the computer and the internet should work fine.

    Still if the internet doesn't works then type "SFC" in the run box and select extract one file from the installatiion disk and then we will have to extract all the winsock files mentioned in the step 9 of the above article.

    Restart the computer when asked .. the computer should work fine after that.

    PS: if norton system works is installed then please disable it.