| |
YN1V > WINPAC 17.10.07 02:34l 49 Lines 1723 Bytes #999 (0) @ WW
BID : 5E0526YN1V
Read: GUEST
Subj: Re: Winsock error
Path: DB0FHN<DB0MRW<DK0WUE<ON0BEL<ON4HU<PY1AYH<PY1AYH<CE8FGC<HR1FBB<YN1BBS
Sent: 071017/0013Z @:YN1BBS.MGA.NIC.CEAM #:350 [Managua] FBB7.00i $:5E0526YN1V
From: YN1V@YN1BBS.MGA.NIC.CEAM
To : WINPAC@WW
>
> a/
> If I use any port other than :23 I get Winsock error connection failed.
> This is with the port number as given to me by the target BBS's
This is upon the target BBS. If the only provide port 23 for connections,
that is the only one it will work. Besides, you have to be authorized to
do telnet access, but apparently you are for the info in the other
questions.
> b/
> Next problem with Winpack telnet is auto BBS, that will not send or
> receive compressed data. When I do tick mail options for compressed that
> causes a lockup problem, as the target gets to send AD which is not
> recognised by winpack. It is ok for auto use uncompressed.
I don't know why or any work around. The thing is I have been never be
able to send and receive compress data in the same connection. Because of
that I leave compress data unchecked... is only text so is not that bad.
> c/
> In winpack help, it says to edit BBS.txt script for the callsign as
> .$MYCALL The help says to note the full stop before $MYCALL, as this
> is MOST important. Howver if I put in the dot, my connection attempt is
> blocked, as unknown callsign. Removing it or just putting in VK2AWZ is
> ok.
Again, never been able to make this script to work with the $stuff. I put
plain text to do the loging as follow:
SEND YN1V
SEND mypassword
and it works just fine. As it is working and I am not changing my call or
password, I don't mind.
Hope sharing my frustrations works for you. If you find any alternate
solution for those problems, please let me know.
Neville - YN1V @ YN1BBS
Sysop YN1BBS & HT8PAQ
Message timed: 00:12 on 17/Oct/2007 UTC
Message sent using WinPack-Telnet V6.80
Read previous mail | Read next mail
| |
