Jul 21, 2017
TCP port 636 -- LDAPS: SSL secured LDAP TCP port 3268 -- LDAP: Active Directory Global Catalog TCP port 3269 -- LDAPS: SSL secured Active Directory Global Catalog. TCP port 4234 -- Required for Archiving mail from Barracuda Email Encryption Service (BEES) TCP port 8000 -- HTTP: Default Administrative Web Interface. TCP port 8002 -- Clustering In both cases, as you can see, MS SQL Server is configured as a service and not as a port, assuming that the port used to connect is the default one (TCP 1433).Needless to say, if we are forced to use a non-standard port, this type of configuration will no longer be fine: we will be forced to specify it manually. Because SSL can use TCP [1] to transport SSL records, and so SSL relies on TCP as a service. That is, SSL takes the user data stream, and converts it into a series of records; it then gives these records to TCP to transmit. On the other side, the receiver's TCP stack gets these records and gives it to SSL to decrypt. Similarly, TCP takes the Change the TCP Port Number in the TCP Port edit box (or click Advanced for multiple Port settings). Click OK to save the changes. Microsoft Internet Information Services 7.0. Open Internet Information Services (IIS) Manager. Select the Web site that you wish to configure. In the Action pane, click Bindings.
Port 992 (tcp/udp) :: SpeedGuide
Choose the Port and Protocol for Mobile VPN with SSL By default, Mobile VPN with SSL operates on the port and protocol used for encrypted website traffic (HTTPS) to avoid being blocked. This is one of the main advantages of SSL VPN over other Mobile VPN options. We recommend that you choose TCP port 53 or UDP port 53 (DNS) to keep this advantage.
Jul 11, 2016 · Port 587 is intended as a client submission port for POP and IMAP clients so you don't have to risk configuring TCP port 25 for authentication and possibly mucking up your transport flow. What you're trying to do is highly nonstandard.
HTTPS is HTTP using SSL/TLS security. SSL/TLS typically runs on top of TCP, but there is nothing to stop you from running it on UDP, SCTP or any other transport layer protocol. As a matter of fact HTTPS over TCP and UDP are both defined as "well known" by IANA and have reserved port numbers.