From: "David F. Strauch" <dstrauch@cyberlink.com>
To: netfilter@lists.netfilter.org
Subject: Re: open ports 25/tcp and 110/tcp
Date: Wed, 3 Dec 2003 17:58:03 -0600 [thread overview]
Message-ID: <003d01c3b9f9$4e074380$0201a8c0@OurPC> (raw)
In-Reply-To: 200312032339.21755.Antony@Soft-Solutions.co.uk
Yes, Antony this is the case. I have only one WinXP machine that I am
testing with. I'm testing the external interface eth0 and I have unplugged
eth1 from the hub.
When I nmap -sT -p 25,110 -P0 xx.xx.xx.xx I get the following output form
nmap:
Starting nmap V. 3.00 ( www.insecure.org/nmap )
Interesting ports on (67.153.34.147):
Port State Service
25/tcp open smtp
110/tcp open pop-3
Nmap run completed -- 1 IP address (1 host up) scanned in 1 second
----- Original Message -----
From: "Antony Stone" <Antony@Soft-Solutions.co.uk>
To: <netfilter@lists.netfilter.org>
Sent: Wednesday, December 03, 2003 5:39 PM
Subject: Re: open ports 25/tcp and 110/tcp
> On Wednesday 03 December 2003 11:32 pm, David F. Strauch wrote:
>
> > Antony,
> >
> > I tried telnet from my WinXP machine to both open ports without any
> > responce. I'm hosting neither services on this machine. It will be a
> > gateway machine with a very minimal hardened installation.
>
> Are you saying that from the same machine you did "nmap -sT -F -P0 -O
> xx.xx.xx.xx" and got a report including "SMTP port 25 open" and "POP3 port
> 110 open", and also doing "telnet xx.xx.xx.xx 25" gives no response?
>
> That makes no sense, because nmap -sT means a full TCP connect - the same
as
> the telnet command would do.
>
> Please confirm whether I am understanding correctly that you are doing
both
> these tests from the same machine to the same address and getting
different
> answers?
>
> Antony.
>
> --
> All matter in the Universe can be placed into one of two categories:
>
> 1. Things which need to be fixed.
> 2. Things which need to be fixed once you've had a few minutes to play
with
> them.
>
> Please reply to the
list;
> please don't CC
me.
>
>
>
>
next prev parent reply other threads:[~2003-12-03 23:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-03 22:46 open ports 25/tcp and 110/tcp David F. Strauch
2003-12-03 23:01 ` Antony Stone
2003-12-03 23:15 ` David F. Strauch
2003-12-03 23:23 ` Antony Stone
2003-12-03 23:34 ` David F. Strauch
[not found] ` <002201c3b9f5$c7ee11a0$0201a8c0@OurPC>
2003-12-03 23:39 ` Antony Stone
2003-12-03 23:58 ` David F. Strauch [this message]
2003-12-04 0:08 ` Antony Stone
2003-12-04 0:14 ` Michael Gale
2003-12-04 0:28 ` Jeffrey Laramie
2003-12-04 0:37 ` Michael Gale
2003-12-04 1:14 ` Jeffrey Laramie
2003-12-04 0:39 ` Antony Stone
2003-12-04 1:27 ` Jeffrey Laramie
2003-12-04 3:46 ` David F. Strauch
2003-12-04 0:11 ` Jeffrey Laramie
2003-12-03 23:08 ` Rob Sterenborg
2003-12-03 23:17 ` Antony Stone
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='003d01c3b9f9$4e074380$0201a8c0@OurPC' \
--to=dstrauch@cyberlink.com \
--cc=netfilter@lists.netfilter.org \
/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