I run a VE7CC DX Cluster with the latest software. It is W7JD-1 >>> w7jd.ddns.net, Port 9000.
As I am the sysop of the DX node, I require a password to log in. I have this set up in the configuration,
however for some reason, the connection is never completed. It appears to be a matter of timing,
and/or not receiving an expected test. Here is the output from a VarAC connect attempt to my DX cluster,
with the resulting error message at the very bottom. I would appreciate any suggestions.
Connecting DxCluster...* WELCOME TO W7JD-1 - The Digital Experimenter's Group *
SYSOP GARY, K7EK (gary.k7ek at yahoo.com)
* Located in Radcliff, Kentucky, Grid EM77at *
Running CC Cluster software version 3.366
* PLEASE ENABLE YOUR GRID SQUARE: Example - SET/QRA EM77AT and enable
DXGRID: SET/DXGRID. Those commands make the cluster display the spotting
station's locator if set by the spotting station. Substitute your own grid
square when setting QRA. Thanks!
* This DX node is currently employing a feed from the Reverse Beacon
Network (RBN). Use SET/SKIM to see RBN spots, SET/NOSKIM to turn them off.
K7EK now operates a CW Skimmer that feeds W7JD-1 and RBN.
NOTE: You must enable Skimmer spots every time you log in. I suggest
automating this in your software by setting up a script to send SET/SKIM upon login.
* To receive FT4 or FT8 spots: SET/FT4 and SET/FT8. To disable them type
UNSET/FT4 and UNSET/FT8.
* From time to time there will be disconnects. It is a fact of life. This
may be due to internet related issues or Microsoft Windows automatic updates. Should
that occur, simply reconnect. Please enable AUTOCONNECT or AUTORECONNECT in your client.
* Also, as an aid in keeping the connection operating, please enable
KEEPALIVE. I have Spectrum Internet, which at times is very poor. I get
loss of service often for no reason. Please bear with me as it is the best
option I have.
* If you find yourself unable to reach k7ek.ddns.net or w7jd.ddns.net, please do a DNS FLUSH,
restart your PC, and try again.
Please enter your call:
Error in dxcluster spot: Unable to read data from the transport connection: 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.