From: "Matt" <matt@proweb.co.uk>
To: "9fans" <9fans@cse.psu.edu>
Subject: Re: [9fans] drawterm etc.
Date: Sun, 30 Jul 2000 17:30:36 +0100 [thread overview]
Message-ID: <001701bffa43$87aedcc0$02a7b6c3@lucid.proweb.net> (raw)
In-Reply-To: <200007301521.QAA06462@pw001.proweb.co.uk>
> It sounds like you typed "aux/listen tcp17013"
> rather than just "aux/listen tcp".
yes it looks like i did
the log now says it's started but .....
drawterm doesn't connect iprint message :
Can't dial tcp!195.182.167.7!17013: connect 195.182.167.7!17013 failed: No
error
Drawterm then crashes with a runtime error
(putting an Abnormal Termination dialog up)
Doing a portscan on donk gets no response from any of the services in
bin/service :
tcp110
tcp13
tcp143
tcp17007
tcp17009
tcp17013
tcp19
tcp21
tcp23
tcp25
tcp513
tcp53
tcp565
tcp567
tcp7
tcp9
So the box is accepting no outside requests for ports
it does answer pings though
it is a stand alone machine doing cpu, auth and kfs
still at least I'm learning
I've not had much time to play today as I'm writing an e-commerce web site
with my other hand
good to see your sunday's aren't wasted
Matt
next parent reply other threads:[~2000-07-30 16:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200007301521.QAA06462@pw001.proweb.co.uk>
2000-07-30 16:30 ` Matt [this message]
[not found] <200007311932.PAA10741@smtp2.fas.harvard.edu>
2000-07-31 22:49 ` Matt
[not found] <200007302230.XAA03260@pw001.proweb.co.uk>
2000-07-31 19:05 ` Matt
2000-07-30 15:20 Russ Cox
-- strict thread matches above, loose matches on Subject: below --
2000-07-30 2:28 [9fans] /sys/lib/pcdist/README Russ Cox
2000-07-30 13:13 ` [9fans] drawterm etc Matt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='001701bffa43$87aedcc0$02a7b6c3@lucid.proweb.net' \
--to=matt@proweb.co.uk \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).