TCP UDP Ports: Difference between revisions

From vwiki
Jump to navigation Jump to search
(Initial draft)
 
m (Updated FTP note)
 
(5 intermediate revisions by the same user not shown)
Line 1: Line 1:
Some common TCP and UDP port numbers,  
Some common TCP and UDP port numbers, for a more complete list see
* http://www.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers
* http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xml


{|cellpadding="4" cellspacing="0" border="1"
{|class="vwikitable"
|- style="background-color:#bbddff;"
|-  
! Port !! Transport !! Application        !! Notes / Comments   
! Port !! Transport !! Application        !! Notes / Comments   
|-
|-
Line 11: Line 13:
| 22  || TCP      || [[Acronyms#S|SSH]]   
| 22  || TCP      || [[Acronyms#S|SSH]]   
|-
|-
| 23  || TCP      || Telnet
| 23  || TCP      || [http://www.wikipedia.org/wiki/Telnet Telnet]
|-
|-
| 25  || TCP      || [[Acronyms#S|SMTP]]
| 25  || TCP      || [[Acronyms#S|SMTP]]
Line 17: Line 19:
| 53  || UDP      || [[Acronyms#D|DNS]]
| 53  || UDP      || [[Acronyms#D|DNS]]
|-
|-
| 67   || UDP      || [[Acronyms#D|DHCP]]
| 68   || UDP      || [[Acronyms#D|DHCP]]
|-
|-
| 80  || TCP      || HTTP
| 80  || TCP      || [[Acronyms#H|HTTP]]
|-
|-
| 110  || TCP      || POP3
| 110  || TCP      || POP3
|-
|-
| 123  || TCP       || NTP
| 123  || UDP       || [[Acronyms#N|NTP]]
|-
|-
| 143  || TCP      || [[Acronyms#I|IMAP]]
| 143  || TCP      || [[Acronyms#I|IMAP]]
|-
|-
| 161  || UDP       || [[Acronyms#S|SNMP]] || Gets (polling)  
| 161  || UDP <ref name="NormUDP" />    || [[Acronyms#S|SNMP]] || Gets (polling), initiated to managed device
|-
|-
| 162  || UDP       || [[Acronyms#S|SNMP]] || Traps
| 162  || UDP <ref name="NormUDP" />    || [[Acronyms#S|SNMP]] || Traps, initiated from managed device
|-
|-
| 389  || TCP      || [[Acronyms#L|LDAP]]
| 389  || TCP      || [[Acronyms#L|LDAP]]
|-
|-
| 443  || UDP       || HTTPS               || HTTP over SSL or TLS
| 427  || UDP/TCP  || [[Acronyms#C|CIM]] [[Acronyms#S|SLP]] ||
|-
| 443  || TCP       || [[Acronyms#H|HTTPS]] || [[Acronyms#H|HTTP]] over [[Acronyms#S|SSL]] or [[Acronyms#T|TLS]]
|-
|-
| 445  || TCP      || [[Acronyms#S|SMB]]
| 445  || TCP      || [[Acronyms#S|SMB]]
|-
|-
| 903  || TCP      || VMware              || VM remote console on ESX host
| 514  || UDP <ref name="NormUDP" />    || Syslog
|-
| 902  || TCP      || VMware              || [[Acronyms#V|VM]] remote console on ESX4 and above hosts
|-
| 903  || TCP      || VMware              || [[Acronyms#V|VM]] remote console on ESX3 hosts
|-
| 989  || TCP      || Implicit [[Acronyms#F|FTPS]] <ref name="FTPS" /> || [[Acronyms#F|FTP]] data over [[Acronyms#S|SSL]] or [[Acronyms#T|TLS]]
|-
| 990  || TCP      || Implicit [[Acronyms#F|FTPS]] <ref name="FTPS" /> || [[Acronyms#F|FTP]] control over [[Acronyms#S|SSL]] or [[Acronyms#T|TLS]]
|-
|-
| 993  || TCP      || [[Acronyms#I|IMAP]] || Over [[Acronyms#S|SSL]]
| 993  || TCP      || [[Acronyms#I|IMAP]] || Over [[Acronyms#S|SSL]]
|-
|-
| 1433 || TCP      || MS SQL
| 1433 || TCP      || MS SQL
|-
| 2049 || UDP/TCP  || [[Acronyms#N|NFS]] Client
|-
|-
| 3260 || TCP      || iSCSI     
| 3260 || TCP      || iSCSI     
|-
|-
| 3306 || TCP      || MySQL  
| 3306 || TCP      || [http://www.mysql.com/ MySQL]
|-
|-
| 5900 || TCP      || VNC   
| 3389 || TCP      || [[Acronyms#R|RDP]]
|-
| 5988 || TCP      || [[Acronyms#C|CIM]]
|-
| 5900 || TCP      || [[Acronyms#V|VNC]]  
|-
|-
| 6501 || TCP      || VMware    || Auto Deploy  
| 6501 || TCP      || VMware    || Auto Deploy  
Line 53: Line 71:
| 6502 || TCP      || VMware    || Auto Deploy
| 6502 || TCP      || VMware    || Auto Deploy
|}
|}
<references>
<ref name="NormUDP">UDP is the normal transport used for this protocol, but TCP can be used if you really want to (and your applications support it). In general there is good reason to use UDP over TCP, and you should leave well alone!</ref>
<ref name="FTPS">Whilst FTPS can use different ports to standard FTP, this is not necessary, and FTP servers are normally capable of accepting secure connections without using different TCP ports.  Explicit FTPS uses the standard FTP ports and the client and server negotiate secure communications. Implicit FTPS uses different ports.  Be aware that some firewalls are incapable of tracking explicit FTPS when it moves to use high ports for data transfer.</ref>
</references>
[[Category:Networking]]

Latest revision as of 08:54, 4 December 2013

Some common TCP and UDP port numbers, for a more complete list see

Port Transport Application Notes / Comments
20 TCP FTP Data transfer
21 TCP FTP Control
22 TCP SSH
23 TCP Telnet
25 TCP SMTP
53 UDP DNS
68 UDP DHCP
80 TCP HTTP
110 TCP POP3
123 UDP NTP
143 TCP IMAP
161 UDP [1] SNMP Gets (polling), initiated to managed device
162 UDP [1] SNMP Traps, initiated from managed device
389 TCP LDAP
427 UDP/TCP CIM SLP
443 TCP HTTPS HTTP over SSL or TLS
445 TCP SMB
514 UDP [1] Syslog
902 TCP VMware VM remote console on ESX4 and above hosts
903 TCP VMware VM remote console on ESX3 hosts
989 TCP Implicit FTPS [2] FTP data over SSL or TLS
990 TCP Implicit FTPS [2] FTP control over SSL or TLS
993 TCP IMAP Over SSL
1433 TCP MS SQL
2049 UDP/TCP NFS Client
3260 TCP iSCSI
3306 TCP MySQL
3389 TCP RDP
5988 TCP CIM
5900 TCP VNC
6501 TCP VMware Auto Deploy
6502 TCP VMware Auto Deploy
  1. ↑ 1.0 1.1 1.2 UDP is the normal transport used for this protocol, but TCP can be used if you really want to (and your applications support it). In general there is good reason to use UDP over TCP, and you should leave well alone!
  2. ↑ 2.0 2.1 Whilst FTPS can use different ports to standard FTP, this is not necessary, and FTP servers are normally capable of accepting secure connections without using different TCP ports. Explicit FTPS uses the standard FTP ports and the client and server negotiate secure communications. Implicit FTPS uses different ports. Be aware that some firewalls are incapable of tracking explicit FTPS when it moves to use high ports for data transfer.
Retrieved from ‘http://vwiki.co.uk/index.php?title=TCP_UDP_Ports&oldid=2409’