| |
VK2AWZ > WINPAC 15.10.07 08:26l 39 Lines 1297 Bytes #999 (0) @ WW
BID : F80009VK2AWZ
Read: DK5SG GUEST
Subj: Winsock error
Path: DB0FHN<DB0FOR<DB0MRW<DK0WUE<DB0RES<IK2XDE<IW2OAZ<IW2OHX<I0TVL<CX2SA<
VK2DOT
Sent: 071015/1830Z @:VK2DOT.CC.NSW.AUS.OC #:20139 [Niagara Park] FBB7.00i
From: VK2AWZ@VK2DOT.CC.NSW.AUS.OC
To : WINPAC@WW
Hi, I have been trying Telnet with Winpack, as our RF bbs systems have
been out for over a week and maybe some time before restoration?
However I am having mixed success with telnet and my troubles are:
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
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.
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.
Somehow I feel the aboves, might have something to do with not being able
to fully access a telnet BBS.
I never have any such troubles with RF BBS's
Your help would be appreciated
PS I am using DIALUP, not broadband.
73 - Dave, VK2AWZ @ VK2DOT
Message timed: 16:17 on 2007-Oct-15
Message sent using WinPack-Telnet V6.80
Read previous mail | Read next mail
| |
