|
[ Home | Contact Me ]
Any Port in a Datastorm
It seems like every day there is a new Internet service that uses some new
set of poorly-documented, unregistered ports. I created this page to gather
together all the information I could find about the ports used by these new
services, for use by firewall administrators and other network monitors.
- "dyn" in the ports field denotes dynamically allocated port(s), usually in
the range >=1024 <=65535
- A name in the ports field (e.g. LDAP) indicates that service is also
required
- A plus sign + in the ports field indicates the service may use a series of
ports starting at the specified one
- An asterisk * in the Notes field indicates that the ports are IANA
registered
When a specific port is registered it is usually assigned for both TCP and
UDP even though only one or the other may be required. Where possible I have
only shown the required ones.
This is not intended to list old, well-documented services such as telnet,
FTP, SMTP etc. You can find these in the IANA
list.
You may contact
me by email with any suggestions or corrections, or post a message to the TCP/IP Ports discussion.
| Service |
TCP |
UDP |
Notes |
| SSH |
22 |
|
Secure Shell * |
| HTTP |
80 |
|
HyperText Transfer Protocol * (e.g. for web browsing). Currently
(2003-07-05) HTTP/1.1 is officially described in RFC 2616. |
| RPC Endpoint Mapper |
135 |
135 |
* registered as "epmap - DCE endpoint resolution". Used by Microsoft
for RPC locator service. See additional
information. |
| LDAP |
389 |
389 |
Lightweight Directory Access Protocol * |
| MS
NetMeeting |
LDAP
or ULP,
dyn >=1024, 1503, H.323
HostCall, MS
ICCP |
dyn >=1024 |
videoconferencing |
| Timbuktu |
1417-1420 |
407 |
remote control * |
| SLP |
427 |
427 |
Service Location Protocol * Used by MacOS. |
| HTTPs |
443 |
|
secure HTTP (SSL) * |
| ULP |
522 |
522 |
User Location Protocol (Microsoft) * |
| AppleTalk Filing Protocol (AFP) |
548 |
548 |
* |
| QuickTime
4 |
RTSP |
RTP-QT4 |
streaming audio, video * |
| RTSP |
554 |
|
Real Time Streaming Protocol *. Currently (2003-07-05) described in RFC 2326. |
| NNTPs |
563 |
|
secure NNTP news (SSL) * |
| Internet Printing Protocol
(IPP) |
631 |
631 |
print remotely to any IPP enabled printer through the Internet * The
Common Unix Printing System (CUPS) is
based on IPP. |
| LDAPs |
636 |
636 |
secure LDAP * (LDAP protocol over TLS/SSL) |
| Doom |
666 |
666 |
network game * |
| Remotely Possible (ControlIT) |
799 |
|
remote control. CA ControlIT
support. |
| SOCKS |
1080 |
|
internet proxy * |
| Lotus Notes Domino |
1352 |
|
* |
| VocalTec Internet Phone |
1490, 6670, 25793 |
22555 |
videoconferencing * |
| Citrix
ICA |
1494, dyn >=1023 |
1604, dyn >=1023 |
remote application access * |
| Virtual Places |
1533 |
|
conferencing *, also see VP
voice |
| Xing
StreamWorks |
|
1558 |
streaming video * |
| Novell
GroupWise (Remote Client) |
1677 |
1677 |
group collaboration * NOTE: Other features of GroupWise use many other
ports. |
| H.323 Host Call |
1720 |
1720 |
H.323 host call * |
| PPTP |
1723 |
|
virtual private network (VPN) * Note PPTP also uses the GRE
protocol.
However Microsoft says in Understanding
PPTP: "PPTP can be used with most firewalls and routers by enabling
traffic destined for port 1723 to be routed through the firewall or
router." |
| MS ICCP |
1731 |
1731 |
audio call control (Microsoft) * |
| MS NetShow |
1755 |
1755, dyn >=1024 <=5000 |
streaming video * |
| MSN
Messenger |
1863 |
|
instant messenging *. NOTE: For file transfer or
voice chat ports and NAT information for Messenger 3 see MS Support
article Q278887.
For Messenger 4 see the detailed document on Windows
Messenger XP |
| Netopia
netOctopus |
1917, 1921 |
1917 |
network management * |
| ICU II |
2000-2003 |
|
videoconferencing. NOTE: security risk on TCP port
50000 |
| iSpQ |
2000-2003 |
|
videoconferencing. Note: support docs are inconsistent on what ports
are required |
| glimpseserver |
2001 |
|
search engine |
| Distributed.Net
RC5/DES |
2064 |
|
distributed computation |
| SoulSeek |
2234, 5534 |
2234, 5534 |
file sharing |
| Netrek |
2592 |
|
network game * |
| squid |
3128 |
3130 |
web proxy cache |
| Windows Remote Desktop Protocol (RDP) |
3389 |
|
* registered as ms-wbt-server. RDP 5.1 is the current version. See
below for more
information. Remote Desktop Web Connection also uses HTTP. |
| Virtual Places Voice Chat |
3450, 8000-9000 |
|
voice chat, also see Virtual
Places |
| Apple iTunes music sharing (DAAP) |
3689 |
3689 |
Digital Audio Access Protocol * |
| Mirabilis ICQ |
dyn >=1024 |
4000 |
locator, chat (note: see newer AOL
ICQ) |
| Blizzard / Battle.net |
4000, 6112-6119 |
4000, 6112-6119 |
network gaming - support
(captured 2001-11-11), proxy and firewall
info |
| Abacast
| 4000-4100, 4500, 9000-9100 |
|
peer-to-peer audio and video streaming. NOTE: This software will
create OUTGOING streams to other users if it can. |
| GlobalChat client,
server |
4020 |
4020 |
chat rooms, used to be called ichat |
| PGPfone |
|
4747 |
secure phone |
| PlayLink |
4747, 4748, 10090 |
6144 |
online games |
| radmin |
4899 |
4899 |
remote control |
| Yahoo Messenger - Voice
Chat |
5000-5001 |
5000-5010 |
voice chat |
| GnomeMeeting |
H.323
HostCall, 30000-30010 |
5000-5003, 5010-5013 |
audio and videoconference. 5000-5003 is RTP and RTCP range for this
app. |
| Yahoo
Messenger - messages |
5050 |
|
messaging. NOTE: It will try ports 5050, 80, any port. |
| SIP |
5060 |
5060 |
Session Initiation Protocol *. For audio and video. Currently
(2003-07-05) see RFCs 3261, 3262, 3263, 3264, 3265 |
| Apple
iChat AV |
|
SIP, RTP-iChatAV |
audio and video conferencing. May also need iChat
local port. |
| Yahoo
Messenger - Webcams |
5100 |
|
video |
| AOL
Instant Messenger (AIM) |
5190 |
5190 |
America OnLine * Also used by Apple iChat (in AIM
compatibility mode). |
| AOL ICQ |
5190, dyn >=1024 |
|
messaging |
| AOL |
5190-5193 |
5190-5193 |
America OnLine * |
| iChat local traffic |
5298 |
5298 |
Some Rendezvous thing. |
| Multicast DNS |
5353 |
5353 |
* Mac
OS X 10.2: About Multicast DNS. Related to Zeroconf which Apple has implemented
as Rendezvous.
(Note: the regular Domain Name Service port is 53.) |
| Dialpad.com |
5354, 7175, 8680-8890, 9000, 9450-9460 |
dyn >=1024 |
telephony |
| HotLine |
5500-5503 |
|
peer-to-peer filesharing. |
| pcAnywhere |
5631 |
5632 |
remote control * |
| eShare Chat Server |
5760 |
|
|
| eShare Web Tour |
5761 |
|
|
| eShare Admin Server |
5764 |
|
|
| VNC |
5800+, 5900+ |
|
remote control |
| GNUtella |
6346, 6347 |
6346, 6347 |
peer-to-peer file sharing * |
| Netscape Conference |
H.323
HostCall, 6498, 6502 |
2327 |
audioconferencing |
| Danware
NetOp Remote Control |
6502 |
6502 |
remote control |
| common IRC |
6665-6669 |
|
Internet Relay Chat * |
| Net2Phone CommCenter
| selected |
6801, selected |
telephony, admin should select one TCP and UDP port in the range
1-3000. Same ports are used by Yahoo
Messenger - PC-to-Phone. |
| VDOLive |
7000 |
user-specified |
streaming video |
| RTP-QT4 |
|
6970-6999 |
Realtime Transport Protocol. (These ports are specifically for the
Apple QT4 version.) |
| Real Audio &
Video |
RTSP,
7070 |
6970-7170 |
streaming audio and video |
| CU-SeeMe, Enhanced CUSM |
7648, 7649, LDAP |
7648-7652, 24032 |
videoconferencing |
| common HTTP |
8000, 8001, 8080 |
|
|
| Apache JServ Protocol v12 (ajp12) |
8007 |
8007 |
(default port) See Workers
HowTo for config info. |
| Apache
JServ Protocol v13 (ajp13) |
8009 |
8009 |
(default port) e.g. Apache mod_jk Tomcat connector using ajp13. See Workers
HowTo for config info. |
| iVisit |
|
9943, 9945, 56768 |
videoconferencing |
| The Palace |
9992-9997 |
9992-9997 |
chat environment * |
| common Palace |
9998 |
|
chat environment |
| Yahoo
Games |
11999 |
|
network games |
| RTP-iChatAV |
|
16384-16403 |
Used by Apple iChat AV. |
| RTP |
|
16384-32767 |
Realtime Transport Protocol. RTP in general is described in RFC 1889. This range
is not registered (it never could be, being so broad) but it seems to be
somewhat common. See Are there
specific ports assigned to RTP? |
| Palm Computing Network Hotsync |
14237 |
14238 |
data synchronization |
| Liquid
Audio |
18888 |
|
streaming audio |
| FreeTel |
|
21300-21303 |
audioconferencing |
| VocalTec Internet Conference |
22555 |
22555 |
audio & document conferencing * |
| Quake |
26000 |
26000 |
network game * |
| MSN
Gaming Zone |
28800-29000 |
28800-29000 |
network gaming |
| Sygate
Manager |
|
39213 |
|
| DirectX
Gaming |
47624, 2300-2400 |
47624, 2300-2400 |
many network games |
After examining Napster, I decided it was such a complex protocol that it
deserved its own section. The first thing to be aware of is that there are two
versions of Napster. The "original" flavor is what most people will be
interested in. This is the full music file-sharing service. This original
service provided by Napster.com has now
been shut down. Napster.com will be providing a new service with much more
controlled music sharing. However, the original protocol lives on, and the
protocol has been analyzed so that people could write compatible applications
for many different operating systems.
There is information on the protocol (and how to get it through your
firewall) from:
Here is a summary of the TCP ports it uses. I have put the notation (primary)
after the main port, if more than one port is listed.
- metaserver / redirector: 8875
- directory servers: 4444, 5555, 6666, 7777, 8888 (primary)
- client: 6600 to 6699 (primary)
PalTalk is another messy service that uses many ports, more than I want to
summarize here. Visit their support page: Getting
PalTalk To Work With Your Firewall Or Network.
Apple released QuickTime 4 some time ago. I am unsure of the status of their
older QuickTime Conferencing (MovieTalk) protocol. All of the applications that
supported it (Connectix VideoPhone, Apple VideoPhone, Netscape CoolTalk,
QuickTime TV) are no longer supported and the QuickTime Conferencing website is
gone.
Official TCP/IP Port Assignments
Also note, although you will sometimes see mention of RFC 1700 "Assigned Numbers"
(dated October 1994) it was long ago obsoleted by the official IANA
list. Do not use RFC 1700 as a reference. This fact is now
officially documented by RFC
3232 "Assigned Numbers: RFC 1700 is Replaced by an On-line Database".
Network Sorcery lists the IANA TCP/UDP
Ports with links to pages describing some protocols in detail, as part of
its incredibly useful RFC
Sourcebook.
These cover registered, unregistered, and trojan ports - note that many ports
have legitimate, required uses, even though people have also used them as trojan
ports.
The IBM RedBooks are an amazing resource for many technical topics. They have
a TCP/IP
Tutorial and Technical Overview available as HTML or 7.7 MB PDF.
Cisco also provides excellent information online. Internet
Protocols is just one section of their Internetworking
Technology Handbook.
There is information on IP (the protocol on which TCP and UDP are built) in
Internet Core Protocols: The Definitive Guide Sample
Chapter 2: The Internet Protocol [IP].
As indicated in the RDP section
above, this protocol uses a registered TCP port. It is used for XP Pro Remote
Desktop and XP Remote Assistance (read Administering
Remote Assistance for a very good overview of firewall, NAT and blocking
issues). Also used for WinNT4 Terminal
Server, Win2000 Terminal
Services, and Win .NET Server 2003 Terminal
Server.
In some cases, Microsoft uses port 135 as an RPC Endpoint Mapper. Runs as
RPCSS on (some versions of?) Windows. This is a sort of "RPC directory" service
which can be used to lookup what ports other services are running on. For some
additional information, see Windows
2000 Network Architecture: Remote Procedure Call and NT
Gatekeeper: RPC and Firewall Configuration.
MS-RPC on port 135 is required for some Exchange Server and Active Directory
communications. See e.g. TCP Ports
and Microsoft Exchange: In-depth Discussion and Restricting
Active Directory Replication Traffic to a Specific Port. However this
port also poses a security risk, as indicated in the NET
SEND section of my broadband security page.
UPDATE 2003-08-13: Also see the Blaster
Worm section for information about this additional security risk.
Additional information:
A related note: the Messenger Service that runs at the Windows SERVICE level
is different from the Windows or MSN Messenger application. For
information about the Messenger APPLICATION see
Mac
OpenDoor (makers of DoorStop) have a nice list of MacOS-related
ports, with hyperlinks to relevant information.
Apple support has provided a list of "Well Known" TCP
and UDP Ports Used By Apple Software Products.
Novell (NetWare)
TCP/IP
Port Numbers used by Novell Products
IP Telephony / Voice over IP (VoIP) / H.323 / SIP /
RTP
Some applications that use H.323 include: ohphone, ohphoneX,
...
Getting H.323 audio/video conferencing through firewalls is particularly
problematic. I have used Google cache to rescue an Intel document The
Problems and Pitfalls of Getting H.323 Safely Through Firewalls. Note in
particular that RTCP (Real Time Control Protocol) has no fixed port, an RTCP
session is paired with an RTP session, if you have an RTP stream on even
numbered UDP port x, RTCP is on x + 1.
General
The white paper Cisco
PIX Firewall and Stateful Firewall Security contains some useful information
about the ports and connection protocols for VDOnet, CU-SeeMe, and RealAudio.
Ed Bott's article Block
those ports! contains some useful information, and also a kind review of
this web page. He also links to my page from the about.com Windows and Internet
Security Information page on TCP and UDP
ports.
You can check out Internet
Firewalls: Frequently Asked Questions. As of this writing it was last
updated 2000/12/01 but it still has lots of good information.
You may also find useful a list of ports specified in ipmasq format (actually it gives you
sets of rules you can use with either ipchains or ipfwadm).
NetGear's
Applications Port List lists a lot of games.
By popular request: a page on Blocking Chat Programs.
More and more good resources are becoming available, particularly for people
with home networks. If you haven't found what you were looking for here, you can
try:
- PracticallyNetworked:
- HomeNetHelp:
Note that certain services such as IPSec and Microsoft's PPTP use non-TCP/UDP
protocols so they may be more complicated to use. In particular, PPTP uses GRE
(protocol 47) and IPSec uses ESP (protocol 50) and AH (protocol 51). Protocol
numbers are not the same as port numbers. IANA maintains the Assigned Internet
Protocol Numbers.
Those of you concerned with Internet security may wish to also check out my
companion page, Trojan TCP/IP
Ports for a list of ports used by trojan horse and backdoor programs. Also I
have a link to firewall
books there (including a free book).
If you have questions, comments or suggestions specifically about this page
or TCP/IP ports then you can email me or use my QuickTopic: Discuss TCP/IP
Ports.
For firewall questions I suggest the USENET group comp.security.firewalls via
groups.google.com
or your newsreader.
If your question is Microsoft-specific, you may want to try the USENET microsoft.public
groups, in particular:
Copyright 1996-2003 Richard Akerman. All rights reserved. No
mirroring without prior written consent.
If you wish to mirror this page, contact me by email. The requirements are:
- The page content including my copyright notice remains intact
- The official permanent link to this page is
http://www.akerman.ca/port-table.html
- The date of the mirror and the frequency of updates must be indicated
- Use metatags or robots.txt to prevent your mirror from being indexed by
search engines
- There can be no other copyright notices or advertising/promotion
of any kind on the mirror page
[ Home | Contact Me ]
|