[Dxspider-support] Connecting to clusters via ip
Filip Jonckers
fjonckers at Interconnect.be
Tue May 21 08:42:57 BST 2002
Hi John,
First try from a command line window - so you can test if the problem is
related to Spider or on a operating system level...
You're running win98?
Open a MSDOS box ...
can you do a ping to the IP address ?
(ping 130.126.139.93)
try to do a telnet connection from the command line
telnet 130.126.139.93 8000
does this work ?
The listening port used depends on the choice of the sysop...
but prefered choices are indeed 7300 and 9000
I wouldn't use 8000 or 8080 because they are often targets of hackers
trying to find proxy servers (which use these portnumbers)
Filip
ON1AFN
-----Original Message-----
From: John Grove
Sent: Tue 5/21/2002 2:33 AM
To: dxspider-support at dxcluster.org
Cc:
Subject: [Dxspider-support] Connecting to clusters via ip
All,
I am having a problem connecting to other clusters via the
internet. If the
connect script contains a name (dns) the connect works fine. If
it contains
an ip address, I get the following:
This is my connect script:
timeout 60
connect telnet 130.126.139.93 8000
'login' 'ke2oi'
This is the error I get:
connect 8: timeout set to 60
connect 8: timeout set to 60
CONNECT 8: sort: telnet 130.126.139.93 8000 Bad File descriptor
Use of unitialized value in subroutine entry at
/spider/perl/msg.pm line 217
Connect 5 failed to 130.126.139.93 8000 bad file descriptor
This is version 56.954 running on a win 98 box.
Thanks
John KE2OI
_______________________________________________
Dxspider-support mailing list
Dxspider-support at dxcluster.org
http://www.tobit.co.uk/mailman/listinfo/dxspider-support
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/ms-tnef
Size: 5638 bytes
Desc: not available
Url : http://www.tobit.co.uk/pipermail/dxspider-support/attachments/20020521/06ef350c/attachment.bin
More information about the Dxspider-support
mailing list