Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Port 81 - What is it good for ?

1,828 views
Skip to first unread message

Rolf Schmidt

unread,
Apr 27, 2001, 9:06:34 AM4/27/01
to
Hello all,

Many times when users on my LAN point there browsers to some pages they
should not point their browsers to (...) my firewall will report large
quantities of rejected packets on port 81. What's going on there?

Thank you

Rolf Schmidt

Thinker

unread,
Apr 27, 2001, 1:07:07 PM4/27/01
to
Don't know if this is the case but you can check here:

http://www.simovits.com/nyheter9902.html

"Rolf Schmidt" <schmidtro...@gmx.net> wrote in message
news:3AE96EDA...@gmx.net...

RDlhnt

unread,
Apr 27, 2001, 5:16:33 PM4/27/01
to
here's what my database on port numbers tells me:

hosts2-ns 81/tcp HOSTS2 Name Server
hosts2-ns 81/udp HOSTS2 Name Server

Felix Tilley

unread,
Apr 28, 2001, 11:20:01 AM4/28/01
to
In article <3AE96EDA...@gmx.net>, "Rolf Schmidt"
<schmidtro...@gmx.net> wrote:

From RFC 1700, allegedly obsolete:

hosts2-ns 81/tcp HOSTS2 Name Server
hosts2-ns 81/udp HOSTS2 Name Server


Felix Tilley

Rolf Schmidt

unread,
Apr 30, 2001, 2:24:16 AM4/30/01
to
Thank you for answering my question. Unfortunatelly, this didn't solve
my problem, as "hosts2-ns" doesn't mean much to me. I just was
wondering, if anyone has remarked similar behaviour.
To give more detail: The connections want to go to some
"sextracker"-sites. Why are they doing this? Is it just a gift to me to
show me who is violating our internet-policy or anything other, maybe
serious?

Regards

Rolf

Daniel Crichton

unread,
May 4, 2001, 4:53:55 AM5/4/01
to
"Rolf Schmidt" <schmidtro...@gmx.net> wrote in message
news:3AE96EDA...@gmx.net...

A lot of sites appear to run extra web servers on ports like 81, 8080, and
8000. Sometimes this is caused by run different web server platforms on the
same OS - eg. IIS on port 80 and Apache on 81 on a Windows server, so that
the sites can use features from both web servers without having the run
multiple servers. Although port 80 is the default HTTP port you can run it
on any port you like (as with almost any TCP/IP software), and some people
do.

Dan


James T. Dennis

unread,
May 9, 2001, 6:41:43 PM5/9/01
to
Rolf Schmidt <schmidtro...@gmx.net> wrote:

> Hello all,

> Thank you
> Rolf Schmidt

The IANA designation for this port is basically completely unused
(as far as I can tell). However Cobalt used it for their administrative
web server. Possibly some crackers are out there looking for vulnerable
Cobalts.

Of course there could be many other ad hoc uses for this port,
and script kiddies may be looking for many things thereon. It would
be SO NICE if vendors and developers would start using tcpmux
instead of arbitrarily choosing ad hoc ports. (Under tcpmux the
TCP client would connect to port 1 and request a service by name. A
tcpmux enhanced inetd would then launch the appropriate service ---
theoretically a really good design could pass the open socket to
a standalone server).

Alas, there hasn't been much activity in this standard.


0 new messages