Skip to main content

Posts

Shared Folder Permissions

Shared folder permissions are used to restrict access to a folder or file that is shared over a network. Folder sharing is normally used to grant remote users access to files and folders over a network. Web sharing grants remote users access to files from the Web if Internet Information Services (IIS) is installed. Members of the Administrators or Power Users group can share folders on a Windows member server. Users have to be members of the Administrators or Server Operators group to share folders on a domain’s domain controller. Users that have the Create Permanent Shared Objects user right are able to share folders as well. To share folders on NTFS volumes, users have to minimally have the Read permission. When folders are shared, it is important to keep in mind that only folders can be shared, not files. Shared folder permissions are irrelevant to users who are locally logged onto a computer. Shared folders that are moved are no longer shared. When shared folders are copied,

How to Register a DLL

On Microsoft Windows operating systems, a DLL stands for Dynamic Link Library. DLLs are relatively small files that include a library of functions- usually data that can be shared across multiple applications. Various applications call on DLLs, which they can load and utilize concurrently. Registering a DLL There are two easy ways to register a DLL in a Windows operating system’s registry. The first way is via self registering files and the second way is to manually register the DLL. Self Registering Files It should be noted that many DLL files are self registering, they include information required to store themselves in the operating system’s registry. As the name states, self registering files require no human intervention. Self registering files automatically store themselves on computers and become accessible when needed. Besides DLL files, other types of files that are sometimes self registering include .EXE and .OCX. Manually Register Files The second method used to r

What is the Windows Registry?

The Windows registry is a database that Microsoft designed to store configuration settings and options for the operating system (OS). It increases OS speed and also contains settings for hardware components, end-users, and system software to help ensure that the highest possible quality of service is delivered to th user. The registry is used as an entrance point or gateway for the Windows OS kernel and has been in use for a number of years. Although significant improvements have been made to the registry, it is still susceptible to getting bloated with time and is a common target for computer malware attack. How to Backup the Windows Registry Before modifying the Windows Registry, Microsoft recommends that a file backup is made in case the change corrupts the registry file. Step 1 – Choose “Start” and “Run.” Step 2 – Enter “Command” in the search text field then press “Enter.” Step 3 – Enter “regedit” at the DOS prompt, then press “Enter” to open the Windows Registry Editor.

How to Repair Windows Registry Errors

Windows Registry is a group of data files within the Windows Operating System that contain essential information for running Windows on a computer. Windows Registry runs all programs, user interfaces, and services that the Windows Operating System provides and is critical to a computer’s proper performance. Whenever a program is installed on a computer, Windows Installer places data in the Windows Registry to allow the program to run and access other Windows Operating System components. When these data files are lost, corrupted, or incomplete uninstallations or viruses modify them, the computer may not work properly or experience decreased performance. By using a software known as a registry cleaner, a user can repair the Windows Registry and improve his/her computer’s performance. Free Window Registry Repair Free Window Registry Repair is a free registry cleaner that allows users to repair Windows Registry by removing invalid registry entries, deleting registry file copies, and

What is Mrtstub.exe?

Mrtstub.exe (Mrt.exe) is a process that runs on all Windows Operating System versions. It is a malicious software that downloads and installs other malicious software. Mrtstub.exe can almost always be found directly on the computer’s primary hard drive, can hide itself in a randomly named folder, and does not have a visible window. If the user discovers Mrtstub.exe or Mrt.exe on his/her computer, it is highly recommended that the process is stopped and removed immediately. How Mrtstub.exe Works Mrtstub.exe infiltrates the computer via third party software, temporary Internet files, cookies, and as mislabeled files. Once the file has been downloaded, it installs itself and begins looking through the computer for known viruses and security weaknesses. Mrtstub.exe then begins to download and install a wide variety of other malicious programs on the computer. Is Mrtstub.exe Harmful? Mrtstub.exe is a very harmful file considering the potential damage it can cause by introducing

What is a Sysvol?

SYSVOL is the acronym for the SYSFOL folder and all of the files stored in it on the Windows Operating System (OS). It stores the server’s copy of public data and files for the domain. These files consist of group or user policy information. The information stored in the SYSVOL folder is copied to all domain controllers on the respective domain. What are the SYSVOL Requirements? First, the SYSVOL folder has to be located on a Windows NTFS volume. The information stored in the SYSVOL folder is replicated on all domain controllers’ local disk via the File Replication Service (FRS), which must be installed for the operation to work properly. For network clients to access the SYSVOL tree’s contents, they must gain permission to access the NETLOGON and SYSVOL folders. The SYSVOL folder is used for a number of common networking applications, including adding a domain to an existing set or “Forest” of domain servers and locally creating a new logon script. How to Add a Domain to an

When was the Routing Information Protocol Invented?

Hedrick of Rutgers University invented the Routing Information Protocol in the summer of 1988. Since then it has become the most common routing protocol on LANs and WANs and continues to be used today. Hedrick’s work was based on the Unix computer program “routed,” which was distributed with the 4.3 version of the BSD branch of the OS. At that time, the “routed” protocol was the de-facto standard for research laboratories to communicate via network gateways. The RIP protocols use the Bellman-Ford algorithm for distance vector computation and other work completed as early as 1969 on the ARPANET. The PUP protocol preceded Hedrick’s work and later became the RIP. How does the Routing Information Protocol Work? RIP relies on a routing database that stores information on the fastest routes that exist between destinations on the network. This lets each router tell others the fastest route(s) and uses an update algorithm that revises route updates for each router based on the latest info

Routing Information Protocol

The Routing Information Protocol (RIP) is the IGP standard protocol that is used on Local Area Networks (LANs). It helps to ensure a higher degree of network stability by quickly re-routing network packets if one of the network connections goes offline. When the RIP is active on a network, users experience little to no service interruptions due to single router, switch, or server outages if there are sufficient network resources available to continue routing network traffic.

Why is RPC Server Unavailable?

An RPC server may be unavailable for a number of reasons. If the service that a client is attempting to contact no longer exists or has been moved to a different location, the RPC server will appear unavailable because it cannot fulfill the client’s request. Another reason an RPC server may be unavailable is that the network is experiencing hardware or software-related difficulties that must be repaired before the RPC server can be contacted. Likewise, a user may have disabled the RPC server or specifically prevented remote clients from contacting it. How to Fix RPC Server In order to fix an RPC server, the user must identify the problem that is causing the RPC server to be unavailable in the first place. The user should check all network cables, restart all network devices, and, if possible, manually check the RPC server for malfunctions and accessibility restrictions.

How RPC Works

RPC implements a series of tasks in order to establish communication between a client and a server. First, the client initiates a specific objective by contacting a local process known as a “client stub” with parameters for accessing a file or service. The client stub converts the parameters it receives from the client into appropriate parameters on the server. The client stub then sends these new parameters to the operating system’s kernel, which then sends the message to the server stub (same as client stub, but is located on the server machine). The server stub decodes the message and sends it to the appropriate application or service. Once the application has been contacted, replies may be sent in the reverse direction through each of these processes.

MPLS Networks

An MPLS (Multi-Protocol Label Switching) network is one in which many devices are connected to each other through a master system that receives data from each individual device and relays it to any other device within the network. MPLS networks differ from traditional networks because they connect a large number of devices across long distances by tunneling through the Internet. How MPLS Networks Work An MPLS network is a cloud-like system of computers and other devices that all communicate with each other by assigning labels to data packets so that they can be forwarded from one device to another. For example, if Device A wishes to send a data packet to Device E, Device A will insert a header in the data packet with a label stack that contains information about the data packet, where it came from, and where it is going. Device A will then send the data packet to Device B, Device B will send the data packet to Device C, Device C will send the data packet to Device D, and Device D