TCP UDP Ports: Difference between revisions
Jump to navigation
Jump to search
m (Update table formatting) |
(Added refs) |
||
| Line 27: | Line 27: | ||
| 143 || TCP || [[Acronyms#I|IMAP]] | | 143 || TCP || [[Acronyms#I|IMAP]] | ||
|- | |- | ||
| 161 || UDP | | 161 || UDP <ref name="NormUDP" /> || [[Acronyms#S|SNMP]] || Gets (polling), initiated to managed device | ||
|- | |- | ||
| 162 || UDP | | 162 || UDP <ref name="NormUDP" /> || [[Acronyms#S|SNMP]] || Traps, initiated from managed device | ||
|- | |- | ||
| 389 || TCP || [[Acronyms#L|LDAP]] | | 389 || TCP || [[Acronyms#L|LDAP]] | ||
| Line 37: | Line 37: | ||
| 445 || TCP || [[Acronyms#S|SMB]] | | 445 || TCP || [[Acronyms#S|SMB]] | ||
|- | |- | ||
| 514 || UDP | | 514 || UDP <ref name="NormUDP" /> || Syslog | ||
|- | |- | ||
| 903 || TCP || VMware || [[Acronyms#V|VM]] remote console on ESX host | | 903 || TCP || VMware || [[Acronyms#V|VM]] remote console on ESX host | ||
|- | |- | ||
| 989 || TCP || [[Acronyms#F|FTPS]] || [[Acronyms#F|FTP]] data over [[Acronyms#S|SSL]] or [[Acronyms#T|TLS]] | | 989 || TCP || [[Acronyms#F|FTPS]] <ref name="FTPS" /> || [[Acronyms#F|FTP]] data over [[Acronyms#S|SSL]] or [[Acronyms#T|TLS]] | ||
|- | |- | ||
| 990 || TCP || [[Acronyms#F|FTPS]] || [[Acronyms#F|FTP]] control over [[Acronyms#S|SSL]] or [[Acronyms#T|TLS]] | | 990 || TCP || [[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]] | ||
| Line 62: | Line 62: | ||
|} | |} | ||
<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</ref> | |||
</references> | |||
Revision as of 22:47, 6 May 2012
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
| 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 | |
| 67 | UDP | DHCP | |
| 80 | TCP | HTTP | |
| 110 | TCP | POP3 | |
| 123 | TCP | 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 | |
| 443 | TCP | HTTPS | HTTP over SSL or TLS |
| 445 | TCP | SMB | |
| 514 | UDP [1] | Syslog | |
| 903 | TCP | VMware | VM remote console on ESX host |
| 989 | TCP | FTPS [2] | FTP data over SSL or TLS |
| 990 | TCP | FTPS [2] | FTP control over SSL or TLS |
| 993 | TCP | IMAP | Over SSL |
| 1433 | TCP | MS SQL | |
| 3260 | TCP | iSCSI | |
| 3306 | TCP | MySQL | |
| 3389 | TCP | RDP | |
| 5900 | TCP | VNC | |
| 6501 | TCP | VMware | Auto Deploy |
| 6502 | TCP | VMware | Auto Deploy |
- ↑ 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.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