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

unregistered TCP/UDP ports

154 views
Skip to first unread message

erik

unread,
Sep 4, 2008, 3:32:34 AM9/4/08
to
I see traffic on my network to a number of unregistered TCP/UDP ports. Where
can I find a list with possible protocols that are using these ports (1535,
4889 and 8092)?


Lars Christensen

unread,
Sep 4, 2008, 4:54:39 AM9/4/08
to
"erik" <erik.va...@teleatlas.com> wrote in
news:48bf8f12$0$2864$ba62...@news.skynet.be:

> I see traffic on my network to a number of unregistered TCP/UDP ports.
> Where can I find a list with possible protocols that are using these
> ports (1535, 4889 and 8092)?
>

Try

http://www.google.co.uk/search?hl=en&q=udp+tcp+port+1535&meta=
http://www.google.co.uk/search?hl=en&q=udp+tcp+port+4889&meta=
http://www.google.co.uk/search?hl=en&q=udp+tcp+port+8092&meta=

Regards,
Lars Christensen

alexd

unread,
Sep 4, 2008, 1:10:00 PM9/4/08
to
On Thu, 04 Sep 2008 09:32:34 +0200, erik wrote:

> Where can I find a list with possible protocols that are using these
> ports (1535, 4889 and 8092)?

Are these source or destination ports?

--
<http://ale.cx/> (AIM:troffasky) (UnSoEs...@ale.cx)
18:09:30 up 54 days, 20:47, 3 users, load average: 0.28, 0.24, 0.16
They call me titless because I have no tits

Scott Perry

unread,
Sep 4, 2008, 9:19:02 AM9/4/08
to
The Internet Assigned Numbers Authority (IANA) is responsible for official
assignment of a TCP or UDP port to a known application. That does not mean
that any software designer could create a program to use any unregistered
TCP or UDP port that they want.

There is a Wikipedia listing for common used TCP and UDP service ports:
http://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers

I did not easily find information about the three port numbers which you
listed. That leads me to believe that they are not commonly associated with
any particular application or program. Also keep in mind that only the
destination TCP or UDP port number is the relevant portion, not the source
port number.

-----
Scott Perry
Indianapolis, IN
-----

"Lars Christensen" <you-dont-...@your-face.ddd> wrote in message
news:Xns9B0F6EEC6F...@62.243.74.163...

erik

unread,
Sep 5, 2008, 3:40:00 AM9/5/08
to
It are destination ports I think.


"alexd" <trof...@hotmail.com> wrote in message
news:48c01668$0$515$bed6...@news.gradwell.net...

Tilman Schmidt

unread,
Sep 5, 2008, 9:21:27 AM9/5/08
to
erik schrieb:

> I see traffic on my network to a number of unregistered TCP/UDP ports. Where
> can I find a list with possible protocols that are using these ports (1535,
> 4889 and 8092)?

Strictly speaking, every protocol is possible on every port. In order to
find out for sure what it is you'll have to look on the destination machine
what service is listening on the port. The picture is further complicated
by protocols that allocate ports dynamically.

Of course there are typical services for many ports. I have in the past had
good results looking up port numbers on the SANS Internet Storm Center's
"PortDetails" page at http://isc.sans.org/port.html. The ports you list,
however, didn't turn up anything interesting there.

HTH
T.

--
Please excuse my bad English/German/French/Greek/Cantonese/Klingon/...

alexd

unread,
Sep 5, 2008, 11:25:18 AM9/5/08
to
On Fri, 05 Sep 2008 09:40:00 +0200, erik wrote:

> It are destination ports I think.

OK. Source ports are effectively irrelevant. If you've got OS-level
access to either end, you can find out what process or service is using
the port. On linux and friends, 'lsof -i -n -P' will list processes and
port numbers [rather than service names], on Windows 'netstat -ban -p IP'
seems to do the job. Failing that, you could run Wireshark and literally
look at the content of the packets.

--
<http://ale.cx/> (AIM:troffasky) (UnSoEs...@ale.cx)

16:20:03 up 55 days, 18:58, 3 users, load average: 0.11, 0.06, 0.05

0 new messages