Date: Fri, 3 Dec 93 04:30:27 PST From: Ham-Digital Mailing List and Newsgroup Errors-To: Ham-Digital-Errors@UCSD.Edu Reply-To: Ham-Digital@UCSD.Edu Precedence: Bulk Subject: Ham-Digital Digest V93 #134 To: Ham-Digital Ham-Digital Digest Fri, 3 Dec 93 Volume 93 : Issue 134 Today's Topics: KPC-3: Remote Station Gets 'Busy' Replies?? Send Replies or notes for publication to: Send subscription requests to: Problems you can't solve otherwise to brian@ucsd.edu. Archives of past issues of the Ham-Digital Digest are available (by FTP only) from UCSD.Edu in directory "mailarchives/ham-digital". We trust that readers are intelligent enough to realize that all text herein consists of personal comments and does not represent the official policies or positions of any party. Your mileage may vary. So there. ---------------------------------------------------------------------- Date: Wed, 1 Dec 93 00:44:03 PST From: elroy.jpl.nasa.gov!sdd.hp.com!portal!cup.portal.com!AllanWS@uunet.uu.net Subject: KPC-3: Remote Station Gets 'Busy' Replies?? To: ham-digital@ucsd.edu This problem is making me lose more hair than I have on my head! I have a KPC-3 TNC which I use to connect to the local PacketCluster. The cluster sysop set up a script where if the path between the cluster and my location drops and I retry out, the cluster will attempt to reconnect to my TNC. This is how I discovered the 'problem'... With the computer off (a 386 clone), leaving the TNC/radio on, a station cannot connect to my TNC. They receive a ***busy on their end and I get a *** connect request! Note that the remote station is not trying to access the KA-Node or the mailbox; he is just trying to connect to my normal user ID. When I turn the computer on and boot up my packet software, I get a buffer full of *** connect requests as well as other channel traffic. Stations can now connect to me. It seems that I must keep the computer on with terminal software loaded up but this does not seem right. I have been involved with packet for 3 years and have used the MFJ-1278 with no problems. In fact, I cannot reproduce this problem with the MFJ. Some locals suggested CTS/RTS hardware flow control might be at fault here. I have my USERS set at 10 /MAXUSERS at 10 btw. Is there anything I am overlooking here? The KPC-3 is 3 weeks old and I never got this thing to work like the MFJ (KPC firmware is 5.1). Any clues?? Thanks Al Schlaugat / allanws@cup.portal.com \ Amateur Radio: N9ISN ------------------------------ End of Ham-Digital Digest V93 #134 ****************************** ******************************