Remove ads!
Based on GVME Community!
Your rating: N/A
Total votes: 0

You cannot rating yet!
You can rate anything - when you add rating to a submission your vote determines its success or failure.

To vote on this submission
register or login

You cannot add to Favorites!
You must register or login

You cannot say thanks!
You must register or login

More informations about this submission!
Development Informations
No details were entered

Scores and popularity
Views: 24
Downloads: 0
Feedback: 0

How to optimize my ping?

Added by: Diablo
Category: Counter-Strike > Client
Tags: optimize ping lag
Author's Readme/Notes

- completely revised 02/16/2003 - Edit on 08/31/2003 for the ping-tuning guide regarding XP users -

This penguin serves as an aid for every connection type and also takes into account the problem provider AOL.

Of course, the DSL protocols are of no interest here, for example, for modem, ISDN, satellite. But there are enough tips for every area.

Principle for dialing in to dial-up networks - Ping Guide

Before blaming God and the world, first check with your provider, ask him or, for example, www.onlinekosten.de whether there are any difficulties on the part of your provider. Otherwise, all the guides in the world will be of no use to you!

Configuration eg under W9X:

Properties of the connection:

correct modem driver inside?
Only use PPP drivers for ISDN.

Everything out except TCP / IP and under TCP / IP settings the IP header compression out. Of course, this also applies to DSL connections over the dial-up network, whereby for pure DSL connections please also remove the TCP / IP! Why will be explained later.

Modem / ISDN
ping still too high? Check out new drivers! If that doesn't help then take a fast provider that is designed for performance.
Modem users in particular, whether analog or ISDN, should always be on the lookout for new firmware at their manufacturer.

Here www.onlinekosten.de has always been a good advisor.

Optimization tips for DSL

For specific tuning also for the modem, Nava's unbeatable DSL tuning guide should be looked at, as long as it is fluent in English.

Never take the Telekom or AOL driver! Take independent PPPoE drivers. I recommend the Schlabbach driver for T-DSL users. Check out the installation instructions for the respective OS there !!!

The speed manager, which is available free of charge from Telekom, is one of the few really useful tools from the magenta giant! It not only optimizes the MTU value but also monitors the connection.

You can get the speed manager for T-DSL here .


yes it is correct the TCP / IP protocol is only on
1. Network card LAN (^^ not if the DSL card is alone!)
2. Dial-up entry

The TCP / IP protocol should not be linked to the network type for DSL (network properties -> eg 3COM 920 TX properties -> Bindings tab).
This is not necessary, but especially with Win98SE and W2K leads to dropouts, which are mostly not noticeable during downloads (bad case).
Under Windows XP and 2000 in particular, this also results in a boot delay that is sometimes even minutes long, since these services first have to be initialized.

The PPP protocol from the dial-up network is already running on the DSL network type where the T-DSL modem is attached.
Pure TCP / IP packets are not to be found there. The trap is lurking with activated DHCP speaks get address automatically.
Then the PC constantly tries to get an address assignment via TCP / IP from the DSL modem, but it doesn't get it. That can and only wants TCP / IP via PPP. This then involves various problems, as already explained above, for example.

Trap with W9x & W2k:

With the Schlabbach driver , it is especially important with W9X to increase the MSTCP values ​​and stacks in the registry.

1. Go to Start - Run
2. Enter regedit + Enter
3. Change to the folder HKEY_LOCAL_MACHINE -System - CurrentControlSet - Services - VxD - MSTCP
4. Create a new entry here with the name MaxConnections
5. Give this entry the value 256.

Edit the following values:

Win 98 Scaling
under [HKEY_LOCAL_MACHINE \ System \ CurrentControlSet \ Services \ VxD \ MSTCP]
DefaultRcvWindow = 261360
Tcp1323Opts = 1

under [HKEY_LOCAL_MACHINE \ SYSTEM \ Current \ TtrolSip ]
TcpWindowSize = dword: 0003fcf0
Tcp1323Opts = dword: 00000001

For Win98SE an additional bugfix for the scaling function and a NDIS bugfix is required (also interesting for ISDN users).

That should solve most ping problems first.

The ping is ok but it is still jerky

If it continues to jerky it may be due to the graphics performance or you have chokes and losses.

For the latter, please add + net_graph 3 in the start properties. If outside of the play or during it occasionally a choke / loss of 1 75.gif appears, this can be considered normal.

Remember that it also depends on the server connection. If the server is above its performance or connection capacity, for example, the server does this. Or if the server is on another continent, which inevitably leads to a lot of hops and the resulting delays.

With a classic tracert (under Execute-> tracert "ip") you can find out pretty quickly.

Do you have a firewall running? Then give CS all rights to have full access to the I-Net. Still Hackelts? Then the FW turns off as a test, usually that's a cause.

Do you run via a proxy server that is defined as a gateway?

Then test the throughput performance with NETCPS . You should always get over 8 MB / S (MPS) with a Fast Ethernet network (100 M / Bit), at least with all newer chips of the last 2 years. If you are below the value, get new drivers for the network card. Always let the operating modes decide the map.


Have you connected your PCs via a hub or switch? Switch would be better. At what speed?

The error appearance looks like this:

1. You have a hub and this can only half-duplex 10 or 100 Mbit
a) The network types of the clients / servers are set to autonegation ON and cannot negotiate the right speed or the half-duplex method with the hub.
b) The network types of the clients / servers are permanently set to the wrong values.

2. You have a switch 10/100 Mbit
a) The network types of the clients / servers are set to autonegation ON and cannot negotiate the correct speed or the half-duplex / full-duplex method correctly with the switch that is also set to autonegation ON. The switch means a small tit (there are some Adaptec network types with DECchip and COMPAQ switch SW3322)
b) The network types of the clients / servers are set to autonegation ON and cannot adjust to the fixed settings of the switch (switch is set to autonegation OFF and fixed to 100 Mbit and full duplex)
c) The network types of the clients / servers are set to fixed any values ​​and the switch does not accept that.

3. You have damaged a defective cable, for example shielding.

4. You have a program running on the server that is already occupying 100% of the CPU. If you then come with VNC, it does the rest.

In all cases, a few bytes spill through the line and VNC may also be funny, but the data hardly ever arrives at the client.

Those who are completely new to the topic can also take a look at Albert Rommel's page . It is well structured and illustrated. There you will also find a tip or two. Otherwise uses a search engine. There are now countless X-DSL support forums or use the local search function.

Special topic router

As you know from the rules, the topic is not supported here. There are enough forums.

Required UDP ports for routers:

TCP 6003:
Outgoing connectivity to this port on remote destinations. Used for
chat in the HL browser.

UDP 27011:
Outgoing connectivity to this port on remote destinations. Used for the
'custom game' mod browser.

UDP 27005:
Incoming connectivity to this port (or whatever port the client has
changed this to, if not using the default). Used for game traffic
(including voice) between client and server.

TCP 7002:
Outgoing connectivity to this port on remote destinations. Used for WON

UDP 27010:
Outgoing connectivity to this port on remote destinations. Used for
advertising a server on the master lists for server browsers.

UDP 27015:
Incoming connectivity to this port (or whatever port the server had been
changed to, if not the default). Used for all client / server game
traffic (including voice), server info requests, etc.

TCP 7002:
Outgoing connectivity to this port on remote destinations. Used for WON

UDP 27010:
Outgoing connectivity to this port on remote destinations. Used for
advertising a server on the master lists for server browsers.

UDP 27020:
Incoming connectivity to this port (or whatever port the server had been
changed to, if not the default). Used for all client / server game
traffic (including voice), server info requests, etc.

Ping tuning for the advanced Wink!


In advance, as an A-DSL user (especially T-DSL / AOL DSL) don't expect any miracles if you already have a ping between 80 - 120. The ping is not everything either. You can get the ping down from 100 - 120 to 70 - 50 using software and configuration, for example tested by me or a known one, but not only at the expense of download speed, but also at the expense of accuracy in CS! That is why it reads through thoroughly and tests for you which config is approximately the golden mean for you, between ping and accuracy as an example.

The data rates with which the providers advertise their DSL access reach up to 1024 kbit / s downstream and 256 kbit / s upstream, at least for normal mortals. What remains of it effectively depends on various factors, such as the connection of your own ISP (i.e. AOL, Telekom ...) to the server in question or simply the distance from the exchange. Not to forget the protocol overhead, which must also be transmitted. As a rule of thumb, with a good connection, 70% to a maximum of 87% of the theoretically achievable bandwidth is expected. In order to get as close as possible to the maximum value, it is worth looking at various TCP / IP settings. Programs that promise automatic optimization of these parameters often only make the situation worse. These programs usually only start from standard situations. In order not to digress too much, I only marginally describe the necessary settings. Also the connection, now for our network pros, who could definitely write a few kilometers more text. You want to get there quickly Wink.

Important for XP users!

Change MTU size when using XP's own PPPoE client
The XP's own PPPoE client ("DSL driver") uses a maximum MTU size of 1480. This value is hard-coded upwards, ie it cannot be increased become. If you do not want to do without the maximum possible MTU size of 1492 under XP for an optimal download speed, you should install RASPPPOE (see the following installation instructions).
However, Microsoft offers a description in the Knowledge Base of how the max. MTU size can be reduced:


I know u. A. also because of this article, because time and again the mistaken opinion is spread on websites and forums that with any tools or registry entries the max. MTU value can be increased when using XP's own driver. However, Microsoft shows in this article which registry entries are required to get the max. However, reducing the MTU value also expressly points out that the max. possible MTU value is 1480 bytes.
Quote: "The default and maximum PPPoE MTU size is 1480 bytes."

Now we come to the playground of the settings:

Windows users may only want to use the TCP / IP protocol. If there is no other option then only limited to DSL.

Maximum Transfer Unit (MTU)

We communicate on the Internet using the TCP / IP protocol. The MTU value defines the maximum size of the data packets. Determining the defined size from the outset has the advantage that with an MTU of not more than 1464 bytes / packet, the router does not have to fragment it again, which is at the expense of pinging. This takes up unnecessary time, as does the automatic negotiation of MTU via ICMP messages *. That is why it is better to choose an optimal MTU value from the outset.

* ICMP = Internet Control Message Protocol. TCP / IP protocol used to exchange error and status messages.

So you have to approach the optimal MTU package size: The

easiest way to do this is to use the famous old ping proggie that every MS user has.

Via the MS-DOS prompt or Start -> Programs -> Execute, you choose the command:

ping -f -l 1500 hostname

So hostname I would take the server name or IP that you mainly use or which is known to be very fast.

If you receive the feedback packet should be fragmented, but the DF flag is set, the packet size is reduced by ten bytes until the message no longer appears. After that I would feel my way back up or down in 1 byte steps.

If you have found the maximum value with which you can send the package without the "DF flag", add 28 bytes for the ICMP header. Then you have the optimal value.

So example:

You have explored 1412 bytes as the maximum packet size for yourself without getting the DF message.

1412 + 28 = 1440 are entered as the MTU value

Maximum Segment Size (MSS)

While MTU specifies the size of the complete data packet, the "Maximum Segment Size" (MSS) determines the space available for the user data. These share the space with the administrative information in the header, which provides information about the sender and recipient, for example.

Overview of related values:

1500 Maximum packet size that can be sent on the Internet without fragmentation
1492 Maximum packet size when using PPPoE
1460 MSS with an MTU value of 1500
1464 With PPPoE implementation: Maximum ping size without fragmentation
1452 MSS with an MTU Value of 1492 (typical for PPPoE)
576 Typical MTU for analog modem dial-up connections
536 MSS with an MTU value of 576
48 Total of the headers of TCP, IP and PPPoE
28 Total of the headers of IP and ICMP
20 IP headers
20 TCP headers
8 PPPoE headers

The formula is simple: MTU header = optimal MSS size

TCP Receive Window (RWIN)

In short: “The Transmission Control Protocol (TCP) ensures that information is transported correctly over the network. If there are errors in the network, a computer sends its data again after a certain time. This is repeated until the sender receives confirmation from the remote station that it has received the information correctly. A RWIN value above 17 no longer brings any advantages. But you have to analyze your management to determine this value. Take a look at DSL reports.
By default, Windows 9x, Me and NT use an eight KB buffer; Reserve Windows 2000 and XP 16 KB

Additional parameters


Path MTU Discovery regulates whether the TCP connection uses a fixed maximum value for MTU or tries to find out the suitable value itself. By default, Path MTU Discovery is active on Windows.


The search for "black holes" refers to routers that do not send back an ICMP message if they had to fragment an IP packet with the "don't fragment bit" set. These messages are important for Path MTU Discovery to work properly. By default, Windows does not use black hole detection to minimize network traffic.


This option enables various scaling options, as defined in RFC 1323. For example, if you need a value higher than 64 KB for the TCP Receive Window (RWIN), you must switch on this parameter.


The "Time To Live" determines after how many routers an IP packet is discarded as undeliverable. Windows 95 uses the value 32 by default, all other versions up to Windows XP 128. However, this in no way influences the speed of a connection; with a shorter TTL you only get the error message that no data is flowing, a little earlier.

Ping tuning?

You are welcome to lower MTU and adjust all other necessary values. The disadvantage is that the ping is better with a smaller package size, but the download is also lower! You only buy a better ping with lower download speeds.

On the CS side, I now recommend a setting

example for low ping for modem / ISDN or for emergency and fault localization also for DSL users: rate 7500.000000
cl_updaterate 17
cl_cmdrate 17

Whether these values ​​are also satisfactory in terms of accuracy and playability, I leave now in the room. If you want more specific config examples (also for AOL), I recommend Klalashnikov's Speed ​​Guide. There I would just not set the MTU value to 1480 because the packets would otherwise have to be fragmented, which would have to be pinged again. The best thing to do is to explore it.

Help with AOL 6-7 and / also XP

For this detailed AOL / XP help, thanks to our Bonzai!

- Beginning -

Topic: The AOL DSL + Win XP problem solution !!!

So, since many CS players with AOL DSL (AOL 7.0) in connection with Win XP have a very bad ping (300-3000 ms !!!) and so CS with which is almost unplayable, I have written a help with that everyone would have to solve this problem !!! I myself, also as a user of AOL DSL, have solved it that way.

Many of them may not be able to connect at all (the time when connecting is counted down and an error message appears at the end). This problem is solved by starting CS, now if you are in the main menu, you switch to the Windows task manager with CTRL + ALT + REMOVE, go under Processes, look for the & quot; cstrike.exe & quot; from the list, right click on it and from the menu that appears you set the priority of the & quot; cstrike.exe & quot; set to LOW.
Now you should at least be able to connect to the CS server.

But if you do not want to always use this trick, you can alternatively create a .bat file that does all of the above work independently.
This is how you do it:
- you open the Windows Editor and simply write the following in the first line (only CS Mod version):
start / low hl.exe -game cstrike -console
behind -console you can set other start parameters, such as: -numericping or -nojoy

- this is how you do it if you have the CS Retail version:
start / low cstrike.exe -console
here you can also set additional start parameters after -console (see above)

Now go to save and choose the file type: & quot; All files & quot; and in the file name you do, for example: & quot; startcs.bat & quot ;. You save this file in your Counter Strike or Half Life directory (the startcs.bat must be in the same folder as the cstrike.exe or the hl.exe). From now on you must ALWAYS start your CS with this file !!! Of course, you can also create a shortcut for this file on the desktop and assign the CS icon to it.

So the thing with the connection problems is now solved, now all you have to do is fix the ping, because this will still be 100 - 200 ms, which you can not be satisfied with DSL, also with AOL DSL not * g * !!!

Tips to improve the ping (bring it in the range of 70-100 ms)
- you should definitely delete the QoS packet planner from the network properties (most will know how to do this, if not then mail me: wcsrk @ aol. com)

- since the AOL software uses the Wan Miniport driver from Win XP for the Inet connection, you should definitely use the OEM CFOS driver 4.12 for the connection to the Inet [do not create a dial-up connection with CFOS (does NOT work with AOL! !!) but connect the AOL 7.0 software with this CFOS driver] You can get
these drivers on the FTPs of AOL, if you can't find them, then email me: wcsrk@aol.com

- As is well known, you should also enter the optimal DSL values ​​in the Windows registry ... this is best done with dial-up speed.
You can get the program pretty much everywhere ... if not, search with Google ... there are enough download sources!
[Tip: You can reduce the ping a little (approx. 5-10 ms) by setting the MTU value a little lower than the program specifies. The disadvantage of this is that the speed of downloads deteriorates somewhat (instead of 90 kbyte / sec ... approx. 85 kbyte / sec)]

- and finally you should have a decent cfg that contains the optimal DSL values, me play with the following values:

rate 12000
cl_rate 9999
cl_cmdrate 101
cl_updaterate 37

With these values ​​I have a ping of 30-50 ms even in the Netgraph and in the scoreboard the LATENCY stands for me at 60-80 ms (very good for AOL DSL !!!).
IN and OUT in the Netgraph are 4-5 kbytes / sec.
And CHOKE and LOSS are of course 0 ... in some situations this goes up to 1-5 ... but is rarely

Jo and so you can even pull a lot with AOL !!!
I hope this guide will help you.

If you have
any questions about the AOL - XP Guide, please contact Bonzai, who can be reached at the following email addresses: wcsrk@aol.com or

- Ende -

EDIT 06.03.2002 for troubleshooting and our proxy connect fans:

List of all RAS Error :

600 An operation is still in progress.

601 The access number (handle) for the connection is invalid.

602 The connection has already been opened.

603 The caller buffer is too small.

604 Wrong information has been provided.

605 Connection information cannot be set.

606 No hardware is connected to the connector.

607 The event is not allowed.

608 The device does not exist.

609 The device type does not exist.

610 The buffer is invalid.

611 route not available.

612 route not assigned.

613 Invalid compression specified.

614 All buffers full.

615 Connection not found.

616 Asynchronous request is still being processed.

617 Connection or device has already been disconnected.

618 Connection not open.

619 port is not connected.

620 There are no endpoints.

621 Phone file could not be opened.

622 Phone file could not be loaded.

623 Telephone entry could not be found.

624 Phone file could not be written.

625 There is invalid information in the phone book file.

626 Character string could not be loaded.

627 Key could not be found.

628 line was not connected.

629 port was disconnected from the remote computer.

630 port was disconnected due to a hardware failure.

631 The connection was disconnected by the user.

632 The structure size is not correct.

633 The port is already in use or is not configured for RAS as a client port.

634 Your computer cannot be registered on the remote network.

635 Unknown error.

636 Wrong device connected to the connector.

637 character string could not be converted.

638 Request timed out.

639 No asynchronous network available.

640 A NetBIOS error has occurred.

641 The server could not provide NetBIOS resources to support the client.

642 One of your NetBIOS names is already registered in the remote network.

643 network adapter in the server failed.

644 You will not be able to receive network messages.

645 Internal authentication error.

646 The user account is prohibited from logging on at this hour.

647 User account blocked.

648 Password expired.

649 user account does not have remote access rights.

650 RAS server is not responding.

651 Your modem (or other connection device) has reported an error.

652 Unprocessed response from the device.

653 A macro required by the modem could not be found in the INF file in the section for this device.

654 A command or response in the INF file in the section for this device refers to an undefined macro.

655 The macro could not be found in the INF file in the section for this device.

656 The macro in the INF file in the section for this device refers to an undefined macro.

657 The INF file for this device cannot be opened.

658 The device name in the INF file (or the media name in the INI file) is too long.

659 The INI file for this medium refers to an unknown device.

660 The INF file for the device contains no response for this command.

661 A command is missing from the device .INF file.

662 Attempt to use a macro not listed in the device .INF file.

663 The INI file for this medium refers to an unknown device type.

664 Memory cannot be allocated.

665 port not configured for RAS.

666 Your modem (or other connection device) is not working.

667 INI file for this medium cannot be read.

668 Connection terminated.

669 Invalid usage parameter in the INI file for this medium.

670 Section name in the INI file for this medium cannot be read.

671 Device type in the INI file for this medium cannot be read.

672 Device name in the INI file for this medium cannot be read.

673 Use in the INI file for this medium cannot be read.

674 Maximum connection baud rate in the INI file for this medium cannot be read.

675 Maximum carrier baud rate in the INI file for this medium cannot be read.

676 line busy.

677 Instead of a modem, one person answered.

678 No response from POP.

679 Carrier baud rate could not be determined.

680 No dial tone.

681 Device reports general error.










691 Access denied because domain username and / or password is / are invalid.

692 Hardware error in the connection or in the connected device.






698 A response key in the INF file for the device is not in the expected format.

699 The device response caused a buffer overflow.

700 The expanded command in the INF file for the device is too long.

701 The device switched to a connection baud rate that is not supported by the serial driver.

702 device responded unexpectedly.





707 X.25 diagnostic display .

708 The account has expired.

709 Failed to change the password for the domain.

710 Serial overflow errors were detected when exchanging data with the modem.

711 RasMan initialization failed. Check the event log.

712 Biplex connection is initialized. Wait a few seconds and then dial again.

713 There are no active ISDN lines available.

714 There are no ISDN lines available to make a call.

715 Too many errors occurred due to a bad phone line.

716 The Remote Access IP configuration cannot be used.

717 No IP addresses from the static pool of remote access IP addresses are available.

718 PPP timeout.

719 PPP was terminated by remote computer.

720 No PPP control protocols configured.

721 Remote PPP peer is not responding.

722 The PPP package is invalid.

723 The phone number, including the area code and extension, is too long.

724 The IPX protocol cannot dial on the port because the computer is an IPX router.

725 The IPX protocol cannot dial on the port because the IPX router is not installed.

726 The IPX protocol cannot be used for dialing on more than one connection at the same time.

727 TCPCFG.DLL is not accessible.

728 No IP adapter can be found that is connected to the RAS service.

729 SLIP can only be used if the IP protocol is installed.

730 Computer registration not completed.

731 The protocol is not configured.

732 PPP negotiation is not working.

733 The PPP control protocol for this protocol is not available on this server.

734 PPP protocol ended.

735 The requested address was rejected by the server.

736 The remote computer has canceled the control protocol.

737 loopback detected.

738 No address was assigned by the server.

739 The remote server cannot use the password encrypted by Windows NT.

740 The TAPI devices configured for RAS were not initialized or installed incorrectly.

741 The local computer does not support encryption.

742 The remote server does not support encryption.

743 The remote server requests encryption.

744 The IPX network number assigned by the remote server cannot be used. Check the event log.

752 A syntax error occurred while processing a script.

Overview of the most important Winsock error codes:

WSAEINTR 10004 A blocking process was interrupted by a call to WSACancelBlockingCall.

WSAEBADF 10009 The specified file handle is invalid.

WSEACCES 10013 Access to a socket was not permitted due to the socket's access rights.

WSAEFAULT 10014 An invalid pointer address was found when trying to use the pointer argument of a call.

WSAEINVAL 10022 An invalid argument was specified.

WSAEMFILE 10024 Too many open sockets.

WSAEWOULDBLOCK 10035 A non-blocking socket operation could not be performed immediately.

WSAEINPROGRESS 10036 A blocking operation is currently in progress.

WSAEALREADY 10037 An attempt was made to subject a non-blocking socket to an operation that has already been performed.

WSAENOTSOCK 10038 An operation related to an object that is not a socket.

WSAEDESTADDRREQ 10039 A required address was missing during a socket operation.

WSAEMSGSIZE 10040 A message sent over a datagram socket was too large for the internal message buffer or other network limit, or the datagram receive buffer was too small for the datagram.

WSAEPROTOTYPE 10041 When the socket function was called, a protocol was specified that does not support the semantics of the requested socket type.

WSAENOPROTOOPT 10042 An unsupported option or level was specified when calling getsockopt or setsockopt.

WSAEPROTONOSUPPORT 10043 The requested protocol has not been configured or there is no implementation for it.

WSAESOCKTNOSUPPORT 10044 This address group does not support the specified socket type.

WSAEOPNOTSUPP 10045 The operation is not supported by the object type referred to.

WSAEPFNOSUPPORT 10046 The requested protocol group has not been configured or there is no implementation for it.

WSAEAFNOSUPPORT 10047 An address was used that is not compatible with the requested protocol.

WSAEADDRINUSE 10048 Normally each socket address (protocol, network address or connection) may only be used once.

WSAEADDRNOTAVAIL 10049 The requested address is invalid in this context.

WSAENETDOWN 10050 The network was inactive during a socket operation.

WSAENETUNREACH 10051 A socket operation was related to an unavailable network.

WSAENETRESET 10052 The connection was terminated due to keepalive activities because an error was found during the process.

WSAECONNABORTED 10053 An existing connection was terminated software-controlled by the host computer.

WSAECONNRESET 10054 An existing connection was closed by the remote host.

WSAENOBUFS 10055 A socket operation could not be performed because the system lacked buffer memory or a queue was full.

WSAEISCONN 10056 A connection request related to an already connected socket.

WSAENOTCONN 10057 A request to send or receive data was prevented because the socket is not connected and (when sending via a datagram socket with a sendto call) no address was specified.

WSAESHUTDOWN 10058 A request to send or receive data was prevented because the socket had already been shut down in this direction by a previous shutdown call.

WSAETOOMANYREFS 10059 Too many references to a kernel object.

WSAETIMEDOUT 10060 A connection attempt failed because the remote site did not respond properly after a certain period of time, or the connection established was faulty because the connected host did not respond.

WSAECONNREFUSED 10061 A connection could not be established because the target computer refused to connect.

WSAELOOP 10062 The name could not be translated.

WSAENAMETOOLONG 10063 The name component or name was too long.

WSAEHOSTDOWN 10064 A socket operation failed because the target host was unavailable.

WSAEHOSTUNREACH 10065 The host could not be reached during a socket operation.

WSASYSNOTREADY 10091 WSAStartup does not work because the system that is providing this service with network services is currently unavailable.

WSAVERNOTSUPPORTED 10092 The requested version of Windows Sockets is not supported.

WSANOTINITIALISED 10093 W The application did not call the WSAStartup function, or an error occurred with this function.

WSAEDISCON 10101 As a return value from WSARecv or WSARecvFrom, this indicates that the remote station has caused the shutdown.

WSAHOST_NOT_FOUND 11001 The specified host is unknown.

WSATRY_AGAIN 11002 This is usually a temporary error in resolving host names. The reason is that the local server has not received any feedback from the authorizing server.

WSANO_RECOVERY 11003 An unrecoverable error occurred during database call.

WSANO_DATA 11004 The requested name is valid and was found in the database. However, it does not have the correct assigned data that should be evaluated.
Added: 2 weeks ago
Modified: Never edited!
  Thanks List: [+]  
Add Feedback

You cannot post yet!
Get involved on GVME by posting your thoughts. Give authors your feedback to help them develop.

To post in this submission register or login