Re: open ports 25/tcp and 110/tcp

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wednesday 03 December 2003 19:39, Antony Stone wrote:
> On Thursday 04 December 2003 12:28 am, Jeffrey Laramie wrote:
> > On Wednesday 03 December 2003 19:14, Michael Gale wrote:
> > > Hello,
> > >
> > > 	Maybe because you are running nmap from a windows box ?
> > >
> > > Have you tried a windows machine ?
> >
> > Yes, and it tasted like chicken.
> >
> >
> >
> > Seriously, that may be a good point. Make sure there isn't anything
> > running on the sending box that might interfere with the test. I've had
> > screwed up nmap tests when the sending box filtered certain ports.
>
> This I can understand, but what puzzles me is that David is saying that
> from the same test machine, doing nmap -sT, and telnet xx.xx.xx.xx 25, are
> giving different results.
>
> nmap -sT does a TCP connect, and telnet does a TCP connect, so how is it
> possible for one to say that the port is open, but the other not to show
> the welcome banner?
>
> Antony.

I don't know. _shrug_ I'd still like to find out what a packet sniffer sees 
during the nmap test.


[Index of Archives]     [Linux Netfilter Development]     [Linux Kernel Networking Development]     [Netem]     [Berkeley Packet Filter]     [Linux Kernel Development]     [Advanced Routing & Traffice Control]     [Bugtraq]

  Powered by Linux