Exposure to Client server concept using TC/PIP, Blowfish

                    Exposure to Client server concept using TC/PIP, Blowfish

The Transmission Control Protocol (TCP) is one of the core protocols of the Internet protocol suite (IP), and is so common that the entire suite is often called TCP/IP. TCP provides reliable, ordered and error-checked delivery of a stream of octets between programs running on computers connected to a local area network, intranet or the public Internet. It resides at the transport layer.

Web browsers use TCP when they connect to servers on the World Wide Web, and it is used to deliver email and transfer files from one location to another. HTTP, HTTPS, SMTP, POP3, IMAP, SSH, FTP, Telnet and a variety of other protocols are typically encapsulated in TCP.

Applications that do not require the reliability of a TCP connection may instead use the connectionless User Datagram Protocol(UDP), which emphasizes low-overhead operation and reduced latency rather than error checking and delivery validation.

How to configure a client to use TCP/IP (Client Network Utility)

To configure a client to use TCP/IP

1. Click the General tab, and then click Add.
2. In the Add Network Library Configuration dialog box, click TCP/IP.
3. In the Server alias box, enter the alias of the instance of Microsoft® SQL Server™ listening on the Windows Sockets Net-Library.

With TCP/IP, you can also specify the server with its IP address instead of its name.

4. Do one of the following:
• Select the Dynamically determine port check box to automatically determine the port.
• Clear the dynamically determine port check box to set the port manually, and then in the Port number box, type the port number.

PGP:

Server Client Key Mode (SCKM) synchronizes private encryption keys with PGP Universal Server while ensuring that signing keys are always retained only by the end user. This mode helps to ensure compliance with local laws and corporate policies in some areas requiring that signing keys must not leave the control of the end user while ensuring that encryption keys are stored in case of emergency.

SCKM keys are generated on the client. Private encryption sub keys will be stored on both the client and PGP Universal Server, and private signing sub keys will be stored only on the client.