Aug 01, 2019
Nov 05, 2019 PostgreSQL: Could not connect to server: TCP/IP If indeed the challenge is port 5432 as you suspect, you can try to start postgres on another port say 5433 and see what happens. For those, whose database server is not running at all, this solution worked for me, after reading the official PostgreSQL-9.6.16 documentation. TCPやUDPにおけるポート番号の一覧 - Wikipedia
Xbox One (LIVE) ports: 3074 TCP/UDP, 53 TCP/UDP, 80 TCP, 88 UDP, 500 UDP, 3544 UDP, 4500 UDP isakmp_sub_print in tcpdump 3.6 through 3.7.1 allows remote attackers to cause a denial of service (CPU consumption) via a certain malformed ISAKMP packet to UDP port 500, which causes tcpdump to enter an infinite loop. References: [CVE-2003-0108]
List of Common Network Port Numbers – Utilize Windows Port Service name Transport protocol 20, 21 File Transfer Protocol (FTP) TCP 22 Secure Shell (SSH) TCP and UDP 23 Telnet TCP 25 Simple Mail Transfer Protocol (SMTP) TCP 50, 51 IPSec 53 Domain Name System (DNS) TCP and UDP 67, 68 Dynamic Host Configuration Protocol (DHCP) UDP 69 Trivial File Transfer Protocol (TFTP) UDP 80 Overview of common TCP and UDP Default Ports The port 53 waits for requests from DHCP to transfer the data over the network. It operates on the Application Layer of the TCP/IP Model. TCP protocol is used by the Zone Transfer function of the DNS server. Once the connection is established, the zone data will be sent by the server using the TCP 53 port.
What do the port numbers in an IPSEC-ESP session represent?
Well known SCTP, TCP and UDP ports, 0 through 999 Port Transport Protocol; 100 : 101: TCP: HOSTNAME.: 102: TCP: TP0 over TCP.: 103: TCP, UDP: Genesis Point-to-Point Trans Net. 104 : ACR-NEMA Digital Imag. & Comm. 300