ws2

ws2_32.dll是Windows Sockets应用程序接口， 用于支持Internet和网络应用程序。

基本信息

外文名称

ws2_32.dll

文件版本

5.1.2600.5512(XP)

目录

1文件简介

2其他用途

3支持的API函数

4英文描述

折叠编辑本段文件简介

Windows和需要执行TCP/IP网络通信的应用程序会调用动态链接库ws2_32.dll。

如果ws2_32.dll不可用,你的计算机连接网络的操作会不稳定(即使不连接到外部网络)。

折叠DLL文件描述

ws2_32.dll是Windows Sockets应用程序接口，用于支持Internet和网络应用程序。

折叠常见错误

File Not Found, Missing File, Exception Errors

程序运行时会自动调用ws2_32.dll文件，ws2_32.dll是个动态链接库文件位于系统文件夹中。Windows在查找动态链接库文件时会先在应用程序当前目录搜索，如果没有找到然后才会搜索Windows所在目录;如果还是没有会搜索system32和system目录。

折叠编辑本段其他用途

折叠阻止使用某个软件

只要在其安装目录下新建一个文件名为ws2_32.dll的文件，这样系统就会以文件出错误而禁止运行(可以新建一个内容为空的文件夹，然后改名为ws2_32.dll)

本方法适用基于NT系统的WinXP,Win2000,Win2003

比较险恶~~用的时候再删除该文件就是。

想在自己电脑上禁止朋友玩游戏，又不能让人看出来是故意的(伤害感情),这招就够绝的~~

比如:

把其放在QQ的安装文件夹下面，就ok了，不过要记得自己用的时候把它删了。

[原因]程序运行时会自动调用ws2_32.dll文件，ws2_32.dll是个动态链接库文件，位于系统文件夹中，Windows在查找动态链接库文件时，会先在应用程序当前目录搜索，如果没有找到然后才会搜索Windows所在目录，如果还是没有会搜索system32和system目录。新建的 ws2_32.dll文件不具备真正地ws2_32.dll文件所具有的功能，所以程序就无法运行了。

===================================================================

ws2_32.dll是Windows Sockets应用程序接口

一些病毒利用此原理在杀毒软件目录中建立伪"ws2_32.dll"的文件或文件夹,在杀毒软件看来这是程序运行需要的文件而调用，这个所谓的"文件"又不具备系统"ws2_32.dll"文件的功能，所以杀毒软件等就无法运行了而提示:应用程序正常初始化(0xc00000ba)失败!

伪"ws2_32.dll"文件夹其实重命名之后程序就可以运行的,但是有个没用的又无法删除的文件夹看着也不舒服，因此这个内部含有非法文件名的文件夹就用下面方法删除!

①解压附件里面的文件(修复"显示所有文件和文件夹".reg)，双击它修复显示所有文件和文件夹。然后在资源管理器上点击工具>>选项 >>查看，将隐藏受保护的操作系系统(推荐)的勾去掉，勾选显示所有文件和文件夹之后一路的确认，好了现在隐藏的文件全部显示出来。(临时解决办法可以将ws2_32.dll文件夹改个名称，要彻底删除请往下看。)

②到杀毒软件的安装目录下找到以伪"ws2_32.dll"的文件夹(一般隐藏的文件夹颜色略白)。

③解压附件里面的"将畸形文件托到我上面.bat"到任意目录，用鼠标左键点击将要删除的ws2_32.dll文件或者文件夹(一般这些目录下的隐藏文件都需要删除)按住不松然后拖放到该文件图标上(就像把文件拖到文件夹里的操作一样,此工具双击是不能运行的)，OK一个CMD窗口闪烁之后伪 "ws2_32.dll"文件夹就被删除了。你需要的软件就可以启动了!此批处理文件也可以删除其他文件名怪怪

折叠文件夹删除不掉

ws2_32.dll文件夹删除不掉 只是因为里面有个1.(畸形路径)文件夹

怎样创建一个1.文件夹

也许各位坛友会问 怎么样我就不能在资源管理器中创建1.文件夹的啊(^_^ 别急 先进入命令提示行)

开始 →运行 输入 cmd

C:\test>md 1..\

回车以后是不是在资源管理器里面可以看到一个1.文件夹。

删除方法:使用rd(rmdir)扩展命令

假设ws2_32.dll在C盘的test文件夹中

可以直接退到test目录:C:\test>rd /s /q c:\test\ws2_32.dll

也可以:C:\test>rmdir /s /q c:\test\ws2_32.dll

rd 命令详解:

删除一个目录。

RD [/S] [/Q] [drive:]path

/S 除目录本身外，还将删除指定目录下的所有子目录和

文件。用于删除目录树。

/Q 安静模式，带 /S 删除目录树时不要求确认

折叠编辑本段支持的API函数

accept

bind

closesocket

connect

freeaddrinfo

getaddrinfo

gethostbyaddr

gethostbyname

gethostname

getnameinfo

getpeername

getprotobyname

getprotobynumber

getservbyname

getservbyport

getsockname

getsockopt

htonl

htons

inet_addr

inet_ntoa

ioctlsocket

listen

ntohl

ntohs

recv

recvfrom

select

send

sendto

setsockopt

shutdown

socket

FreeAddrInfoW

GetAddrInfoW

GetNameInfoW

WEP

WPUCompleteOverlappedRequest

WSAAccept

WSAAddressToStringA

WSAAddressToStringW

WSAAsyncGetHostByAddr

WSAAsyncGetHostByName

WSAAsyncGetProtoByName

WSAAsyncGetProtoByNumber

WSAAsyncGetServByName

WSAAsyncGetServByPort

WSAAsyncSelect

WSACancelAsyncRequest

WSACancelBlockingCall

WSACleanup

WSACloseEvent

WSAConnect

WSACreateEvent

WSADuplicateSocketA

WSADuplicateSocketW

WSAEnumNameSpaceProvidersA

WSAEnumNameSpaceProvidersW

WSAEnumNetworkEvents

WSAEnumProtocolsA

WSAEnumProtocolsW

WSAEventSelect

WSAGetLastError

WSAGetOverlappedResult

WSAGetQOSByName

WSAGetServiceClassInfoA

WSAGetServiceClassInfoW

WSAGetServiceClassNameByClassIdA

WSAGetServiceClassNameByClassIdW

WSAHtonl

WSAHtons

WSAInstallServiceClassA

WSAInstallServiceClassW

WSAIoctl

WSAIsBlocking

WSAJoinLeaf

WSALookupServiceBeginA

WSALookupServiceBeginW

WSALookupServiceEnd

WSALookupServiceNextA

WSALookupServiceNextW

WSANSPIoctl

WSANtohl

WSANtohs

WSAProviderConfigChange

WSARecv

WSARecvDisconnect

WSARecvFrom

WSARemoveServiceClass

WSAResetEvent

WSASend

WSASendDisconnect

WSASendTo

WSASetBlockingHook

WSASetEvent

WSASetLastError

WSASetServiceA

WSASetServiceW

WSASocketA

WSASocketW

WSAStartup

WSAStringToAddressA

WSAStringToAddressW

WSAUnhookBlockingHook

WSAWaitForMultipleEvents

WSApSetPostRoutine

WSCDeinstallProvider

WSCEnableNSProvider

WSCEnumProtocols

WSCGetProviderPath

WSCInstallNameSpace

WSCInstallProvider

WSCUnInstallNameSpace

WSCUpdateProvider

WSCWriteNameSpaceOrder

WSCWriteProviderOrder

__WSAFDIsSet

折叠编辑本段英文描述

Windows Process Description:

A file that contains the Windows Sockets API used by most Internet and network applications to handle network connections is known as the ws2_32.dll file. This program is referred to as the Windows socket 2.0 DLL for 32-bit Windows platforms. It is used by applications when performing TCP/IP network communication.

The ws2_32.dll module uses Winsock internally to handle network connections. However, the program can be used directly in applications to control the creation and management of socket connections. WinSock 2 is made up of several separate documents that are available in 3 different formats: MS Word for Windows, Text and Postscript.

The ws2_32.dll file defines and documents the use of the API in conjunction with the Internet Protocol Suite. Specifically, all of its implementations support both stream (TCP) and datagram (UDP) sockets. It allows the creation of applications that are network protocol independent. The application can transparently select a protocol based on its service needs. It can also adapt to differences in network names and addresses using the mechanisms.

The Winsock 2 defines a network programming interface for Microsoft Windows, which is based on the "socket" paradigm popularized in the Berkeley Software Distribution (BSD). It includes familiar Berkeley socket style routines and a set of Windows-specific extensions designed to allow the programmer to take advantage of the message-driven nature of Windows.

The ws2_32.dll module adds support for protocol-independent name resolution, asynchronous operations with event-based notifications and completion routines, layered protocol implementations, multicasting, and quality of service. It supports the multiple protocols, including ATM, IPX/SPX and DECNet. It also allowed sockets to be optionally shared between processes, incoming connection requests to be conditionally accepted, and certain operations to be performed on socket groups rather than individual sockets.

Winsock 2 does not only allow coexistence of multiple protocol stacks, but it can also transparently select a protocol based on its service needs. Using the mechanisms, the process can adapt to differences in network names and addresses. It also provides socket sharing wherein two or more processes can share a socket handle.