/etc/fstab (static mounts)
/etc/auto.master (dynamic mounts)
/etc/fstab (static mounts) /etc/auto.master (dynamic mounts)
Simple: in order to have a client-server architecture you need a network. The role of the network is to move data packets between the client and the server. In a client-server architecture the server usually has to manage the network (for example, a domain controller in a Windows environment).
In order to begin the handshake process, the client sends a SYN packet to the server. This is required to establish a synchronization with the server in order to ensure that both the client and the server will maintain and keep their exchange of packets in the right order. In order to complete the "handshake," the reponse from the server will be an ACK packet.
In general, and in the simplest form, a server is a machine or a program (software application) that waits for incoming requests, and a client is a machine or program sending requests to another client or a server in order to take action
Inverse domain is used to map an address to a name. For instance, if a server receives a request from a client and this server has only the ip addresses of the clients in its list then the server needs to find out if this client is on its authorized client list. In order to determine if the client is on the authorized client list,server asks its resolver to query to the DNS server to map an address to name. And this type of querys are called inverse query(pointer query -PTR).
Inverse domain is used to map an address to a name. For instance, if a server receives a request from a client and this server has only the ip addresses of the clients in its list then the server needs to find out if this client is on its authorized client list. In order to determine if the client is on the authorized client list,server asks its resolver to query to the DNS server to map an address to name. And this type of querys are called inverse query(pointer query -PTR).
Cache,Host Files, DNS server
In order to mount a drive, if it is a network drive, you must have an NFS server installed and an NFS client on the machine you wish to mount the directory for. The NFS server will export the file system to the network, and the NFS client machine will mount it. To mount it on a client machine, create or use an empty directory. Then, using the 'mount' command, indicate the server name and directory on the server and the mount point of the client. For example: mount tarzan:/opt/testing/data /mnt Will mount a directory from the 'tarzan' server called /opt/testing/data under the /mnt directory of the client. So when a client looks at /mnt, they are really looking at /opt/testing/data on the server.
FTP is a TCP based service exclusively. There is no UDP component to FTP. FTP is an unusual service in that it utilizes two ports, a 'data' port and a 'command' port (also known as the control port). Traditionally these are port 21 for the command port and port 20 for the data port. The confusion begins however, when we find that depending on the mode, the data port is not always on port 20. In active mode FTP the client connects from a random unprivileged port (N > 1023) to the FTP server's command port, port 21. Then, the client starts listening to port N+1 and sends the FTP command PORT N+1 to the FTP server. The server will then connect back to the client's specified data port from its local data port, which is port 20. From the server-side firewall's standpoint, to support active mode FTP the following communication channels need to be opened: * FTP server's port 21 from anywhere (Client initiates connection) * FTP server's port 21 to ports > 1023 (Server responds to client's control port) * FTP server's port 20 to ports > 1023 (Server initiates data connection to client's data port) * FTP server's port 20 from ports > 1023 (Client sends ACKs to server's data port) In order to resolve the issue of the server initiating the connection to the client a different method for FTP connections was developed. This was known as passive mode, or PASV, after the command used by the client to tell the server it is in passive mode. In passive mode FTP the client initiates both connections to the server, solving the problem of firewalls filtering the incoming data port connection to the client from the server. When opening an FTP connection, the client opens two random unprivileged ports locally (N > 1023 and N+1). The first port contacts the server on port 21, but instead of then issuing a PORT command and allowing the server to connect back to its data port, the client will issue the PASV command. The result of this is that the server then opens a random unprivileged port (P > 1023) and sends the PORT P command back to the client. The client then initiates the connection from port N+1 to port P on the server to transfer data. From the server-side firewall's standpoint, to support passive mode FTP the following communication channels need to be opened: * FTP server's port 21 from anywhere (Client initiates connection) * FTP server's port 21 to ports > 1023 (Server responds to client's control port) * FTP server's ports > 1023 from anywhere (Client initiates data connection to random port specified by server) * FTP server's ports > 1023 to remote ports > 1023 (Server sends ACKs (and data) to client's data port)
A server is that which meets the needs or provides services to order computers,specifically client computers.it looks just like the cpu but sometimes bigger or smaller than the cpu
A license is a way for software manufacturers to make sure that bootleg software is not supported. You must have a license(for businesses) to run certain software. This applies when you have say Windows Server 2003. the server has it's own license. You need client licenses to access this software from the workstation pc's. They are called Client Access Licenses (CAL's) and must be bought in order for them to access the server. You need one for each client. and they are not cheap.
A stateful server loses all its volatile state in a crash. * Restore state using a recovery protocol based on a dialog with clients, or abort operations that were underway when the crash occurred. * Server needs to be aware of client failures in order to reclaim space allocated to record the state of crashed client processes (orphan detection and elimination).