Manual TCP/IP Configuration

[williameboley]

This is intended for the more computer savvy and experienced user. It is not meant for the novice. Users may follow the advice of other members with the understanding it is at their own risk. The recommended TCP/IP stacks tool is sufficient for most Members and has advance settings for the more adept.

These suggestions were excerpted from a post submitted by Contributing Member: TheHound. Additional content and editing provided by williameboley.
You could try something that seemed to help me greatly. I've had IRC issues. This mostly solved them. Adjust the Windows KeepAliveInterval and KeepAliveTime. I kept turning mine down until I had 15 for each. This seems to be working.The thing about http tunnel is it makes a huge number of http connections to TCP port 80 and Windows, being the non-intelligent OS it is, doesn't declare them dead sometimes, even if they have had no data exchange for a very long time. This fix addresses that If you have XPSP2 installed, make sure to use the patch from http://www.lvllord.de to override the half open connection limit SP2 imposes.

In conjunction with the keep alives, you'll want to set TcpTimedWaitDelay down to 30. This is how long your pc waits before resetting a connection determined dead, thus freeing up the user port.This setting is recommended by Microsoft for any Windows system running a server because of connection volume.

Optionally set MaxUserPort to 50000 or so as well. Then you'll be configured just like a server, which is appropriate with any app that makes a huge amount of connections,such as http tunnel.

These are extreme settings but cause me to connect 90% or better of the time

KeepAliveInterval 15
KeepAliveTime 15
---------------------------------------------------------------------------------------------------------------------
TcpTimedWaitDelay
The TcpTimedWaitDelay value determines the time that must elapse before TCP/IP can release a closed connection and reuse its resources. This interval between closure and release is known as the TIME_WAIT state or twice the maximum segment lifetime (2MSL) state. During this time, reopening the connection to the client and server costs less than establishing a new connection. By reducing the value of this entry, TCP/IP can release closed connections faster and provide more resources for new connections. Adjust this parameter if the running application requires
rapid release, the creation of new connections, or an adjustment because of a low throughput caused by multiple connections in the TIME_WAIT state.The default value is 0xF0, which sets the wait time to 240 seconds (4 minutes). The smallest recommended value is 0x1E, which sets the wait time to 30 seconds. Use this procedure to view or customize your value.

Start the regedit command, navigate to the

HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Ser vices\\TCPIP\\Parameters registry subkey, and create
a new REG_DWORD value named TcpTimedWaitDelay.
Set the value to decimal 30, which is Hex 0x0000001e This value sets the wait time to 30 seconds.
Close the registry editor.
Stop and restart the system.

Continued Next Page

[williameboley]

KeepAliveTime
The KeepAliveTime value controls how frequently TCP/IP tries to verify that an idle connection is still intact. If there has been no activity for this amount of time, a keep-alive tranmission will be sent. If the network is intact and the partner is active, the partner will respond. If you need to be sensitive to lost partners, in other word, you need to recognize that the partner has been lost more quickly, consider reducing this value. If idle connections with long periods of inactivity are common and lost partners are uncommon, you may want to increase this value to
reduce overhead. By default, Windows sends a keep-alive message when an idle connection has had no activity for 7,200,000 milliseconds (2 hours). Often 1,800,000 milliseconds is the preferred value so half
closed connections are sensed at 30 minutes. Use this procedure to view
or customize your value.

Start the regedit command, navigate to the

HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Ser vices\\Tcpip\\Parameters registry subkey, and create or set new a REG_DWORD value named KeepAliveTime.
Set this value to an appropriate number of milliseconds.
Close the registry editor.
Stop and restart the system.

KeepAliveInterval
The KeepAliveInterval value determines how often TCP/IP repeats keep-alive transmissions when a keep-alive response is not received from the partner. The connection will be abandoned when the number of consecutive keep-alive transmissions with no response exceeds the value of the TcpMaxDataRetransmissions. If long response times are expected, you may need to increase this value to reduce overhead. If you need to reduce the time spent verifying that a partner has been
lost, consider reducing this value or the TcpMaxDataRetransmissions value. By default, Windows waits 1000 milliseconds (1 second) for a keep-alive response before resending the keep-alive message.
Use this procedure to view or customize your value.

Start the regedit command, navigate to the

HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Ser vices\\Tcpip\\Parameters registry subkey, and create or set new a REG_DWORD value named KeepAliveInterval.

Set this value to an appropriate number of milliseconds.
Close the registry editor.
Stop and restart the system

MaxUserPort
The MaxUserPort value determines the highest port number that TCP/IP can assign when an application requests an available user port from the system. If your system reports Erro establishing socket exceptions, it may be caused by an inadequate number of anonymous (ephemeral) ports, especially if your system opens a large number of ports to establish
connections to web services, a database, or other remote resources.
By default, Windows reserves port numbers 1024 to 5000 for anonymous (ephemeral) ports A common practice is to set this value to 32768. Use this procedure to view or customize your value.
Start the regedit command, navigate to the
HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Ser vices\\TCPIP\\Parameters registry subkey, and create a new REG_DWORD value named MaxUserPort.
Set this value to at least decimal 32768.
Close the registry editor.
Stop and restart the system.

[williameboley]

I followed the advice of TheHound on manually configuring the TCP/IP settings ( listed in this post ) on my computer. I state that no harm was done to my computer. Though I always respected TheHound's opinion. I have used his suggestions on other issues as well on Computer and Network related matters.