Skip to main content

What is the difference between a Peer to Peer Network and a Windows Domain?

A Peer to Peer Network is a configuration that was made popular in 1992 with the release of Microsoft Windows for Workgroups 3.11. In Windows XP and beyond, this configuration is referred to as "File & Printer Sharing."  Although Peer to Peer Networks are quick and easy to setup, they are very basic and can be costly to support due to their inherent design.  A Windows Domain is a far more beneficial network configuration for a number of reasons outlined in this document.  The primary difference between a Peer to Peer Network and a Windows Domain is centralized network management.  As we will demonstrate in this article, centralized network management dramatically reduces tech support which saves your organization time and money.  Additionally, a Windows Domain provides a number of significant benefits.

Data Location - Peer to Peer Network
In a Windows Peer to Peer network, business documents and email are stored on various workstations throughout the network rather than being stored in one central location. The daily backup job if one exists is therefore not able to backup all company data because important business data is not stored in one central location.

Data Location - Domain Environment
All important business data is stored in one place - on the Server. The daily backup process then insures that all business documents and email are backed up from this location on a daily basis.


Network Management - Peer to Peer Network
In a Windows Peer to Peer Network, each workstation on the network must be individually configured and supported.  The management of your network is spread out amongst all workstations on the network. When a technical issue arises, it is not uncommon that it is addressed on each individual workstation throughout the organization.  This configuration can be very inefficient and costly to support. 

Network Management - Domain Environment
The management of the network is conducted from one place - on the server. When a technical issue arises, it is typically addressed from on the server which often resolves the problem for the entire network including all workstations.


User Accounts - Peer to Peer Network
For each staff member to have access to each Workstation, a user account must be created on each Workstation.  The user account name and account password must having a matching value on each Workstation in order to maintain access to network resources such as Shared Files, Shared Drives and Shared Printers.

User Accounts - Domain Environment
The user accounts for the network are created and managed from one one place - on the Server. The workstations on the network are then joined to the Windows Domain.  This allows staff members to login to the Domain from any workstation on the network.


Shared Drives - Peer to Peer Network
Shared Drives must be manually mapped from each workstation on the network.

Shared Drives - Domain Environment
When a user logs into the Windows Domain, the Windows Server Login Script automatically maps all Shared Drives on the network.


Shared Printers - Peer to Peer Network
Shared Printers must be manually connected and printer drivers installed on each workstation.

Shared Printers - Domain Environment
The print driver is only installed once on the Server.  The Windows Server Login Script automatically maps all Shared Printers on the network. 


Antivirus - Peer to Peer Network
A stand-alone antvirus application must be installed on each workstation.  Each workstation then performs its own antivirus signature updates and

Antivirus - Domain Environment
A network antivirus application on the Server protects all workstations.  The Server retrieves antivirus signatures and distributes them to each workstation via the network antivirus client.


Email - Peer to Peer Network
An email client such as Microsoft Outlook is installed on each workstation.  Each workstation independently sends and receives email.

Email - Domain Environment
Using Exchange Server, the Server sends and receives email and distributes it to each user on the network via Microsoft Outlook.  In addition, Exchange Server provides for Shared Contacts, Shared Schedule Appointments and a single data location for all email.


Domain Controller - Peer to Peer Network
A Windows Peer to Peer Network configuration is designed for a computer network that does not include a Windows Server.  However, we periodically encounter Windows Peer to Peer Networks that have a Windows Server configured as a Windows Peer rather than a Windows Domain Controller.  When a Windows Server has been setup as a Windows Peer, it eliminates the benefit of purchasing a Windows Server.

Domain Controller - Domain Environment
The Windows Domain environment requires a Windows Server. The server is then configured as a Windows Domain Controller.

Comments

Popular posts from this blog

Access Denied (policy_denied). Your system policy has denied access to the requested URL. For assistance, contact your network support team.

While browsing the internet, you may encounter the message: "Access Denied (policy_denied).  Your system policy has denied access to the requested URL.  For assistance, contact your network support team."   This message indicates the internet traffic is being filtered.  The most common source of an internet traffic filter is in corporate environments that use a proxy server or a firewall appliance designed to filter web traffic.  Some businesses are configured as satellite locations using a VPN tunnel.  In these configurations, the VPN may be configured to filter internet traffic.  In rare instances, the Internet Service Provider is filtering internet traffic.  Typically though, your IT Department or a Network Management Team has configured your internet traffic to be filtered.  Isolating Source of Web Filtering In an environment that is unmanaged and the source of the filtering is unknown, following are some steps you may wish to peform: Th...

Event ID: 7001 - Source: VSS - Unable to create a shadow copy

When using Microsoft Windows Server, you may encounter the error message: "Unable to create a shadow copy."  In the Event Viewer, you may find the following Event: "Event ID: 7001 - Source: VSS - Unable to create a shadow copy."  This event involves the Volume Shadow Copy Service (VSS).  Most likely the Server was rebooted while creating a Shadow Copy.  Many websites describe deleting or renaming the C:\WINDOWS\SYSTEM32\WBEM directory used by Windows Management Instrumentation to resolve this issue.  This is not correct.  Following are the steps to resolve this issue: Double-click My Computer. Right-mouse click the Hard Drive causing the problem. Click the Shadow Copies tab. Select the appropriate Volume. Click Disable. Click OK. Click Start - Control Panel - Administrative Tools - Scheduled Tasks. Delete all tasks related to the Volume Shadow Copy Service. Reboot the Server. Double-click My Computer. Right-mouse click the Hard Drive causing the problem. Cl...

How do you stop an unstoppable Windows Service?

You may encounter a Windows Service in Services that has the buttons for Start, Stop, Pause and Resume greyed out.  If you attempt to stop the Service using sc stop [servicename], you encounter the error message: "The requested control is not valid for this service."  To resolve this issue, please perform the following steps: Click Start - Control Panel - Administrative Tools - Services. Double-click the relevant Service. Change the Service Start-Up Type to Disabled. Click Apply. Click OK. Hit CTRL-ALT-DEL on your keyboard. Select Task Manger. Perform an End Task on the relevant Service. This issue has been resolved. http://www.smartnetadmin.com