I run a website (www.newzbot.com) that lists publicly accessible USENET news servers. To populate this site, I go out and connect to various hosts looking for USENET services on port 119 (NNTP) and 563 (NNTP over SSL); I then put the results in a database and publish them in various formats.
Conceptually, this works much like a web spider which talk to hosts to determine if they offer web services, and if so, "spiders" the pages for indexing, except mine is more of a meta-search engine, not offering the USENET news itself, but where to find it.
Furthermore, if your firewalling software can detect a so-called "stealth scan" -- such as SYNs w/ no ACK -- this almost (almost!) always indicates a portscan.
In general, there have been few NNTP-related security problems, aside from a bad one a couple years back that affected Unix boxes running INN, so connections to port 119 or 563 usually indicate a probe to determine if a public news server is available, but little else.
200 avalon.jammed.com NNTPcache server V1.0.6 Sep 1 1997 ready (posting ok).
However, when a news server refuses a connection from a client, it will issue a "500 message", a-la
502 You have no permission to talk. Goodbye.
If my robot connects to a server it gets anything other than a 200 message, I automatically add it to an exclude database, which means I will never scan it again. This way I don't bang on people's news servers if they've told me to go away -- again, very similar to the 'robots.txt' file that websites put up to keep (polite) spiders at bay.
However -- if your host is firewalled, then this "automatic exclusion" won't work, since they'll just appear to be offline. Most firewalls (personal and otherwise) will silently drop packets, as opposed to accepting the connection, saying "Go away", and disconnecting. They are, from a network's perspective, unreachable.
-O
option to
"fingerprint"
the OS.
These probes will almost always come from the machine 'flagstaff.jammed.com'.
Note that nmap is only used for OS detection; as newzbot is only interested in ports 119 and 563, there is no need for it to identify every listening service on a host ("portscanning"). Newzbot only performs OS detection on hosts that are public news servers; it will not bother your host if it is unreachable or private.
Keep in mind that I may still connect to your machine or network. I may ping you, I may try to visit your web site, or I may try to send you mail -- particularly if you send me mail about this issue.