Enabling Post-Connection Scripts to Run Without User Intervention

Overview

This article describes the steps necessary for setting up a Windows 2003 server for unauthenticated file share access so that Connect/OnDemand tunnel client post-connection scripts will run on computers that are not logged into a domain.  When you define a post-connection script by UNC (\serversharescript.bat, for instance), Connect Tunnel and OnDemand Tunnel will attempt to run that script, but a Windows system will not prompt the user to authenticate to the share.  The result is that the script will not run.  The following procedure will describe how to set up the fileserver for unauthenticated access so that users can still run this script even if their system is not logged into a domain.

NOTE: The following procedure should be validated against your own security policy.

Assumptions

• A file share has been configured and enabled on a Windows 2003 server
• The post-connection script UNC (for example, \serversharescript.bat) has been configured in the community to which users will log in.

Procedure

1. Run Group Policy on your local computer: in the Start > Run  box, type gpedit.msc. 
2. In the Group Policy Editor, navigate to Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options.
3. The following options should be set as follows:
   • Accounts: Guest account status: enabled
   • Network Access: Allow anonymous SID/Name translation: disabled
   • Network Access: Do not allow anonymous enumeration of SAM accounts: enabled
   • Network Access: Do not allow anonymous enumeration of SAM accounts and shares: disabled
   • Network Access: Let Everyone permissions apply to anonymous users: enabled
   • Network Access: Restrict remote access to named pipes and shares: disabled
4. In the Group Policy Editor, navigate to Computer Configuration > Windows Settings > Security Settings > Local Policies > User Rights Assignment.
5. Set Access this computer from the network to at least allow Everyone and anonymous logon.
6. The guest account should be set with a blank password in Computer Management's Users and Groups.
7. Users who attempt to access a share that's been set up with access for everyone will no longer be prompted for credentials.

More Information

This information was obtained from this web site.