{"id":819,"date":"2026-09-18T13:36:57","date_gmt":"2026-09-18T13:36:57","guid":{"rendered":"https:\/\/www.vps.tc\/blog\/?p=819"},"modified":"2026-09-18T17:40:22","modified_gmt":"2026-09-18T17:40:22","slug":"how-to-set-up-smb-file-sharing-on-windows-server","status":"publish","type":"post","link":"https:\/\/www.vps.tc\/blog\/en\/how-to-set-up-smb-file-sharing-on-windows-server\/","title":{"rendered":"How to Set Up SMB File Sharing on Windows Server"},"content":{"rendered":"<div class=\"aiw-summary\" id=\"aiw-ozet\">\n<p class=\"aiw-summary-title\">Quick Summary &#8211; Windows Server File Sharing<\/p>\n<p>A secure SMB share needs more than a folder and a network path. Prepare the server, separate share and NTFS permissions, restrict TCP 445, and test both access and recovery.<\/p>\n<ul>\n<li><strong>Prepare the server<\/strong> \u2014 Set a static IP, correct DNS, a meaningful hostname, and an appropriate network profile.<\/li>\n<li><strong>Create the share<\/strong> \u2014 Use Server Manager or PowerShell and keep shared data on a suitable data volume.<\/li>\n<li><strong>Control permissions<\/strong> \u2014 Use Active Directory security groups and test the effective combination of SMB and NTFS permissions.<\/li>\n<li><strong>Secure SMB<\/strong> \u2014 Keep SMBv1 disabled, restrict TCP 445, and enable encryption where the workload requires it.<\/li>\n<li><strong>Monitor access<\/strong> \u2014 Watch disk capacity, sessions, open files, authentication failures, and relevant security events.<\/li>\n<li><strong>Test recovery<\/strong> \u2014 Treat RAID and shadow copies as availability features, not backups, and perform regular restore tests.<\/li>\n<\/ul>\n<\/div>\n<p class=\"aiw-lead\">To set up Windows Server file sharing safely, install the File Server role, create an SMB share, and control access through both share and NTFS permissions. Keep SMB traffic on trusted networks, disable SMBv1, restrict TCP 445, and verify the result from a normal client with real read, write, and restore tests.<\/p>\n<div class=\"aiw-toc\" style=\"border:1px solid #dbe3ea;border-radius:8px;padding:16px 20px;margin:0 0 28px\">\n<p class=\"aiw-toc-head\"><strong>Table of Contents<\/strong><span class=\"aiw-toc-meta\"> \u00b7 13 min read<\/span><\/p>\n<ol style=\"margin:10px 0 0;padding-left:22px\">\n<li><a href=\"#start-with-the-server-not-the-share-wizard\">Start with the server, not the share wizard<\/a><\/li>\n<li><a href=\"#create-the-share-with-a-clear-layout\">Create the share with a clear layout<\/a><\/li>\n<li><a href=\"#share-permissions-are-only-half-the-decision\">Share permissions are only half the decision<\/a><\/li>\n<li><a href=\"#keep-smb-inside-the-networks-that-need-it\">Keep SMB inside the networks that need it<\/a><\/li>\n<li><a href=\"#connect-clients-and-troubleshoot-the-right-layer\">Connect clients and troubleshoot the right layer<\/a><\/li>\n<li><a href=\"#monitor-the-server-and-prove-that-recovery-works\">Monitor the server and prove that recovery works<\/a><\/li>\n<li><a href=\"#read-the-error-before-changing-the-firewall\">Read the error before changing the firewall<\/a><\/li>\n<li><a href=\"#choose-smb-for-shared-work-not-public-transfer\">Choose SMB for shared work, not public transfer<\/a><\/li>\n<li><a href=\"#test-it-as-the-person-who-will-use-it\">Test it as the person who will use it<\/a><\/li>\n<li><a href=\"#check-these-before-going-live\">Check These Before Going Live<\/a><\/li>\n<li><a href=\"#frequently-asked-questions\">Frequently Asked Questions<\/a><\/li>\n<li><a href=\"#sources\">Sources<\/a><\/li>\n<\/ol>\n<\/div>\n<h2 id=\"start-with-the-server-not-the-share-wizard\">Start with the server, not the share wizard<\/h2>\n<p>A file share can look healthy while its permissions, backups, or network boundaries are quietly wrong. I have learned to treat SMB as a small system rather than a folder with a network name: the server identity, TCP 445 access, authentication, share permissions, NTFS permissions, monitoring, and recovery all belong in the same plan.<\/p>\n<p>First decide what the server is meant to do. If it only provides file shares, I do not install unrelated roles just because the wizard offers them. On Windows Server versions that support the current File Server role, PowerShell is usually quicker than Server Manager:<\/p>\n<pre><code>Install-WindowsFeature -Name FS-FileServer -IncludeManagementTools<\/code><\/pre>\n<p>That command installs the File Server role and its management tools. Nothing more.<\/p>\n<p>Give the server a static IP address, a meaningful hostname, and a correct DNS record. In an Active Directory environment, join it to the domain. On a small workgroup network, avoid maintaining matching local usernames and passwords on every machine if you can use a central authentication method instead.<\/p>\n<p>Check the hostname and network profile before creating anything:<\/p>\n<pre><code>hostname\nGet-NetConnectionProfile\nGet-NetIPAddress -AddressFamily IPv4<\/code><\/pre>\n<p>You should see the expected hostname, a <code>DomainAuthenticated<\/code> or otherwise appropriate network profile, and the correct IPv4 address. There is no good reason to expose SMB directly to the internet. Keep it on a trusted LAN, VPN, or private network segment.<\/p>\n<p><strong>Before you continue:<\/strong> verify the hostname, DNS, static address, and network profile.<\/p>\n<h2 id=\"create-the-share-with-a-clear-layout\">Create the share with a clear layout<\/h2>\n<p>In Server Manager, open <em>File and Storage Services<\/em>, select <em>Shares<\/em>, and start the <em>New Share<\/em> wizard. For most internal folders, <em>SMB Share &#8211; Quick<\/em> is the sensible choice. Select the physical folder path rather than hiding the layout from yourself.<\/p>\n<p>A small file server might use a structure like this:<\/p>\n<pre><code>D:\\Shares\\Accounting\nD:\\Shares\\Common\nD:\\Shares\\Archive<\/code><\/pre>\n<p>I prefer shared data on a separate volume from the operating system. That makes capacity alerts, backups, and recovery work easier to reason about. Spaces and non-ASCII characters are supported, but short and consistent names cause fewer surprises in scripts, backup jobs, and older clients.<\/p>\n<p>PowerShell can create the directory and share in a few lines:<\/p>\n<pre><code>New-Item -ItemType Directory -Path 'D:\\Shares\\Common' -Force\nNew-SmbShare -Name 'Common' -Path 'D:\\Shares\\Common' -ChangeAccess 'DOMAIN\\Common-Users' -FullAccess 'DOMAIN\\Domain Admins'<\/code><\/pre>\n<p>Here, <code>-Name<\/code> is the share name clients see and <code>-Path<\/code> is the local folder. <code>-ChangeAccess<\/code> allows users to create and modify files, while <code>-FullAccess<\/code> should stay limited to administrators.<\/p>\n<p>Confirm what was created:<\/p>\n<pre><code>Get-SmbShare -Name 'Common' | Format-List Name,Path,Description,EncryptData\nGet-SmbShareAccess -Name 'Common'<\/code><\/pre>\n<p>Clients can connect to <code>\\\\FILE-SERVER\\Common<\/code>. An IP path such as <code>\\\\192.0.2.10\\Common<\/code> is useful for troubleshooting, but I use the DNS name for normal operation. It keeps mapped drives independent of a future address change.<\/p>\n<div class=\"aiw-callout aiw-callout-tip\">\n<p class=\"aiw-callout-label\">Tip<\/p>\n<p>Use a DNS hostname for normal access and reserve the IP address for troubleshooting. This keeps mapped drives stable if the server address changes later.<\/p>\n<\/div>\n<h2 id=\"share-permissions-are-only-half-the-decision\">Share permissions are only half the decision<\/h2>\n<p>SMB access has two permission layers: share permissions and NTFS permissions. The effective result is the intersection of both. If the share grants <code>Change<\/code> but NTFS grants only <code>Read<\/code>, the user still cannot write. A <code>Full Control<\/code> share permission cannot override a read-only NTFS ACL.<\/p>\n<table>\n<thead>\n<tr>\n<th>Layer<\/th>\n<th>When it applies<\/th>\n<th>Where it is managed<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>SMB share permission<\/td>\n<td>Network access<\/td>\n<td>Share Permissions or <code>Grant-SmbShareAccess<\/code><\/td>\n<\/tr>\n<tr>\n<td>NTFS permission<\/td>\n<td>Local and network access<\/td>\n<td>Security tab or <code>icacls<\/code><\/td>\n<\/tr>\n<tr>\n<td>Effective permission<\/td>\n<td>The more restrictive combination<\/td>\n<td>Effective Access<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>A practical design is to keep share permissions relatively broad and apply detailed restrictions with NTFS. For example, you might grant <code>Authenticated Users<\/code> <code>Change<\/code> at the share level, then control department folders with security groups. That design is safe only when the NTFS rules are deliberate and reviewed.<\/p>\n<p>Use groups instead of individual user entries:<\/p>\n<pre><code>icacls \"D:\\Shares\\Accounting\" \/inheritance:r\nicacls \"D:\\Shares\\Accounting\" \/grant \"DOMAIN\\Accounting-Read:(OI)(CI)(RX)\"\nicacls \"D:\\Shares\\Accounting\" \/grant \"DOMAIN\\Accounting-Write:(OI)(CI)(M)\"\nicacls \"D:\\Shares\\Accounting\" \/grant \"DOMAIN\\Domain Admins:(OI)(CI)(F)\"<\/code><\/pre>\n<p><code>(OI)<\/code> inherits to files, while <code>(CI)<\/code> inherits to subdirectories. <code>(RX)<\/code> means read and execute, <code>(M)<\/code> means modify, and <code>(F)<\/code> means full control. The <code>\/inheritance:r<\/code> option removes existing inheritance, so check that administrators and required system accounts will retain access before running it.<\/p>\n<p>Auditing can record failed access attempts in the Security log. I do not add audit rules to every folder by default. Too much noise buries the event I actually need.<\/p>\n<p><strong>Use role-based groups.<\/strong> Then test the effective result with a normal user account, not an administrator account that can bypass the question.<\/p>\n<div class=\"aiw-callout aiw-callout-warn\">\n<p class=\"aiw-callout-label\">Caution<\/p>\n<p>The share permission is not the whole permission model. NTFS can still deny an operation, and a broad share permission can expose more data than intended if the folder ACL is careless.<\/p>\n<\/div>\n<h2 id=\"keep-smb-inside-the-networks-that-need-it\">Keep SMB inside the networks that need it<\/h2>\n<p>SMB 3.x includes features such as signing and encryption. SMBv1 is obsolete, and current Windows Server installations should not enable it unless you have identified a specific legacy dependency that cannot yet be removed.<\/p>\n<pre><code>Get-WindowsOptionalFeature -Online -FeatureName SMB1Protocol\nGet-SmbServerConfiguration | Select-Object EnableSMB1Protocol,EnableSMB2Protocol,RequireSecuritySignature,EncryptData<\/code><\/pre>\n<p>If SMBv1 is enabled, identify the dependent devices before disabling it:<\/p>\n<pre><code>Disable-WindowsOptionalFeature -Online -FeatureName SMB1Protocol -NoRestart<\/code><\/pre>\n<p>Test client compatibility first. An old printer or NAS is not a good reason to enable SMBv1 for every share. Update it, replace it, or isolate it on a restricted network.<\/p>\n<p>For encryption on a particular share:<\/p>\n<pre><code>Set-SmbShare -Name 'Accounting' -EncryptData $true\nGet-SmbShare -Name 'Accounting' | Select-Object Name,EncryptData<\/code><\/pre>\n<p>Encryption protects data while it crosses the network. It does not encrypt files at rest on the server. For theft or physical-access scenarios, consider BitLocker and key management separately.<\/p>\n<p>Windows Defender Firewall rules for file sharing should be limited to the profiles and source networks that require them. The main SMB target is TCP 445. Forwarding that port from an internet router puts the file server directly in reach of scanners and attackers.<\/p>\n<p><strong>Keep SMBv1 disabled and TCP 445 private.<\/strong> Those two checks remove a surprising amount of unnecessary exposure.<\/p>\n<h2 id=\"connect-clients-and-troubleshoot-the-right-layer\">Connect clients and troubleshoot the right layer<\/h2>\n<p>On a Windows client, enter <code>\\\\FILE-SERVER\\Common<\/code> in File Explorer. For a temporary command-line connection:<\/p>\n<pre><code>net use \\\\FILE-SERVER\\Common \/user:DOMAIN\\user *<\/code><\/pre>\n<p>The asterisk prompts for the password without displaying it. To map a persistent drive:<\/p>\n<pre><code>net use Z: \\\\FILE-SERVER\\Common \/persistent:yes<\/code><\/pre>\n<p>In a domain, Group Policy Preferences are easier to manage across many clients. Windows can also retain existing credentials for a server, so connecting to the same host with different accounts may produce a misleading error.<\/p>\n<p>When a connection fails, check name resolution and TCP 445 separately:<\/p>\n<pre><code>Resolve-DnsName FILE-SERVER\nTest-NetConnection FILE-SERVER -Port 445\nGet-SmbConnection<\/code><\/pre>\n<p><code>TcpTestSucceeded : True<\/code> proves that the port is reachable. It does not prove that the account is authorized. If the port is open but access is denied, inspect the share name, authentication context, group membership, and NTFS permissions.<\/p>\n<p>The troubleshooting method in <strong><a href=\"https:\/\/www.vps.tc\/blog\/en\/how-to-fix-dns-probe-finished-nxdomain-error\/\">How to Fix DNS_PROBE_FINISHED_NXDOMAIN Error<\/a><\/strong> is useful when the problem is name resolution. For a wider network-layer check, <strong><a href=\"https:\/\/www.vps.tc\/blog\/en\/what-is-an-ip-address-and-how-does-it-work\/\">What Is an IP Address and How Does It Work?<\/a><\/strong> and <strong><a href=\"https:\/\/www.vps.tc\/blog\/en\/what-is-arp-address-resolution-protocol-explained\/\">What Is ARP? Address Resolution Protocol Explained<\/a><\/strong> provide useful background.<\/p>\n<h2 id=\"monitor-the-server-and-prove-that-recovery-works\">Monitor the server and prove that recovery works<\/h2>\n<p>A share is not finished when the first user opens it. Watch free disk space, active SMB sessions, open files, copy failures, and failed authentication attempts.<\/p>\n<pre><code>Get-SmbSession | Select-Object ClientComputerName,ClientUserName,NumOpens\nGet-SmbOpenFile | Select-Object ClientComputerName,ClientUserName,Path<\/code><\/pre>\n<p>Do not close a session merely because a file appears locked. Identify the client and user first, then close the application in a controlled way whenever possible.<\/p>\n<p>I learned the backup part during a degraded RAID1 incident. One disk had already failed, and then the remaining disk began making noises that were impossible to ignore. The replacement process was tense because the array was still serving files, but the real comfort came from knowing we had an independent backup and had actually restored from it before. RAID gave us continuity; it did not give us a second copy.<\/p>\n<p>Windows Server Backup, VSS-based backups, a separate backup server, or another suitable backup system can all work. RAID is not a backup. Ransomware and accidental deletion call for a separate offline or immutable copy, plus regular restore tests.<\/p>\n<p>Shadow Copies for Shared Folders can help users recover previous versions quickly, but they are not a replacement for backups. They can disappear with the same disk failure, and their allocated space can fill under heavy write activity.<\/p>\n<p>Set a disk-capacity alert instead of watching Explorer manually. Treating less than 15 percent free space as an early warning can be a reasonable starting point, but the useful threshold depends on workload, volume size, and how quickly the data grows.<\/p>\n<p><strong>Restore something.<\/strong> After each backup job, restore at least one file. Once a month, rehearse a larger restore into a different folder or test environment.<\/p>\n<div class=\"aiw-callout aiw-callout-field\">\n<p class=\"aiw-callout-label\">From the field<\/p>\n<p>During a degraded RAID1 incident, I was grateful that the independent backup had been tested before the second disk became unreliable. RAID kept the files available for a while; the restore test gave me confidence that recovery did not depend on the array surviving.<\/p>\n<\/div>\n<h2 id=\"read-the-error-before-changing-the-firewall\">Read the error before changing the firewall<\/h2>\n<h3>&#8220;Network path was not found&#8221;<\/h3>\n<p>Check the share name and DNS resolution first. If <code>Test-NetConnection FILE-SERVER -Port 445<\/code> fails, inspect Windows Defender Firewall, network ACLs, VPN routes, and whether the server is running. If the IP path works but the hostname does not, DNS is the likely cause.<\/p>\n<h3>&#8220;Access is denied&#8221;<\/h3>\n<p>Review both SMB and NTFS permissions. If group membership changed recently, sign out and back in or renew Kerberos tickets. Traversal permissions on parent folders can affect the result too.<\/p>\n<h3>Credentials are requested repeatedly<\/h3>\n<p>Check saved credentials on the client, the domain format, and time synchronization. In Active Directory, clock skew can interfere with Kerberos authentication. Inspect existing connections with <code>net use<\/code> and remove unnecessary ones before trying another account.<\/p>\n<h3>Copy speed is low<\/h3>\n<p>Separate disk latency, client and server link speed, antivirus scanning, and the number of small files. One large file may transfer quickly while thousands of small files crawl because of metadata work, disk latency, or the application&#8217;s access pattern. Tuning theoretical network numbers will not fix a queue building on the disk.<\/p>\n<div class=\"aiw-callout aiw-callout-example\">\n<p class=\"aiw-callout-label\">Example<\/p>\n<p>If a client can reach TCP 445 but receives &quot;Access is denied,&quot; stop treating it as a firewall problem. Check the share name, authentication context, group membership, NTFS ACLs, and parent-folder traversal permissions.<\/p>\n<\/div>\n<h2 id=\"choose-smb-for-shared-work-not-public-transfer\">Choose SMB for shared work, not public transfer<\/h2>\n<p>SMB and FTP solve different problems. SMB suits Windows users who need to open, edit, and lock files on a network share while using NTFS and Active Directory permissions. FTP is designed for transfer; for current deployments, use FTPS with TLS or SFTP over SSH instead of plain FTP.<\/p>\n<table>\n<thead>\n<tr>\n<th>Criteria<\/th>\n<th>SMB<\/th>\n<th>FTP\/SFTP<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Typical use<\/td>\n<td>Shared folder on a local network<\/td>\n<td>Remote file transfer<\/td>\n<\/tr>\n<tr>\n<td>Authentication<\/td>\n<td>AD or local Windows account<\/td>\n<td>Account, TLS, or SSH key<\/td>\n<\/tr>\n<tr>\n<td>Mapped-drive behavior<\/td>\n<td>Supported natively<\/td>\n<td>Requires an extra client or layer<\/td>\n<\/tr>\n<tr>\n<td>Internet exposure<\/td>\n<td>Not recommended<\/td>\n<td>Can be controlled with SFTP or FTPS<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>For a one-time file transfer to a remote customer, use SFTP, a secure portal, or a VPN rather than exposing SMB. The guide <strong><a href=\"https:\/\/www.vps.tc\/blog\/en\/what-is-ftp-file-transfer-protocol-explained\/\">What Is FTP? File Transfer Protocol Explained<\/a><\/strong> covers the basic differences between transfer protocols.<\/p>\n<h2 id=\"test-it-as-the-person-who-will-use-it\">Test it as the person who will use it<\/h2>\n<p>Run the first test from a real client, not only from the file server itself. Test reading, creating, modifying, and deleting a file. Then test a folder the account should not reach. Use a standard test account, not your everyday administrator account.<\/p>\n<p>In Event Viewer, review SMB-related entries under <em>Applications and Services Logs<\/em> and security events under <em>Windows Logs &gt; Security<\/em>. Decide which events matter before enabling auditing; otherwise useful signals disappear into noise.<\/p>\n<p>Document the share inventory: share name, physical path, owner group, write access, backup policy, retention period, and permitted networks. Months later, the useful question will be &#8220;Who can access this folder, and why?&#8221;<\/p>\n<p>I now keep that answer next to the restore result. A share that opens is only a share that opens; the finished system is the one whose access and recovery behavior I can demonstrate.<\/p>\n<h2 id=\"check-these-before-going-live\">Check These Before Going Live<\/h2>\n<ul class=\"aiw-checklist\">\n<li>Give the server a static IP address and create the correct DNS record.<\/li>\n<li>Confirm the hostname and network profile before creating any shares.<\/li>\n<li>Create shares with clear names on a dedicated data volume where appropriate.<\/li>\n<li>Assign access through role-based groups and review both SMB and NTFS permissions.<\/li>\n<li>Keep SMBv1 disabled and restrict TCP 445 to trusted networks.<\/li>\n<li>Test read, write, delete, and denied-access behavior from a standard client account.<\/li>\n<li>Restore files from a backup and record the result before calling the backup usable.<\/li>\n<\/ul>\n<div class=\"aiw-cta\">\n<p>Before handing over a new share, connect with a standard user account and test the exact actions that user should be able to perform. A share is not finished when it opens; it is finished when access, logging, backup, and restore behavior are all known.<\/p>\n<p class=\"aiw-cta-action\"><a href=\"https:\/\/www.vps.tc\/en\/vps\">Explore VPS plans<\/a><\/p>\n<\/div>\n<p>If you&#8217;re running Windows Server on physical rack hardware, I also recommend reading my new <a href=\"https:\/\/www.vps.tc\/blog\/en\/what-is-a-data-center-pdu-power-distribution-guide\/\">data center PDU guide<\/a> to understand how power is distributed safely and monitored across your equipment.<\/p>\n<h2 id=\"frequently-asked-questions\">Frequently Asked Questions<\/h2>\n<div class=\"aiw-faq\">\n<details class=\"aiw-faq-item\" open>\n<summary>What is required for Windows Server file sharing?<\/summary>\n<p>You need a Windows Server installation with the File Server role, a reachable network address, correct DNS, a shared folder, and appropriate SMB and NTFS permissions. In a domain environment, joining the server to Active Directory usually makes authentication and group-based access easier. You also need firewall rules that permit TCP 445 only from trusted networks and a backup plan that has been tested by restoring files.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>Should SMBv1 be enabled for older devices?<\/summary>\n<p>Usually no. SMBv1 is obsolete and lacks the security expected from current Windows Server deployments. First identify the device that requires it, then update or replace the device, or isolate it on a restricted network segment. Enabling SMBv1 across the file server simply to accommodate one old printer or NAS increases exposure for every share on that server.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>What is the difference between share and NTFS permissions?<\/summary>\n<p>Share permissions apply when a user connects over SMB, while NTFS permissions apply both locally and over the network. Effective access is limited by the more restrictive result. For example, Change at the share level does not override read-only NTFS permissions. Use groups, document the design, and test with a standard account rather than assuming that an administrator&#039;s access represents everyone else&#039;s access.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>Why can I reach port 445 but not open the share?<\/summary>\n<p>A successful TCP 445 test proves only that the network path to the SMB service is available. The share name may be wrong, authentication may use the wrong account or domain, or share and NTFS permissions may deny access. Check Get-SmbShareAccess, the folder ACL, group membership, and existing client credentials before changing firewall rules.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>Is RAID a backup for a Windows file server?<\/summary>\n<p>No. RAID can keep a server operating after some disk failures, but it does not protect against accidental deletion, ransomware, corruption, or a failure affecting the whole array. Keep separate backup copies, preferably including an offline or immutable copy, and test restoration regularly. Shadow Copies can help recover earlier versions quickly, but they also do not replace independent backups.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>Should I expose SMB to the internet for remote users?<\/summary>\n<p>Do not forward TCP 445 directly from the internet to a file server. Use a VPN, private network connection, secure portal, SFTP, or another controlled access method instead. SMB is designed primarily for trusted network environments, and internet exposure increases scanning and attack risk. Restrict firewall rules by source network even inside a VPN or private segment.<\/p>\n<\/details>\n<\/div>\n<h2 id=\"sources\">Sources<\/h2>\n<ul class=\"aiw-sources\">\n<li><a href=\"https:\/\/learn.microsoft.com\/en-us\/windows-server\/storage\/file-server\/file-server-smb-overview\" target=\"_blank\" rel=\"noopener\">Microsoft Learn &#8211; Server Message Block overview<\/a> \u2014 learn.microsoft.com<\/li>\n<li><a href=\"https:\/\/learn.microsoft.com\/en-us\/powershell\/module\/smbshare\/\" target=\"_blank\" rel=\"noopener\">Microsoft Learn &#8211; SmbShare PowerShell module<\/a> \u2014 learn.microsoft.com<\/li>\n<li><a href=\"https:\/\/learn.microsoft.com\/\" target=\"_blank\" rel=\"noopener\">Microsoft Learn &#8211; File Server documentation<\/a> \u2014 learn.microsoft.com<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Set up Windows Server file sharing with SMB, correct share and NTFS permissions, restricted TCP 445 access, client testing, monitoring, and verified backups.<\/p>\n","protected":false},"author":2,"featured_media":817,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6],"tags":[],"class_list":["post-819","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-windows"],"lang":"en","translations":{"en":819,"tr":818},"pll_sync_post":[],"_links":{"self":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts\/819","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/comments?post=819"}],"version-history":[{"count":2,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts\/819\/revisions"}],"predecessor-version":[{"id":825,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts\/819\/revisions\/825"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/media\/817"}],"wp:attachment":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/media?parent=819"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/categories?post=819"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/tags?post=819"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}