API tools faq
paste
Advertisement
matt_mods

ports and there uses

matt_mods
Nov 5th, 2017
155
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 6.80 KB | None | 0 0
raw download clone embed print report
  1. Protocol
  2.  
  3.  
  4. TCP/UDP
  5.  
  6.  
  7. Port Number
  8.  
  9.  
  10. Description
  11.  
  12. File Transfer Protocol (FTP)
  13.  
  14. (RFC 959)
  15.  
  16.  
  17. TCP
  18.  
  19.  
  20. 20/21
  21.  
  22.  
  23. FTP is one of the most commonly used file transfer protocols on the Internet and within private networks. An FTP server can easily be set up with little networking knowledge and provides the ability to easily relocate files from one system to another. FTP control is handled on TCP port 21 and its data transfer can use TCP port 20 as well as dynamic ports depending on the specific configuration.
  24.  
  25. Secure Shell (SSH)
  26.  
  27. (RFC 4250-4256)
  28.  
  29.  
  30. TCP
  31.  
  32.  
  33. 22
  34.  
  35.  
  36. SSH is the primary method used to manage network devices securely at the command level. It is typically used as a secure alternative to Telnet which does not support secure connections.
  37.  
  38. Telnet
  39.  
  40. (RFC 854)
  41.  
  42.  
  43. TCP
  44.  
  45.  
  46. 23
  47.  
  48.  
  49. Telnet is the primary method used to manage network devices at the command level. Unlike SSH which provides a secure connection, Telnet does not, it simply provides a basic unsecured connection. Many lower level network devices support Telnet and not SSH as it required some additional processing. Caution should be used when connecting to a device using Telnet over a public network as the login credentials will be transmitted in the clear.
  50.  
  51. Simple Mail Transfer Protocol (SMTP)
  52.  
  53. (RFC 5321)
  54.  
  55.  
  56. TCP
  57.  
  58.  
  59. 25
  60.  
  61.  
  62. SMTP is used for two primary functions, it is used to transfer mail (email) from source to destination between mail servers and it is used by end users to send email to a mail system.
  63.  
  64. Domain Name System (DNS)
  65.  
  66. (RFC 1034-1035)
  67.  
  68.  
  69. TCP/UDP
  70.  
  71.  
  72. 53
  73.  
  74.  
  75. The DNS is used widely on the public internet and on private networks to translate domain names into IP addresses, typically for network routing. DNS is hieratical with main root servers that contain databases that list the managers of high level Top Level Domains (TLD) (such as .com). These different TLD managers then contain information for the second level domains that are typically used by individual users (for example, cisco.com). A DNS server can also be set up within a private network to private naming services between the hosts of the internal network without being part of the global system.
  76.  
  77. Dynamic Host Configuration Protocol (DHCP)
  78.  
  79. (RFC 2131)
  80.  
  81.  
  82. UDP
  83.  
  84.  
  85. 67/68
  86.  
  87.  
  88. DHCP is used on networks that do not use static IP address assignment (almost all of them). A DHCP server can be set up by an administrator or engineer with a poll of addresses that are available for assignment. When a client device is turned on it can request an IP address from the local DHCP server, if there is an available address in the pool it can be assigned to the device. This assignment is not permanent and expires at a configurable interval; if an address renewal is not requested and the lease expires the address will be put back into the poll for assignment.
  89.  
  90. Trivial File Transfer Protocol (TFTP)
  91.  
  92. (RFC 1350)
  93.  
  94.  
  95. UDP
  96.  
  97.  
  98. 69
  99.  
  100.  
  101. TFTP offers a method of file transfer without the session establishment requirements that FTP uses. Because TFTP uses UDP instead of TCP it has no way of ensuring the file has been properly transferred, the end device must be able to check the file to ensure proper transfer. TFTP is typically used by devices to upgrade software and firmware; this includes Cisco and other network vendors’ equipment.
  102.  
  103. Hypertext Transfer Protocol (HTTP)
  104.  
  105. (RFC 2616)
  106.  
  107.  
  108. TCP
  109.  
  110.  
  111. 80
  112.  
  113.  
  114. HTTP is one of the most commonly used protocols on most networks. HTTP is the main protocol that is used by web browsers and is thus used by any client that uses files located on these servers.
  115.  
  116. Post Office Protocol (POP) version 3
  117.  
  118. (RFC 1939)
  119.  
  120.  
  121. TCP
  122.  
  123.  
  124. 110
  125.  
  126.  
  127. POP version 3 is one of the two main protocols used to retrieve mail from a server. POP was designed to be very simple by allowing a client to retrieve the complete contents of a server mailbox and then deleting the contents from the server.
  128.  
  129. Network Time Protocol (NTP)
  130.  
  131. (RFC 5905)
  132.  
  133.  
  134. UDP
  135.  
  136.  
  137. 123
  138.  
  139.  
  140. One of the most overlooked protocols is NTP. NTP is used to synchronize the devices on the Internet. Even most modern operating systems support NTP as a basis for keeping an accurate clock. The use of NTP is vital on networking systems as it provides an ability to easily interrelate troubles from one device to another as the clocks are precisely accurate.
  141.  
  142. NetBIOS
  143.  
  144. (RFC 1001-1002)
  145.  
  146.  
  147. TCP/UDP
  148.  
  149.  
  150. 137/138/139
  151.  
  152.  
  153. NetBIOS itself is not a protocol but is typically used in combination with IP with the NetBIOS over TCP/IP (NBT) protocol. NBT has long been the central protocol used to interconnect Microsoft Windows machines.
  154.  
  155. Internet Message Access Protocol (IMAP)
  156.  
  157. (RFC 3501)
  158.  
  159.  
  160. TCP
  161.  
  162.  
  163. 143
  164.  
  165.  
  166. IMAP version3 is the second of the main protocols used to retrieve mail from a server. While POP has wider support, IMAP supports a wider array of remote mailbox operations which can be helpful to users.
  167.  
  168. Simple Network Management Protocol (SNMP)
  169.  
  170. (RFC 1901-1908, 3411-3418)
  171.  
  172.  
  173. TCP/UDP
  174.  
  175.  
  176. 161/162
  177.  
  178.  
  179. SNMP is used by network administrators as a method of network management. SNMP has a number of different abilities including the ability to monitor, configure and control network devices. SNMP traps can also be configured on network devices to notify a central server when specific actions are occurring. Typically, these are configured to be used when an alerting condition is happening. In this situation, the device will send a trap to network management stating that an event has occurred and that the device should be looked at further for a source to the event.
  180.  
  181. Border Gateway Protocol (BGP)
  182.  
  183. (RFC 4271)
  184.  
  185.  
  186. TCP
  187.  
  188.  
  189. 179
  190.  
  191.  
  192. BGP version 4 is widely used on the public internet and by Internet Service Providers (ISP) to maintain very large routing tables and traffic processing. BGP is one of the few protocols that have been designed to deal with the astronomically large routing tables that must exist on the public Internet.
  193.  
  194. Lightweight Directory Access Protocol (LDAP)
  195.  
  196. (RFC 4510)
  197.  
  198.  
  199. TCP/UDP
  200.  
  201.  
  202. 389
  203.  
  204.  
  205. LDAP provides a mechanism of accessing and maintaining distributed directory information. LDAP is based on the ITU-T X.500 standard but has been simplified and altered to work over TCP/IP networks.
  206.  
  207. Hypertext Transfer Protocol over SSL/TLS (HTTPS)
  208.  
  209. (RFC 2818)
  210.  
  211.  
  212. TCP
  213.  
  214.  
  215. 443
  216.  
  217.  
  218. HTTPS is used in conjunction with HTTP to provide the same services but doing it using a secure connection which is provided by either SSL or TLS.
  219.  
  220. Lightweight Directory Access Protocol over TLS/SSL (LDAPS)
  221.  
  222. (RFC 4513)
  223.  
  224.  
  225. TCP/UDP
  226.  
  227.  
  228. 636
  229.  
  230.  
  231. Just like HTTPS, LDAPS provides the same function as LDAP but over a secure connection which is provided by either SSL or TLS.
  232.  
  233. FTP over TLS/SSL
  234.  
  235. (RFC 4217)
  236.  
  237.  
  238. TCP
  239.  
  240.  
  241. 989/990
  242.  
  243.  
  244. Again, just like the previous two entries, FTP over TLS/SSL uses the FTP protocol which is then secured using either SSL or TLS.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!