The error codes listed in Table A.1 are used throughout the stack. Success
is zero, definite errors are negative numbers, and indeterminate
conditions are positive numbers. These codes are provided in
You can modify them to wrap around an existing system.
If you define errors with non-negative values, the stack does not work.
These error codes are typically returned by functions that return an integer. See the function specifications (Chapter 3 TCP/IP API Functions and Chapter 6 Low-overhead UDP Functions) for information on specific functions.
|Error type||Error code
(defined in ||Return value||Description|
|Nonfatal/success:||1||ARP is holding the packet while awaiting a response from the target host|
|2||The packet was of no interest (callback reply only)|
|Programming errors:||–10||Bad parameter|
|–11||Illogical sequence of events|
|–21||Ran out of free packets|
|–22||Ran out of queueable resources OR full queue|
|–23||TCP layer error|
|–24||Operation did not complete in reasonable time|
|–25||Expected file was missing.|
|–26||File I/O error|
|Net errors:||–30||Send to net failed at a lower layer|
|–31||No ARP reply for a given host|
|–32||Bad header at the upper layer (for callbacks)|
|–33||Cannot find a reasonable next IP hop|
|–34||Cannot find a reasonable interface|
|–35||Detected a hardware failure|