[ct-user] CT Networking - solved
Ted Bryant
w4nz at comcast.net
Tue Nov 15 19:04:52 EST 2005
Thanks to all those who answered my call for help, and help I did get. Seems my problem was having
the wrong port specified in the setup for NETTSR. Several people suggested this as the probable
cause of trouble. As suggested, I searched the documentation and finally found the answer I needed
on what port CTWin uses, in K1TTT's document "K1TTT CT Ethernet TSR". It was tucked away on the
very last page. For anyone who may be facing a similar issue, the NETTSR command line has to look
like:
Nettsr [network card's IP address] 100 0.0.0.0 3030 255.255.255.255
This will talk to CTWin. Note that the port (3030) is different than the default (9870) and CTWin
uses 255.255.255.255 as the broadcast address.
For the full story go to:
www.k1ttt.net/software/nettsr.html
Thanks again and 73,
Ted W4NZ
>-----Original Message-----
>From: ct-user-bounces at contesting.com
>[mailto:ct-user-bounces at contesting.com]On Behalf Of Ted Bryant
>Sent: Tuesday, November 15, 2005 8:51 PM
>To: ct-user at contesting.com
>Subject: [ct-user] CT Networking
>
>
>I am trying to network CT-dos and CT-win over ethernet. I have a network card (3Com 3c905B-txnm)
>installed in the dos pc. The dos packet driver appears to load ok and K1TTT's NETTSR also appears
>to load as well.
>
>After loading these and trying to ping from the win pc, the ping times out with no response. In
>addition the dos pc appears to lock up. It will not accept any keyboard commands and I have to
>re-boot. The "dos" pc is actually a Win98SE machine which I've booted to a dos command prompt on
>startup. (could this be the problem?) The win pc is my dedicated "radio" pc which is connected to
>the network and is performing normally.
>
>The network router is a Belkin BEL1KQW cable/DSL/wireless with a built-in 4-port hub. I've tried
>this with DHCP on and off with no difference.
>
>Suggestions? Advice? HELP!?
>
>TIA,
>73, Ted W4NZ
More information about the CT-User
mailing list