Код ошибки 10052

У нас есть настольное приложение .NET 2.0, которое отправляет и получает сеть
пакетов через UDP.

Несколько пользователей сообщили о случайной ошибке сокета 10052, которая происходит
когда код вызывает socket.BeginReceiveFrom на UDP-сокете.

Что это значит?

Официальная документация MS для сокета об ошибке 10052 говорит — quote:
«WSAENETRESET (10052) Сетевое соединение отключено на reset.
был нарушен из-за активности активности, обнаруживающей отказ, в то время как
продолжалась операция. Он также может быть возвращен setsockopt, если
делается попытка установить SO_KEEPALIVE на соединение, которое уже
не удалось «.

Это просто не имеет смысла для UDP-сокета, поскольку UDP является
протокол без установления соединения.

Я знаю, что еще один код ошибки 10054 в связи с сокетами UDP
означает, что получено сообщение ICMP «Port Unreachable», и я
интересно, может ли 10052 сопоставить другое сообщение ICMP?

Я искал это в течение нескольких месяцев, читал сетевые книги и т.д., но не могу найти
что-нибудь.
Пожалуйста, помогите — что означает ошибка сокета 10052 на гнезде UDP?

Заранее спасибо

Ответ 1

См. http://msdn.microsoft.com/en-us/library/ms740120%28v=vs.85%29.aspx, в котором описывается функция recvfrom. В нем говорится о WSAENETRESET (который является ошибкой winsock 10052):

Для сокета датаграммы эта ошибка указывает на то, что время жизни истекло.

Ответ 2

Убедитесь, что значение TTL достаточно велико при отправке дейтаграмм UDP.

Если вы используете класс UdpClient.
Затем перед отправкой дейтаграммы используйте следующее:

myUdpClient.Ttl = 255;

Примечание: 255 — максимальное значение для TTL.
Существует проблема с сетью, если этого значения недостаточно.

Ответ 3

WSAE NET RESET предполагает, что это происходит из-за RESET самого сетевого интерфейса. Ваша программа сидит там, привязанная к UDP-порту, поэтому в некотором смысле она подключена, но к сетевому интерфейсу, а не к удаленному узлу.

Попробуйте запустить свою программу, доведя ее до того момента, когда будет запущен этот вызов BeginReceiveFrom, затем отключите ваш сетевой адаптер в диспетчере устройств и снова включите его. Или, используя Wi-Fi, снимите и восстановите соединение с WAP. Это может произойти, просто отсоединив кабель Ethernet к вашему компьютеру, так как последние версии Windows по умолчанию убивают все сокеты, подключенные через этот сетевой адаптер, когда это происходит.

Это объясняет редкие сообщения о проблемах с поля. Вероятно, это происходит только тогда, когда на аппаратном уровне возникает локальная сетевая ошибка.

Ошибка подключения OpenVPN к VPS серверу.

Всем привет. Столкнулся со следующей проблемой, а именно не могу подружить openvpn с VPS.

Tue May 01 19:59:10 2018 Windows version 6.2 (Windows 8 or greater) 64bit Tue May 01 19:59:10 2018 library versions: OpenSSL 1.1.0f 25 May 2017, LZO 2.10 Tue May 01 19:59:10 2018 WARNING: Your certificate is not yet valid! Tue May 01 19:59:10 2018 Outgoing Control Channel Authentication: Using 512 bit message hash ‘SHA512’ for HMAC authentication Tue May 01 19:59:10 2018 Incoming Control Channel Authentication: Using 512 bit message hash ‘SHA512’ for HMAC authentication Tue May 01 19:59:10 2018 TCP/UDP: Preserving recently used remote address: [AF_INET]148.251.3.246:1194 Tue May 01 19:59:10 2018 Socket Buffers: R=[65536->65536] S=[65536->65536] Tue May 01 19:59:10 2018 UDP link local: (not bound) Tue May 01 19:59:10 2018 UDP link remote: [AF_INET]148.251.3.246:1194 Tue May 01 20:00:10 2018 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity) Tue May 01 20:00:10 2018 TLS Error: TLS handshake failed Tue May 01 20:00:10 2018 SIGUSR1[soft,tls-error] received, process restarting

Options error: Bad protocol: ’11’. Allowed protocols with —proto option: [proto-uninitialized] [udp] [tcp-server] [tcp-client] [tcp] [udp4] [tcp4-server] [tcp4-client] [tcp4] [udp6] [tcp6-server] [tcp6-client] [tcp6] Use —help for more information.

Следовал инструкции github.com/Angristan/OpenVPN-install.

client dev tun proto udp sndbuf 0 rcvbuf 0 remote 148.251.3.246 1194 resolv-retry infinite nobind persist-key persist-tun remote-cert-tls server auth SHA512 cipher AES-256-CBC comp-lzo setenv opt block-outside-dns key-direction 1 verb 3

Источник

Ошибка сокета 10052 на сокете UDP

У нас есть настольное приложение .NET 2.0, которое отправляет и получает сеть пакетов через UDP.

Несколько пользователей сообщили о случайной ошибке сокета 10052, которая происходит когда код вызывает socket.BeginReceiveFrom на UDP-сокете.

Официальная документация MS для сокета об ошибке 10052 говорит — quote: «WSAENETRESET (10052) Сетевое соединение отключено на reset. был нарушен из-за активности активности, обнаруживающей отказ, в то время как продолжалась операция. Он также может быть возвращен setsockopt, если делается попытка установить SO_KEEPALIVE на соединение, которое уже не удалось «.

Это просто не имеет смысла для UDP-сокета, поскольку UDP является протокол без установления соединения.

Я знаю, что еще один код ошибки 10054 в связи с сокетами UDP означает, что получено сообщение ICMP «Port Unreachable», и я интересно, может ли 10052 сопоставить другое сообщение ICMP?

Я искал это в течение нескольких месяцев, читал сетевые книги и т.д., но не могу найти что-нибудь. Пожалуйста, помогите — что означает ошибка сокета 10052 на гнезде UDP?

ОТВЕТЫ

Ответ 1

См. http://msdn.microsoft.com/en-us/library/ms740120%28v=vs.85%29.aspx, в котором описывается функция recvfrom. В нем говорится о WSAENETRESET (который является ошибкой winsock 10052):

Для сокета датаграммы эта ошибка указывает на то, что время жизни истекло.

Ответ 2

Убедитесь, что значение TTL достаточно велико при отправке дейтаграмм UDP.

Если вы используете класс UdpClient. Затем перед отправкой дейтаграммы используйте следующее:

Примечание: 255 — максимальное значение для TTL. Существует проблема с сетью, если этого значения недостаточно.

Ответ 3

WSAE NET RESET предполагает, что это происходит из-за RESET самого сетевого интерфейса. Ваша программа сидит там, привязанная к UDP-порту, поэтому в некотором смысле она подключена, но к сетевому интерфейсу, а не к удаленному узлу.

Попробуйте запустить свою программу, доведя ее до того момента, когда будет запущен этот вызов BeginReceiveFrom, затем отключите ваш сетевой адаптер в диспетчере устройств и снова включите его. Или, используя Wi-Fi, снимите и восстановите соединение с WAP. Это может произойти, просто отсоединив кабель Ethernet к вашему компьютеру, так как последние версии Windows по умолчанию убивают все сокеты, подключенные через этот сетевой адаптер, когда это происходит.

Это объясняет редкие сообщения о проблемах с поля. Вероятно, это происходит только тогда, когда на аппаратном уровне возникает локальная сетевая ошибка.

Источник

System Error Codes (9000-11999)

This information is intended for developers debugging system errors. For other errors, such as issues with Windows Update, there is a list of resources on the Error codes page.

The following list describes system error codes (errors 9000 to 11999). They are returned by the GetLastError function when many functions fail. To retrieve the description text for the error in your application, use the FormatMessage function with the FORMAT_MESSAGE_FROM_SYSTEM flag.

DNS_ERROR_RCODE_FORMAT_ERROR

DNS server unable to interpret format.

DNS_ERROR_RCODE_SERVER_FAILURE

DNS server failure.

DNS_ERROR_RCODE_NAME_ERROR

DNS name does not exist.

DNS_ERROR_RCODE_NOT_IMPLEMENTED

DNS request not supported by name server.

DNS_ERROR_RCODE_REFUSED

DNS operation refused.

DNS_ERROR_RCODE_YXDOMAIN

DNS name that ought not exist, does exist.

DNS_ERROR_RCODE_YXRRSET

DNS RR set that ought not exist, does exist.

DNS_ERROR_RCODE_NXRRSET

DNS RR set that ought to exist, does not exist.

DNS_ERROR_RCODE_NOTAUTH

DNS server not authoritative for zone.

DNS_ERROR_RCODE_NOTZONE

DNS name in update or prereq is not in zone.

DNS_ERROR_RCODE_BADSIG

DNS signature failed to verify.

DNS_ERROR_RCODE_BADKEY

DNS_ERROR_RCODE_BADTIME

DNS signature validity expired.

DNS_ERROR_KEYMASTER_REQUIRED

Only the DNS server acting as the key master for the zone may perform this operation.

DNS_ERROR_NOT_ALLOWED_ON_SIGNED_ZONE

This operation is not allowed on a zone that is signed or has signing keys.

DNS_ERROR_NSEC3_INCOMPATIBLE_WITH_RSA_SHA1

NSEC3 is not compatible with the RSA-SHA-1 algorithm. Choose a different algorithm or use NSEC.

This value was also named DNS_ERROR_INVALID_NSEC3_PARAMETERS

DNS_ERROR_NOT_ENOUGH_SIGNING_KEY_DESCRIPTORS

The zone does not have enough signing keys. There must be at least one key signing key (KSK) and at least one zone signing key (ZSK).

DNS_ERROR_UNSUPPORTED_ALGORITHM

The specified algorithm is not supported.

DNS_ERROR_INVALID_KEY_SIZE

The specified key size is not supported.

DNS_ERROR_SIGNING_KEY_NOT_ACCESSIBLE

One or more of the signing keys for a zone are not accessible to the DNS server. Zone signing will not be operational until this error is resolved.

DNS_ERROR_KSP_DOES_NOT_SUPPORT_PROTECTION

The specified key storage provider does not support DPAPI++ data protection. Zone signing will not be operational until this error is resolved.

DNS_ERROR_UNEXPECTED_DATA_PROTECTION_ERROR

An unexpected DPAPI++ error was encountered. Zone signing will not be operational until this error is resolved.

DNS_ERROR_UNEXPECTED_CNG_ERROR

An unexpected crypto error was encountered. Zone signing may not be operational until this error is resolved.

DNS_ERROR_UNKNOWN_SIGNING_PARAMETER_VERSION

The DNS server encountered a signing key with an unknown version. Zone signing will not be operational until this error is resolved.

DNS_ERROR_KSP_NOT_ACCESSIBLE

The specified key service provider cannot be opened by the DNS server.

DNS_ERROR_TOO_MANY_SKDS

The DNS server cannot accept any more signing keys with the specified algorithm and KSK flag value for this zone.

DNS_ERROR_INVALID_ROLLOVER_PERIOD

The specified rollover period is invalid.

DNS_ERROR_INVALID_INITIAL_ROLLOVER_OFFSET

The specified initial rollover offset is invalid.

DNS_ERROR_ROLLOVER_IN_PROGRESS

The specified signing key is already in process of rolling over keys.

DNS_ERROR_STANDBY_KEY_NOT_PRESENT

The specified signing key does not have a standby key to revoke.

DNS_ERROR_NOT_ALLOWED_ON_ZSK

This operation is not allowed on a zone signing key (ZSK).

DNS_ERROR_NOT_ALLOWED_ON_ACTIVE_SKD

This operation is not allowed on an active signing key.

DNS_ERROR_ROLLOVER_ALREADY_QUEUED

The specified signing key is already queued for rollover.

DNS_ERROR_NOT_ALLOWED_ON_UNSIGNED_ZONE

This operation is not allowed on an unsigned zone.

DNS_ERROR_BAD_KEYMASTER

This operation could not be completed because the DNS server listed as the current key master for this zone is down or misconfigured. Resolve the problem on the current key master for this zone or use another DNS server to seize the key master role.

DNS_ERROR_INVALID_SIGNATURE_VALIDITY_PERIOD

The specified signature validity period is invalid.

DNS_ERROR_INVALID_NSEC3_ITERATION_COUNT

The specified NSEC3 iteration count is higher than allowed by the minimum key length used in the zone.

DNS_ERROR_DNSSEC_IS_DISABLED

This operation could not be completed because the DNS server has been configured with DNSSEC features disabled. Enable DNSSEC on the DNS server.

DNS_ERROR_INVALID_XML

This operation could not be completed because the XML stream received is empty or syntactically invalid.

DNS_ERROR_NO_VALID_TRUST_ANCHORS

This operation completed, but no trust anchors were added because all of the trust anchors received were either invalid, unsupported, expired, or would not become valid in less than 30 days.

DNS_ERROR_ROLLOVER_NOT_POKEABLE

The specified signing key is not waiting for parental DS update.

DNS_ERROR_NSEC3_NAME_COLLISION

Hash collision detected during NSEC3 signing. Specify a different user-provided salt, or use a randomly generated salt, and attempt to sign the zone again.

DNS_ERROR_NSEC_INCOMPATIBLE_WITH_NSEC3_RSA_SHA1

NSEC is not compatible with the NSEC3-RSA-SHA-1 algorithm. Choose a different algorithm or use NSEC3.

DNS_INFO_NO_RECORDS

No records found for given DNS query.

DNS_ERROR_BAD_PACKET

DNS_ERROR_NO_PACKET

DNS_ERROR_RCODE

DNS error, check rcode.

DNS_ERROR_UNSECURE_PACKET

Unsecured DNS packet.

DNS_REQUEST_PENDING

DNS query request is pending.

DNS_ERROR_INVALID_TYPE

Invalid DNS type.

DNS_ERROR_INVALID_IP_ADDRESS

Invalid IP address.

DNS_ERROR_INVALID_PROPERTY

DNS_ERROR_TRY_AGAIN_LATER

Try DNS operation again later.

DNS_ERROR_NOT_UNIQUE

Record for given name and type is not unique.

DNS_ERROR_NON_RFC_NAME

DNS name does not comply with RFC specifications.

DNS_STATUS_FQDN

DNS name is a fully-qualified DNS name.

DNS_STATUS_DOTTED_NAME

DNS name is dotted (multi-label).

DNS_STATUS_SINGLE_PART_NAME

DNS name is a single-part name.

DNS_ERROR_INVALID_NAME_CHAR

DNS name contains an invalid character.

DNS_ERROR_NUMERIC_NAME

DNS name is entirely numeric.

DNS_ERROR_NOT_ALLOWED_ON_ROOT_SERVER

The operation requested is not permitted on a DNS root server.

DNS_ERROR_NOT_ALLOWED_UNDER_DELEGATION

The record could not be created because this part of the DNS namespace has been delegated to another server.

DNS_ERROR_CANNOT_FIND_ROOT_HINTS

The DNS server could not find a set of root hints.

DNS_ERROR_INCONSISTENT_ROOT_HINTS

The DNS server found root hints but they were not consistent across all adapters.

DNS_ERROR_DWORD_VALUE_TOO_SMALL

The specified value is too small for this parameter.

DNS_ERROR_DWORD_VALUE_TOO_LARGE

The specified value is too large for this parameter.

DNS_ERROR_BACKGROUND_LOADING

This operation is not allowed while the DNS server is loading zones in the background. Please try again later.

DNS_ERROR_NOT_ALLOWED_ON_RODC

The operation requested is not permitted on against a DNS server running on a read-only DC.

DNS_ERROR_NOT_ALLOWED_UNDER_DNAME

No data is allowed to exist underneath a DNAME record.

DNS_ERROR_DELEGATION_REQUIRED

This operation requires credentials delegation.

DNS_ERROR_INVALID_POLICY_TABLE

Name resolution policy table has been corrupted. DNS resolution will fail until it is fixed. Contact your network administrator.

DNS_ERROR_ZONE_DOES_NOT_EXIST

DNS zone does not exist.

DNS_ERROR_NO_ZONE_INFO

DNS zone information not available.

DNS_ERROR_INVALID_ZONE_OPERATION

Invalid operation for DNS zone.

DNS_ERROR_ZONE_CONFIGURATION_ERROR

Invalid DNS zone configuration.

DNS_ERROR_ZONE_HAS_NO_SOA_RECORD

DNS zone has no start of authority (SOA) record.

DNS_ERROR_ZONE_HAS_NO_NS_RECORDS

DNS zone has no Name Server (NS) record.

DNS_ERROR_ZONE_LOCKED

DNS zone is locked.

DNS_ERROR_ZONE_CREATION_FAILED

DNS zone creation failed.

DNS_ERROR_ZONE_ALREADY_EXISTS

DNS zone already exists.

DNS_ERROR_AUTOZONE_ALREADY_EXISTS

DNS automatic zone already exists.

DNS_ERROR_INVALID_ZONE_TYPE

Invalid DNS zone type.

DNS_ERROR_SECONDARY_REQUIRES_MASTER_IP

Secondary DNS zone requires master IP address.

DNS_ERROR_ZONE_NOT_SECONDARY

DNS zone not secondary.

DNS_ERROR_NEED_SECONDARY_ADDRESSES

Need secondary IP address.

DNS_ERROR_WINS_INIT_FAILED

WINS initialization failed.

DNS_ERROR_NEED_WINS_SERVERS

Need WINS servers.

DNS_ERROR_NBSTAT_INIT_FAILED

NBTSTAT initialization call failed.

DNS_ERROR_SOA_DELETE_INVALID

Invalid delete of start of authority (SOA).

DNS_ERROR_FORWARDER_ALREADY_EXISTS

A conditional forwarding zone already exists for that name.

DNS_ERROR_ZONE_REQUIRES_MASTER_IP

This zone must be configured with one or more master DNS server IP addresses.

DNS_ERROR_ZONE_IS_SHUTDOWN

The operation cannot be performed because this zone is shut down.

DNS_ERROR_ZONE_LOCKED_FOR_SIGNING

This operation cannot be performed because the zone is currently being signed. Please try again later.

DNS_ERROR_PRIMARY_REQUIRES_DATAFILE

Primary DNS zone requires datafile.

DNS_ERROR_INVALID_DATAFILE_NAME

Invalid datafile name for DNS zone.

DNS_ERROR_DATAFILE_OPEN_FAILURE

Failed to open datafile for DNS zone.

DNS_ERROR_FILE_WRITEBACK_FAILED

Failed to write datafile for DNS zone.

DNS_ERROR_DATAFILE_PARSING

Failure while reading datafile for DNS zone.

DNS_ERROR_RECORD_DOES_NOT_EXIST

DNS record does not exist.

DNS_ERROR_RECORD_FORMAT

DNS record format error.

DNS_ERROR_NODE_CREATION_FAILED

Node creation failure in DNS.

DNS_ERROR_UNKNOWN_RECORD_TYPE

Unknown DNS record type.

DNS_ERROR_RECORD_TIMED_OUT

DNS record timed out.

DNS_ERROR_NAME_NOT_IN_ZONE

Name not in DNS zone.

DNS_ERROR_CNAME_LOOP

CNAME loop detected.

DNS_ERROR_NODE_IS_CNAME

Node is a CNAME DNS record.

DNS_ERROR_CNAME_COLLISION

A CNAME record already exists for given name.

DNS_ERROR_RECORD_ONLY_AT_ZONE_ROOT

Record only at DNS zone root.

DNS_ERROR_RECORD_ALREADY_EXISTS

DNS record already exists.

DNS_ERROR_SECONDARY_DATA

Secondary DNS zone data error.

DNS_ERROR_NO_CREATE_CACHE_DATA

Could not create DNS cache data.

DNS_ERROR_NAME_DOES_NOT_EXIST

DNS name does not exist.

DNS_WARNING_PTR_CREATE_FAILED

Could not create pointer (PTR) record.

DNS_WARNING_DOMAIN_UNDELETED

DNS domain was undeleted.

DNS_ERROR_DS_UNAVAILABLE

The directory service is unavailable.

DNS_ERROR_DS_ZONE_ALREADY_EXISTS

DNS zone already exists in the directory service.

DNS_ERROR_NO_BOOTFILE_IF_DS_ZONE

DNS server not creating or reading the boot file for the directory service integrated DNS zone.

DNS_ERROR_NODE_IS_DNAME

Node is a DNAME DNS record.

DNS_ERROR_DNAME_COLLISION

A DNAME record already exists for given name.

DNS_ERROR_ALIAS_LOOP

An alias loop has been detected with either CNAME or DNAME records.

DNS_INFO_AXFR_COMPLETE

DNS AXFR (zone transfer) complete.

DNS_ERROR_AXFR

DNS zone transfer failed.

DNS_INFO_ADDED_LOCAL_WINS

Added local WINS server.

DNS_STATUS_CONTINUE_NEEDED

Secure update call needs to continue update request.

DNS_ERROR_NO_TCPIP

TCP/IP network protocol not installed.

DNS_ERROR_NO_DNS_SERVERS

No DNS servers configured for local system.

DNS_ERROR_DP_DOES_NOT_EXIST

The specified directory partition does not exist.

DNS_ERROR_DP_ALREADY_EXISTS

The specified directory partition already exists.

DNS_ERROR_DP_NOT_ENLISTED

This DNS server is not enlisted in the specified directory partition.

DNS_ERROR_DP_ALREADY_ENLISTED

This DNS server is already enlisted in the specified directory partition.

DNS_ERROR_DP_NOT_AVAILABLE

The directory partition is not available at this time. Please wait a few minutes and try again.

DNS_ERROR_DP_FSMO_ERROR

The operation failed because the domain naming master FSMO role could not be reached. The domain controller holding the domain naming master FSMO role is down or unable to service the request or is not running Windows Server 2003 or later.

WSAEINTR

A blocking operation was interrupted by a call to WSACancelBlockingCall.

WSAEBADF

The file handle supplied is not valid.

WSAEACCES

An attempt was made to access a socket in a way forbidden by its access permissions.

WSAEFAULT

The system detected an invalid pointer address in attempting to use a pointer argument in a call.

WSAEINVAL

An invalid argument was supplied.

WSAEMFILE

Too many open sockets.

WSAEWOULDBLOCK

A non-blocking socket operation could not be completed immediately.

WSAEINPROGRESS

A blocking operation is currently executing.

WSAEALREADY

An operation was attempted on a non-blocking socket that already had an operation in progress.

WSAENOTSOCK

An operation was attempted on something that is not a socket.

WSAEDESTADDRREQ

A required address was omitted from an operation on a socket.

WSAEMSGSIZE

A message sent on a datagram socket was larger than the internal message buffer or some other network limit, or the buffer used to receive a datagram into was smaller than the datagram itself.

WSAEPROTOTYPE

A protocol was specified in the socket function call that does not support the semantics of the socket type requested.

WSAENOPROTOOPT

An unknown, invalid, or unsupported option or level was specified in a getsockopt or setsockopt call.

WSAEPROTONOSUPPORT

The requested protocol has not been configured into the system, or no implementation for it exists.

WSAESOCKTNOSUPPORT

The support for the specified socket type does not exist in this address family.

WSAEOPNOTSUPP

The attempted operation is not supported for the type of object referenced.

WSAEPFNOSUPPORT

The protocol family has not been configured into the system or no implementation for it exists.

WSAEAFNOSUPPORT

An address incompatible with the requested protocol was used.

WSAEADDRINUSE

Only one usage of each socket address (protocol/network address/port) is normally permitted.

WSAEADDRNOTAVAIL

The requested address is not valid in its context.

WSAENETDOWN

A socket operation encountered a dead network.

WSAENETUNREACH

A socket operation was attempted to an unreachable network.

WSAENETRESET

The connection has been broken due to keep-alive activity detecting a failure while the operation was in progress.

WSAECONNABORTED

An established connection was aborted by the software in your host machine.

WSAECONNRESET

An existing connection was forcibly closed by the remote host.

WSAENOBUFS

An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full.

WSAEISCONN

A connect request was made on an already connected socket.

WSAENOTCONN

A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied.

WSAESHUTDOWN

A request to send or receive data was disallowed because the socket had already been shut down in that direction with a previous shutdown call.

WSAETOOMANYREFS

Too many references to some kernel object.

WSAETIMEDOUT

A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

WSAECONNREFUSED

No connection could be made because the target machine actively refused it.

WSAELOOP

Cannot translate name.

WSAENAMETOOLONG

Name component or name was too long.

WSAEHOSTDOWN

A socket operation failed because the destination host was down.

WSAEHOSTUNREACH

A socket operation was attempted to an unreachable host.

WSAENOTEMPTY

Cannot remove a directory that is not empty.

WSAEPROCLIM

A Windows Sockets implementation may have a limit on the number of applications that may use it simultaneously.

WSAEUSERS

Ran out of quota.

WSAEDQUOT

Ran out of disk quota.

WSAESTALE

File handle reference is no longer available.

WSAEREMOTE

Item is not available locally.

WSASYSNOTREADY

WSAStartup cannot function at this time because the underlying system it uses to provide network services is currently unavailable.

WSAVERNOTSUPPORTED

The Windows Sockets version requested is not supported.

WSANOTINITIALISED

Either the application has not called WSAStartup, or WSAStartup failed.

WSAEDISCON

Returned by WSARecv or WSARecvFrom to indicate the remote party has initiated a graceful shutdown sequence.

WSAENOMORE

No more results can be returned by WSALookupServiceNext.

WSAECANCELLED

A call to WSALookupServiceEnd was made while this call was still processing. The call has been canceled.

WSAEINVALIDPROCTABLE

The procedure call table is invalid.

WSAEINVALIDPROVIDER

The requested service provider is invalid.

WSAEPROVIDERFAILEDINIT

The requested service provider could not be loaded or initialized.

WSASYSCALLFAILURE

A system call has failed.

WSASERVICE_NOT_FOUND

No such service is known. The service cannot be found in the specified name space.

WSATYPE_NOT_FOUND

The specified class was not found.

WSA_E_NO_MORE

No more results can be returned by WSALookupServiceNext.

WSA_E_CANCELLED

A call to WSALookupServiceEnd was made while this call was still processing. The call has been canceled.

WSAEREFUSED

A database query failed because it was actively refused.

WSAHOST_NOT_FOUND

No such host is known.

WSATRY_AGAIN

This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.

WSANO_RECOVERY

A non-recoverable error occurred during a database lookup.

WSANO_DATA

The requested name is valid, but no data of the requested type was found.

WSA_QOS_RECEIVERS

At least one reserve has arrived.

WSA_QOS_SENDERS

At least one path has arrived.

WSA_QOS_NO_SENDERS

There are no senders.

WSA_QOS_NO_RECEIVERS

There are no receivers.

WSA_QOS_REQUEST_CONFIRMED

Reserve has been confirmed.

WSA_QOS_ADMISSION_FAILURE

Error due to lack of resources.

WSA_QOS_POLICY_FAILURE

Rejected for administrative reasons — bad credentials.

WSA_QOS_BAD_STYLE

Unknown or conflicting style.

WSA_QOS_BAD_OBJECT

Problem with some part of the filterspec or providerspecific buffer in general.

WSA_QOS_TRAFFIC_CTRL_ERROR

Problem with some part of the flowspec.

WSA_QOS_GENERIC_ERROR

General QOS error.

WSA_QOS_ESERVICETYPE

An invalid or unrecognized service type was found in the flowspec.

WSA_QOS_EFLOWSPEC

An invalid or inconsistent flowspec was found in the QOS structure.

WSA_QOS_EPROVSPECBUF

Invalid QOS provider-specific buffer.

WSA_QOS_EFILTERSTYLE

An invalid QOS filter style was used.

WSA_QOS_EFILTERTYPE

An invalid QOS filter type was used.

WSA_QOS_EFILTERCOUNT

An incorrect number of QOS FILTERSPECs were specified in the FLOWDESCRIPTOR.

WSA_QOS_EOBJLENGTH

An object with an invalid ObjectLength field was specified in the QOS provider-specific buffer.

WSA_QOS_EFLOWCOUNT

An incorrect number of flow descriptors was specified in the QOS structure.

WSA_QOS_EUNKOWNPSOBJ

An unrecognized object was found in the QOS provider-specific buffer.

WSA_QOS_EPOLICYOBJ

An invalid policy object was found in the QOS provider-specific buffer.

WSA_QOS_EFLOWDESC

An invalid QOS flow descriptor was found in the flow descriptor list.

WSA_QOS_EPSFLOWSPEC

An invalid or inconsistent flowspec was found in the QOS provider specific buffer.

WSA_QOS_EPSFILTERSPEC

An invalid FILTERSPEC was found in the QOS provider-specific buffer.

WSA_QOS_ESDMODEOBJ

An invalid shape discard mode object was found in the QOS provider specific buffer.

WSA_QOS_ESHAPERATEOBJ

An invalid shaping rate object was found in the QOS provider-specific buffer.

WSA_QOS_RESERVED_PETYPE

A reserved policy element was found in the QOS provider-specific buffer.

WSA_SECURE_HOST_NOT_FOUND

No such host is known securely.

WSA_IPSEC_NAME_POLICY_ERROR

Name based IPSEC policy could not be added.

Источник

description	ms.assetid	title	ms.topic	ms.date
Windows Sockets (Winsock) error codes returned by the WSAGetLastError function.	50b924f3-2c88-443b-8a90-4293fe5c3048	Windows Sockets Error Codes (Winsock2.h)	reference	05/31/2018

Most Windows Sockets 2 functions do not return the specific cause of an error when the function returns. For information, see the Handling Winsock Errors topic.

The WSAGetLastError function returns the last error that occurred for the calling thread. When a particular Windows Sockets function indicates an error has occurred, this function should be called immediately to retrieve the extended error code for the failing function call. These error codes and a short text description associated with an error code are defined in the Winerror.h header file. The FormatMessage function can be used to obtain the message string for the returned error.

For information on how to handle error codes when porting socket applications to Winsock, see Error Codes — errno, h_errno and WSAGetLastError.

The following list describes the possible error codes returned by the WSAGetLastError function. Errors are listed in numerical order with the error macro name. Some error codes defined in the Winsock2.h header file are not returned from any function.

Return code/value	Description
WSA_INVALID_HANDLE 6	Specified event object handle is invalid. An application attempts to use an event object, but the specified handle is not valid.
WSA_NOT_ENOUGH_MEMORY 8	Insufficient memory available. An application used a Windows Sockets function that directly maps to a Windows function. The Windows function is indicating a lack of required memory resources.
WSA_INVALID_PARAMETER 87	One or more parameters are invalid. An application used a Windows Sockets function which directly maps to a Windows function. The Windows function is indicating a problem with one or more parameters.
WSA_OPERATION_ABORTED 995	Overlapped operation aborted. An overlapped operation was canceled due to the closure of the socket, or the execution of the SIO_FLUSH command in WSAIoctl.
WSA_IO_INCOMPLETE 996	Overlapped I/O event object not in signaled state. The application has tried to determine the status of an overlapped operation which is not yet completed. Applications that use WSAGetOverlappedResult (with the fWait flag set to FALSE) in a polling mode to determine when an overlapped operation has completed, get this error code until the operation is complete.
WSA_IO_PENDING 997	Overlapped operations will complete later. The application has initiated an overlapped operation that cannot be completed immediately. A completion indication will be given later when the operation has been completed.
WSAEINTR 10004	Interrupted function call. A blocking operation was interrupted by a call to WSACancelBlockingCall.
WSAEBADF 10009	File handle is not valid. The file handle supplied is not valid.
WSAEACCES 10013	Permission denied. An attempt was made to access a socket in a way forbidden by its access permissions. An example is using a broadcast address for sendto without broadcast permission being set using setsockopt(SO_BROADCAST). Another possible reason for the WSAEACCES error is that when the bind function is called (on Windows NT 4.0 with SP4 and later), another application, service, or kernel mode driver is bound to the same address with exclusive access. Such exclusive access is a new feature of Windows NT 4.0 with SP4 and later, and is implemented by using the SO_EXCLUSIVEADDRUSE option.
WSAEFAULT 10014	Bad address. The system detected an invalid pointer address in attempting to use a pointer argument of a call. This error occurs if an application passes an invalid pointer value, or if the length of the buffer is too small. For instance, if the length of an argument, which is a sockaddr structure, is smaller than the sizeof(sockaddr).
WSAEINVAL 10022	Invalid argument. Some invalid argument was supplied (for example, specifying an invalid level to the setsockopt function). In some instances, it also refers to the current state of the socket—for instance, calling accept on a socket that is not listening.
WSAEMFILE 10024	Too many open files. Too many open sockets. Each implementation may have a maximum number of socket handles available, either globally, per process, or per thread.
WSAEWOULDBLOCK 10035	Resource temporarily unavailable. This error is returned from operations on nonblocking sockets that cannot be completed immediately, for example recv when no data is queued to be read from the socket. It is a nonfatal error, and the operation should be retried later. It is normal for WSAEWOULDBLOCK to be reported as the result from calling connect on a nonblocking SOCK_STREAM socket, since some time must elapse for the connection to be established.
WSAEINPROGRESS 10036	Operation now in progress. A blocking operation is currently executing. Windows Sockets only allows a single blocking operation—per- task or thread—to be outstanding, and if any other function call is made (whether or not it references that or any other socket) the function fails with the WSAEINPROGRESS error.
WSAEALREADY 10037	Operation already in progress. An operation was attempted on a nonblocking socket with an operation already in progress—that is, calling connect a second time on a nonblocking socket that is already connecting, or canceling an asynchronous request (WSAAsyncGetXbyY) that has already been canceled or completed.
WSAENOTSOCK 10038	Socket operation on nonsocket. An operation was attempted on something that is not a socket. Either the socket handle parameter did not reference a valid socket, or for select, a member of an fd_set was not valid.
WSAEDESTADDRREQ 10039	Destination address required. A required address was omitted from an operation on a socket. For example, this error is returned if sendto is called with the remote address of ADDR_ANY.
WSAEMSGSIZE 10040	Message too long. A message sent on a datagram socket was larger than the internal message buffer or some other network limit, or the buffer used to receive a datagram was smaller than the datagram itself.
WSAEPROTOTYPE 10041	Protocol wrong type for socket. A protocol was specified in the socket function call that does not support the semantics of the socket type requested. For example, the ARPA Internet UDP protocol cannot be specified with a socket type of SOCK_STREAM.
WSAENOPROTOOPT 10042	Bad protocol option. An unknown, invalid or unsupported option or level was specified in a getsockopt or setsockopt call.
WSAEPROTONOSUPPORT 10043	Protocol not supported. The requested protocol has not been configured into the system, or no implementation for it exists. For example, a socket call requests a SOCK_DGRAM socket, but specifies a stream protocol.
WSAESOCKTNOSUPPORT 10044	Socket type not supported. The support for the specified socket type does not exist in this address family. For example, the optional type SOCK_RAW might be selected in a socket call, and the implementation does not support SOCK_RAW sockets at all.
WSAEOPNOTSUPP 10045	Operation not supported. The attempted operation is not supported for the type of object referenced. Usually this occurs when a socket descriptor to a socket that cannot support this operation is trying to accept a connection on a datagram socket.
WSAEPFNOSUPPORT 10046	Protocol family not supported. The protocol family has not been configured into the system or no implementation for it exists. This message has a slightly different meaning from WSAEAFNOSUPPORT. However, it is interchangeable in most cases, and all Windows Sockets functions that return one of these messages also specify WSAEAFNOSUPPORT.
WSAEAFNOSUPPORT 10047	Address family not supported by protocol family. An address incompatible with the requested protocol was used. All sockets are created with an associated address family (that is, AF_INET for Internet Protocols) and a generic protocol type (that is, SOCK_STREAM). This error is returned if an incorrect protocol is explicitly requested in the socket call, or if an address of the wrong family is used for a socket, for example, in sendto.
WSAEADDRINUSE 10048	Address already in use. Typically, only one usage of each socket address (protocol/IP address/port) is permitted. This error occurs if an application attempts to bind a socket to an IP address/port that has already been used for an existing socket, or a socket that was not closed properly, or one that is still in the process of closing. For server applications that need to bind multiple sockets to the same port number, consider using setsockopt (SO_REUSEADDR). Client applications usually need not call bind at all—connect chooses an unused port automatically. When bind is called with a wildcard address (involving ADDR_ANY), a WSAEADDRINUSE error could be delayed until the specific address is committed. This could happen with a call to another function later, including connect, listen, WSAConnect, or WSAJoinLeaf.
WSAEADDRNOTAVAIL 10049	Cannot assign requested address. The requested address is not valid in its context. This normally results from an attempt to bind to an address that is not valid for the local computer. This can also result from connect, sendto, WSAConnect, WSAJoinLeaf, or WSASendTo when the remote address or port is not valid for a remote computer (for example, address or port 0).
WSAENETDOWN 10050	Network is down. A socket operation encountered a dead network. This could indicate a serious failure of the network system (that is, the protocol stack that the Windows Sockets DLL runs over), the network interface, or the local network itself.
WSAENETUNREACH 10051	Network is unreachable. A socket operation was attempted to an unreachable network. This usually means the local software knows no route to reach the remote host.
WSAENETRESET 10052	Network dropped connection on reset. The connection has been broken due to keep-alive activity detecting a failure while the operation was in progress. It can also be returned by setsockopt if an attempt is made to set SO_KEEPALIVE on a connection that has already failed.
WSAECONNABORTED 10053	Software caused connection abort. An established connection was aborted by the software in your host computer, possibly due to a data transmission time-out or protocol error.
WSAECONNRESET 10054	Connection reset by peer. An existing connection was forcibly closed by the remote host. This normally results if the peer application on the remote host is suddenly stopped, the host is rebooted, the host or remote network interface is disabled, or the remote host uses a hard close (see setsockopt for more information on the SO_LINGER option on the remote socket). This error may also result if a connection was broken due to keep-alive activity detecting a failure while one or more operations are in progress. Operations that were in progress fail with WSAENETRESET. Subsequent operations fail with WSAECONNRESET.
WSAENOBUFS 10055	No buffer space available. An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full.
WSAEISCONN 10056	Socket is already connected. A connect request was made on an already-connected socket. Some implementations also return this error if sendto is called on a connected SOCK_DGRAM socket (for SOCK_STREAM sockets, the to parameter in sendto is ignored) although other implementations treat this as a legal occurrence.
WSAENOTCONN 10057	Socket is not connected. A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using sendto) no address was supplied. Any other type of operation might also return this error—for example, setsockopt setting SO_KEEPALIVE if the connection has been reset.
WSAESHUTDOWN 10058	Cannot send after socket shutdown. A request to send or receive data was disallowed because the socket had already been shut down in that direction with a previous shutdown call. By calling shutdown a partial close of a socket is requested, which is a signal that sending or receiving, or both have been discontinued.
WSAETOOMANYREFS 10059	Too many references. Too many references to some kernel object.
WSAETIMEDOUT 10060	Connection timed out. A connection attempt failed because the connected party did not properly respond after a period of time, or the established connection failed because the connected host has failed to respond.
WSAECONNREFUSED 10061	Connection refused. No connection could be made because the target computer actively refused it. This usually results from trying to connect to a service that is inactive on the foreign host—that is, one with no server application running.
WSAELOOP 10062	Cannot translate name. Cannot translate a name.
WSAENAMETOOLONG 10063	Name too long. A name component or a name was too long.
WSAEHOSTDOWN 10064	Host is down. A socket operation failed because the destination host is down. A socket operation encountered a dead host. Networking activity on the local host has not been initiated. These conditions are more likely to be indicated by the error WSAETIMEDOUT.
WSAEHOSTUNREACH 10065	No route to host. A socket operation was attempted to an unreachable host. See WSAENETUNREACH.
WSAENOTEMPTY 10066	Directory not empty. Cannot remove a directory that is not empty.
WSAEPROCLIM 10067	Too many processes. A Windows Sockets implementation may have a limit on the number of applications that can use it simultaneously. WSAStartup may fail with this error if the limit has been reached.
WSAEUSERS 10068	User quota exceeded. Ran out of user quota.
WSAEDQUOT 10069	Disk quota exceeded. Ran out of disk quota.
WSAESTALE 10070	Stale file handle reference. The file handle reference is no longer available.
WSAEREMOTE 10071	Item is remote. The item is not available locally.
WSASYSNOTREADY 10091	Network subsystem is unavailable. This error is returned by WSAStartup if the Windows Sockets implementation cannot function at this time because the underlying system it uses to provide network services is currently unavailable. Users should check: That the appropriate Windows Sockets DLL file is in the current path. That they are not trying to use more than one Windows Sockets implementation simultaneously. If there is more than one Winsock DLL on your system, be sure the first one in the path is appropriate for the network subsystem currently loaded. The Windows Sockets implementation documentation to be sure all necessary components are currently installed and configured correctly.
WSAVERNOTSUPPORTED 10092	Winsock.dll version out of range. The current Windows Sockets implementation does not support the Windows Sockets specification version requested by the application. Check that no old Windows Sockets DLL files are being accessed.
WSANOTINITIALISED 10093	Successful WSAStartup not yet performed. Either the application has not called WSAStartup or WSAStartup failed. The application may be accessing a socket that the current active task does not own (that is, trying to share a socket between tasks), or WSACleanup has been called too many times.
WSAEDISCON 10101	Graceful shutdown in progress. Returned by WSARecv and WSARecvFrom to indicate that the remote party has initiated a graceful shutdown sequence.
WSAENOMORE 10102	No more results. No more results can be returned by the WSALookupServiceNext function.
WSAECANCELLED 10103	Call has been canceled. A call to the WSALookupServiceEnd function was made while this call was still processing. The call has been canceled.
WSAEINVALIDPROCTABLE 10104	Procedure call table is invalid. The service provider procedure call table is invalid. A service provider returned a bogus procedure table to Ws2_32.dll. This is usually caused by one or more of the function pointers being NULL.
WSAEINVALIDPROVIDER 10105	Service provider is invalid. The requested service provider is invalid. This error is returned by the WSCGetProviderInfo and WSCGetProviderInfo32 functions if the protocol entry specified could not be found. This error is also returned if the service provider returned a version number other than 2.0.
WSAEPROVIDERFAILEDINIT 10106	Service provider failed to initialize. The requested service provider could not be loaded or initialized. This error is returned if either a service provider’s DLL could not be loaded (LoadLibrary failed) or the provider’s WSPStartup or NSPStartup function failed.
WSASYSCALLFAILURE 10107	System call failure. A system call that should never fail has failed. This is a generic error code, returned under various conditions. Returned when a system call that should never fail does fail. For example, if a call to WaitForMultipleEvents fails or one of the registry functions fails trying to manipulate the protocol/namespace catalogs. Returned when a provider does not return SUCCESS and does not provide an extended error code. Can indicate a service provider implementation error.
WSASERVICE_NOT_FOUND 10108	Service not found. No such service is known. The service cannot be found in the specified name space.
WSATYPE_NOT_FOUND 10109	Class type not found. The specified class was not found.
WSA_E_NO_MORE 10110	No more results. No more results can be returned by the WSALookupServiceNext function.
WSA_E_CANCELLED 10111	Call was canceled. A call to the WSALookupServiceEnd function was made while this call was still processing. The call has been canceled.
WSAEREFUSED 10112	Database query was refused. A database query failed because it was actively refused.
WSAHOST_NOT_FOUND 11001	Host not found. No such host is known. The name is not an official host name or alias, or it cannot be found in the database(s) being queried. This error may also be returned for protocol and service queries, and means that the specified name could not be found in the relevant database.
WSATRY_AGAIN 11002	Nonauthoritative host not found. This is usually a temporary error during host name resolution and means that the local server did not receive a response from an authoritative server. A retry at some time later may be successful.
WSANO_RECOVERY 11003	This is a nonrecoverable error. This indicates that some sort of nonrecoverable error occurred during a database lookup. This may be because the database files (for example, BSD-compatible HOSTS, SERVICES, or PROTOCOLS files) could not be found, or a DNS request was returned by the server with a severe error.
WSANO_DATA 11004	Valid name, no data record of requested type. The requested name is valid and was found in the database, but it does not have the correct associated data being resolved for. The usual example for this is a host name-to-address translation attempt (using gethostbyname or WSAAsyncGetHostByName) which uses the DNS (Domain Name Server). An MX record is returned but no A record—indicating the host itself exists, but is not directly reachable.
WSA_QOS_RECEIVERS 11005	QoS receivers. At least one QoS reserve has arrived.
WSA_QOS_SENDERS 11006	QoS senders. At least one QoS send path has arrived.
WSA_QOS_NO_SENDERS 11007	No QoS senders. There are no QoS senders.
WSA_QOS_NO_RECEIVERS 11008	QoS no receivers. There are no QoS receivers.
WSA_QOS_REQUEST_CONFIRMED 11009	QoS request confirmed. The QoS reserve request has been confirmed.
WSA_QOS_ADMISSION_FAILURE 11010	QoS admission error. A QoS error occurred due to lack of resources.
WSA_QOS_POLICY_FAILURE 11011	QoS policy failure. The QoS request was rejected because the policy system couldn’t allocate the requested resource within the existing policy.
WSA_QOS_BAD_STYLE 11012	QoS bad style. An unknown or conflicting QoS style was encountered.
WSA_QOS_BAD_OBJECT 11013	QoS bad object. A problem was encountered with some part of the filterspec or the provider-specific buffer in general.
WSA_QOS_TRAFFIC_CTRL_ERROR 11014	QoS traffic control error. An error with the underlying traffic control (TC) API as the generic QoS request was converted for local enforcement by the TC API. This could be due to an out of memory error or to an internal QoS provider error.
WSA_QOS_GENERIC_ERROR 11015	QoS generic error. A general QoS error.
WSA_QOS_ESERVICETYPE 11016	QoS service type error. An invalid or unrecognized service type was found in the QoS flowspec.
WSA_QOS_EFLOWSPEC 11017	QoS flowspec error. An invalid or inconsistent flowspec was found in the QOS structure.
WSA_QOS_EPROVSPECBUF 11018	Invalid QoS provider buffer. An invalid QoS provider-specific buffer.
WSA_QOS_EFILTERSTYLE 11019	Invalid QoS filter style. An invalid QoS filter style was used.
WSA_QOS_EFILTERTYPE 11020	Invalid QoS filter type. An invalid QoS filter type was used.
WSA_QOS_EFILTERCOUNT 11021	Incorrect QoS filter count. An incorrect number of QoS FILTERSPECs were specified in the FLOWDESCRIPTOR.
WSA_QOS_EOBJLENGTH 11022	Invalid QoS object length. An object with an invalid ObjectLength field was specified in the QoS provider-specific buffer.
WSA_QOS_EFLOWCOUNT 11023	Incorrect QoS flow count. An incorrect number of flow descriptors was specified in the QoS structure.
WSA_QOS_EUNKOWNPSOBJ 11024	Unrecognized QoS object. An unrecognized object was found in the QoS provider-specific buffer.
WSA_QOS_EPOLICYOBJ 11025	Invalid QoS policy object. An invalid policy object was found in the QoS provider-specific buffer.
WSA_QOS_EFLOWDESC 11026	Invalid QoS flow descriptor. An invalid QoS flow descriptor was found in the flow descriptor list.
WSA_QOS_EPSFLOWSPEC 11027	Invalid QoS provider-specific flowspec. An invalid or inconsistent flowspec was found in the QoS provider-specific buffer.
WSA_QOS_EPSFILTERSPEC 11028	Invalid QoS provider-specific filterspec. An invalid FILTERSPEC was found in the QoS provider-specific buffer.
WSA_QOS_ESDMODEOBJ 11029	Invalid QoS shape discard mode object. An invalid shape discard mode object was found in the QoS provider-specific buffer.
WSA_QOS_ESHAPERATEOBJ 11030	Invalid QoS shaping rate object. An invalid shaping rate object was found in the QoS provider-specific buffer.
WSA_QOS_RESERVED_PETYPE 11031	Reserved policy QoS element type. A reserved policy element was found in the QoS provider-specific buffer.

Requirements

Requirement	Value
Header	Winsock2.h; Winerror.h

See also

Error Codes — errno, h_errno and WSAGetLastError

Handling Winsock Errors

FormatMessage

WSAGetLastError