Well-Known TCP Port Numbers 6

[compgirlfhredi]

Well-Known TCP Port Numbers

In TCP/IP and UDP networks, a port is an endpoint to a logical connection and the way a client program specifies a specific server program on a computer in a network. Some ports have numbers that are preassigned to them by the IANA, and these are known as well-known ports (specified in RFC 1700). Port numbers range from 0 to 65536, but only ports numbers 0 to 1024 are reserved for privileged services and designated as well-known ports. This list of well-known port numbers specifies the port used by the server process as its contact port.
Port Number Description
1 TCP Port Service Multiplexer (TCPMUX)
5 Remote Job Entry (RJE)
7 ECHO
18 Message Send Protocol (MSP)
20 FTP -- Data
21 FTP -- Control
22 SSH Remote Login Protocol
23 Telnet
25 Simple Mail Transfer Protocol (SMTP)
29 MSG ICP
37 Time
42 Host Name Server (Nameserv)
43 WhoIs
49 Login Host Protocol (Login)
53 Domain Name System (DNS)
69 Trivial File Transfer Protocol (TFTP)
70 Gopher Services
79 Finger
80 HTTP
103 X.400 Standard
108 SNA Gateway Access Server
109 POP2
110 POP3
115 Simple File Transfer Protocol (SFTP)
118 SQL Services
119 Newsgroup (NNTP)
137 NetBIOS Name Service
139 NetBIOS Datagram Service
143 Interim Mail Access Protocol (IMAP)
150 NetBIOS Session Service
156 SQL Server
161 SNMP
179 Border Gateway Protocol (BGP)
190 Gateway Access Control Protocol (GACP)
194 Internet Relay Chat (IRC)
197 Directory Location Service (DLS)
389 Lightweight Directory Access Protocol (LDAP)
396 Novell Netware over IP
443 HTTPS
444 Simple Network Paging Protocol (SNPP)
445 Microsoft-DS
458 Apple QuickTime
546 DHCP Client
547 DHCP Server
563 SNEWS
569 MSN
1080 Socks

 

[iSeriesCodePoet]

You need a star for this info, however, you should have posted a link to a page that has a more complete list.

iSeriesCodePoet
iSeries Programmer/Lawson Software Administrator

http://www.koldark.net

See my progress to converting to linux.

http://linux.koldark.net

 

[compgirlfhredi]

These are the only "well-known' ports I know of. Guess I should have stated "well-known by ME". sorry. Does anyone know of such a page?

 

[compgirlfhredi]

OH! and Thank You!!!

 

[smah]

How about this one:

http://www.iana.org/assignments/port-numbers

 

[GlenJohnson]

Here's a star for both of you, but why didn't you post this in the TCP/IP forum as well? (Or did I miss it?) Good going either way.



Glen A. Johnson
Johnson Computer Consulting

http://www.johnsoncomputers.us

"The best fire does not flare up the soonest."
George Eliot (1819-1880); Englist novelist.

Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884

 

[GlenJohnson]

Oh, FYI.

thread96-371090

Glen A. Johnson
Johnson Computer Consulting

http://www.johnsoncomputers.us

"The best fire does not flare up the soonest."
George Eliot (1819-1880); Englist novelist.

Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884

 

[iSeriesCodePoet]

This should be in a FAQ.

iSeriesCodePoet
iSeries Programmer/Lawson Software Administrator

http://www.koldark.net

See my progress to converting to linux.

http://linux.koldark.net

 

[compgirlfhredi]

Thank you everyone, I really thought this MAY come in handy for a FEW users, but I am finding a LOT of Q's out there about ports and such. For those concerned about Blaster and such...
(Quote)
I had to deal with one machine that had the RPC service knocked cold by the worm, but no actual infestations of the Blaster payload. The victim was a Windows 2000 box serving as a router for a small network, and subject to dynamic IP addressing, so I couldn't get the box patched until I was able to obtain the current address. Even an RRAS box using NAT is wide open to attack unless packets are specifically being filtered in order to stop all processing of traffic on affected ports, not just routing. The port numbers relevant to Blaster are as follows:

TCP:
135
139
445
593
4444
UDP:
69
135
137
138
This is a shining example of why the Windows Update concept isn't well thought out on a large scale. When a major incident like this occurs, many users actually can't obtain patches in a timely manner due to the overload. I literally could not apply critical updates to two servers yesterday, although I had already manually downloaded and installed the RPC patch that protects against Blaster. The majority of users don't know that a manual update is available or where to obtain it, so they simply try the update later... perhaps too late.

Right now, you occupy a point where three lines reach across the expanse of time and space and intersect only there, and that you and only you possess.

 

[Moonrsr]

I have read some of his/her Tips in the TCP\IP forum as well. He/She should put this and the webpages in an FAQ. Could solve a lot of time saving and head-banging!