Winsock Fix

Originally written to fix problems with the other programs, it is now one of the main building blocks of CC Cluster.

Latest version 1.99

This version is compatible with previous configuration files. Just run the program. It will make any changes that are needed.

Use of this program allows the cluster computer to be up and running with a simple reboot. Just place this program and other required programs in the startup menu.

This Window's program intercepts connections to a Dx Cluster. It then makes a connection for the user to the Dx Cluster. The program delays these through connections if required. The through connections need to be delayed if many users attempt to connect to the dx cluster at almost the same time. This is especially true with AR Cluster nodes. Without this program, the node can lock up and refuse further connections. If a node reboots, or otherwise loses its users, then they all will be attempting to reconnect at the same time. This program stops the node winsock from locking up in this situation. It has been tested with both AR Cluster and Dx Spider.

Winsock Setup for User Port

Cluster Setup

If the cluster is listening on port 23 for users, change it to an unused port, ie port 7333 or any port of your choice.

Download Winsock.exe for AR Cluster or Dx Spider. CC Cluster requires a special version linked to from the CC Cluster page.

Run it once and exit. The program will generate "winsock.cfg"

Edit this file.

NB - The line "ListeningPort" may be missing in your config file. It MUST be manually added if it is missing.

• ListeningPort = old port number of Dx Cluster before it was changed in the "Cluster Setup" above. (probably 23).
  eg. "ListeningPort", "23"
• ClusterIP = Local IP Address of the Dx Cluster (192.168.0.100 on my network). If possible, don't use 127.0.0.1 for the IP address as this address shows up in the login message. 192.168.x.x numbers do not show.
• ClusterPort = port number you now use for the cluster in the "Cluster Setup" above. (7333)
• MonitorPort = Port that the Monitor.exe program will connect to. I use 15555. You can select any unused port you want.
• Loop Time = Use 192 for Win2K. What you want is for the time to be 3 seconds between users when connecting.
• Preload = Expected number of users. Preloads the number of winsocks to save time if they all reconnect at once. If more users connect than the preloaded number, the program will simply load more sockets etc. It just requires a slight additional time per user to do this, which should not be a problem, once the initial surge is over.
• Locked Out = IP addresses of users that are locked out. Example is given of "10.01.01.11". Change to suit your situation. You may have as many entries as required. All begin with "Locked Out", ..... Each on its own line. Enter as many significant digits as you wish for the IP address.

Winsock Setup for AR Cluster Passive Port

Setup same as for user port except change the Listening port to 3607 and Cluster Port to 3606. Set router to translate incoming port 3606 to port 3607.

Winsock Setup for Dx Spider running in Windows

If you expect more than 60 telnet connections, you need to do this!

Dx Spider for Windows has a limitation of about 60 telnet connections. The solution is to run 2 or more copies of Dx Spider in your computer and use this program to look after the users. All incoming users connect to the same port. After an instance of Spider fills up, further users will be re-directed to the next instance. I am currently running 3 instances of Spider in my machine.

Nodes can be directed to only connect to the first instance, since they get upset if the call they connect to isn't exactly correct. This requires you to set aside an incoming port for nodes and another port for users. If you set aside a port for nodes, then you need two "ListeningPort" lines in the .cfg file. The first is the node port, the second the port for all the users.

There are additional configuration items to be added to the winsock.cfg file.

• As many "ClusterIP", "xxx.xxx.xxx.xxx" lines as you have instances of Spider. These probably will all be the same, but are required anyways.
• Each "ClusterIP" line must be followed by "ClusterPort", "xx" (Each instance must have its own unique port number.)
• "ReservedForNode", xx (where the xx = number of streams set aside for node connections. Only required if you have set aside a node only port.)
• "MaxConnects", 56

Run

• Start the cluster .exe program
• Start winsock.exe
• Start monitor.exe whenever you wish. It is not necessary to run it.

After about 1 minute the winsock.exe will full screen, covering the cluster display. This is done deliberately for use with AR Cluster nodes. If the AR Cluster screen is displayed with 40+ users or so and during contests, it can lock up due to its inability to refresh the screen fast enough. With less users, there should be no problem.

---

Monitor Setup

CC Cluster

User Program