forked from docs/doc-exports
zhangyue
5da982a576
Reviewed-by: Muller, Martin <martin.muller@t-systems.com> Co-authored-by: zhangyue <zhangyue164@huawei.com> Co-committed-by: zhangyue <zhangyue164@huawei.com>
29 lines
5.4 KiB
HTML
29 lines
5.4 KiB
HTML
<a name="sfs_01_0063"></a><a name="sfs_01_0063"></a>
|
|
|
|
<h1 class="topictitle1">Failed to Access the Shared Folder in Windows</h1>
|
|
<div id="body1577756761595"><div class="section" id="sfs_01_0063__section41158684111639"><h4 class="sectiontitle">Symptom</h4><p id="sfs_01_0063__p54895391161045">When you mount a file system to an ECS running Windows, the system displays a message "You cannot access this shared folder because your organization's security policies block unauthenticated guest access. These policies help to protect you PC from unsafe or malicious devices on the network."</p>
|
|
</div>
|
|
<div class="section" id="sfs_01_0063__section31326994111720"><h4 class="sectiontitle">Possible Causes</h4><p id="sfs_01_0063__p13813183613562">Guest access to CIFS file systems is blocked or disabled.</p>
|
|
</div>
|
|
<div class="section" id="sfs_01_0063__section34776262111735"><h4 class="sectiontitle">Fault Diagnosis</h4><p id="sfs_01_0063__p5670333819385">Solution 1: Manually enable guest access.</p>
|
|
<p id="sfs_01_0063__p72361020194512">Solution 2: Modify the registry to allow guest access (suitable for versions later than Windows Server 2016).</p>
|
|
</div>
|
|
<div class="section" id="sfs_01_0063__section28103453161025"><h4 class="sectiontitle">Solution</h4><p id="sfs_01_0063__p178661734161319"><strong id="sfs_01_0063__b781212664918">Solution 1: Manually enable guest access.</strong></p>
|
|
<ol id="sfs_01_0063__ol151849420578"><li id="sfs_01_0063__li132511139143"><span>Open <strong id="sfs_01_0063__b182911119113">Run</strong> command box, enter <strong id="sfs_01_0063__b1829831171116">gpedit.msc</strong>, and press <strong id="sfs_01_0063__b15835112612110">Enter</strong> to start <strong id="sfs_01_0063__b16299171181117">Local Group Policy Editor</strong>.</span><p><div class="fignone" id="sfs_01_0063__fig6411524192918"><span class="figcap"><b>Figure 1 </b>Entering gpedit.msc</span><br><span><img id="sfs_01_0063__image74485417289" src="en-us_image_0000001567076805.png"></span></div>
|
|
</p></li><li id="sfs_01_0063__li10489519559"><span>On the <strong id="sfs_01_0063__b316985091211">Local Group Policy Editor</strong> page, choose <strong id="sfs_01_0063__b1050145713128">Computer Configuration</strong> > <strong id="sfs_01_0063__b1251515101316">Administrative Templates</strong>.</span><p><div class="fignone" id="sfs_01_0063__fig028718275419"><span class="figcap"><b>Figure 2 </b>Local Group Policy Editor</span><br><span><img id="sfs_01_0063__image11819235911" src="en-us_image_0000001567316461.png"></span></div>
|
|
</p></li><li id="sfs_01_0063__li31481068143"><span>Under <strong id="sfs_01_0063__b14194145201410">Administrative Templates</strong>, choose <strong id="sfs_01_0063__b1925495318144">Network</strong> > <strong id="sfs_01_0063__b107251259151412">Lanman Workstation</strong> and find the option of <strong id="sfs_01_0063__b1448431716155">Enable insecure guest logons</strong>.</span><p><div class="fignone" id="sfs_01_0063__fig11864175522717"><span class="figcap"><b>Figure 3 </b>Locating the option</span><br><span><img id="sfs_01_0063__image46243434272" src="en-us_image_0000001515917384.png"></span></div>
|
|
</p></li><li id="sfs_01_0063__li1433113582815"><span>Double-click <strong id="sfs_01_0063__b65933441617">Enable insecure guest logons</strong>. Select <strong id="sfs_01_0063__b842352706135856">Enabled</strong> and click <strong id="sfs_01_0063__b84235270613590">OK</strong>.</span><p><div class="fignone" id="sfs_01_0063__fig2121419121217"><span class="figcap"><b>Figure 4 </b>Enabling insecure guest logons</span><br><span><img id="sfs_01_0063__image2783117388" src="en-us_image_0000001516076964.png"></span></div>
|
|
</p></li><li id="sfs_01_0063__li917313308147"><span>After the access is enabled, mount the file system again. If the fault persists, contact technical support.</span></li></ol>
|
|
<p id="sfs_01_0063__p1813214520133"><strong id="sfs_01_0063__b15909174024918">Solution 2: Modify the registry to allow guest access (suitable for versions later than Windows Server 2016).</strong></p>
|
|
<ol id="sfs_01_0063__ol189371562138"><li id="sfs_01_0063__li20433184204620"><span>Choose <strong id="sfs_01_0063__b355059104120">Start</strong> > <strong id="sfs_01_0063__b155110904117">Run</strong> and enter <strong id="sfs_01_0063__b115511892419">regedit</strong> to open the registry.</span></li><li id="sfs_01_0063__li1043314194613"><span>Go to the <strong id="sfs_01_0063__b2019471218504">HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters</strong> directory.</span><p><div class="fignone" id="sfs_01_0063__fig16151714339"><span class="figcap"><b>Figure 5 </b>Entering the registry</span><br><span><img id="sfs_01_0063__image46151074331" src="en-us_image_0000001567396721.png"></span></div>
|
|
</p></li><li id="sfs_01_0063__li09271511153415"><span>Right-click <strong id="sfs_01_0063__b19755152715529">AllowInsecureGuestAuth</strong> and choose <strong id="sfs_01_0063__b127471518125212">Modify</strong> from the shortcut menu. In the pop-up window, change the value to <strong id="sfs_01_0063__b104221349145219">1</strong>.</span><p><div class="fignone" id="sfs_01_0063__fig13530735204112"><span class="figcap"><b>Figure 6 </b>Changing the value</span><br><span><img id="sfs_01_0063__image75309357411" src="en-us_image_0000001516236536.png"></span></div>
|
|
</p></li></ol>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="sfs_01_0056.html">Troubleshooting</a></div>
|
|
</div>
|
|
</div>
|
|
|