Hidden Shares Are Not Available After You Use the System Policy Editor

Article translations Article translations
Article ID: 156365 - View products that this article applies to.
This article was previously published under Q156365
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

SYMPTOMS

Hidden shares are no longer available after you save changes with System Policy Editor in registry mode.

CAUSE

The value for the AutoShareServer parameter was replaced with the setting in System Policy Editor\Windows NT Network\Sharing\Create Hidden Drive Shares (server).

RESOLUTION

To resolve this problem you can edit the WINNT.ADM file or obtain Service Pack 3.
POLICY !!WorkstationShareAutoCreate
VALUENAME "AutoShareWks"
VALUEOFF NUMERIC 0
---->VALUEON  NUMERIC 1   <----
PART !!ShareWks_Tip1            TEXT    END PART
PART !!ShareWks_Tip2            TEXT    END PART
END POLICY

POLICY !!ServerShareAutoCreate
VALUENAME "AutoShareServer"
VALUEOFF NUMERIC 0
---->VALUEON  NUMERIC 1  <----
PART !!ShareServer_Tip1         TEXT    END PART
PART !!ShareServer_Tip2         TEXT    END PART
END POLICY
				

and for BeepEnabled, add the indicated line:
POLICY !!Beep_Enabled
VALUENAME BeepEnabled
VALUEOFF NUMERIC 0
---->VALUEON  NUMERIC 1   <----
PART !!Beep_Tip1TEXTEND PART
PART !!Beep_Tip2TEXTEND PART
END POLICY
				

Add the lines surrounded by, ----> <----, but leave those characters out.

-OR-

To correct this problem, manually set the following Local Computer Properties in System Policy Editor before saving changes to the registry:

Windows NT Network
   Sharing
      Create hidden drive shares (workstation)
      Create hidden drive shares (server)
				

Windows NT Printers
   Beep for error enabled
				

NOTE: You must manually set the Local Computer Properties mentioned above each time you save changes to the registry. Their check boxes will be blank (clear) each time you start System Policy Editor, unless you edit the WINNT.ADM file or obtain SP3.

STATUS

Microsoft has confirmed this to be a problem in Windows NT Server version 4.0. This problem was corrected in the latest U.S. Service Pack for Windows NT version 4.0. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):
S E R V P A C K

Properties

Article ID: 156365 - Last Review: February 28, 2014 - Revision: 2.1
APPLIES TO
  • Microsoft Windows NT Workstation 3.5
  • Microsoft Windows NT Workstation 3.51
  • Microsoft Windows NT Workstation 4.0 Developer Edition
  • Microsoft Windows NT Server 3.5
  • Microsoft Windows NT Server 3.51
  • Microsoft Windows NT Server 4.0 Standard Edition
Keywords: 
kbnosurvey kbarchive kbbug kbusage KB156365

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com