-
Products
-
SonicPlatform
SonicPlatform is the cybersecurity platform purpose-built for MSPs, making managing complex security environments among multiple tenants easy and streamlined.
Discover More
-
-
Solutions
-
Federal
Protect Federal Agencies and Networks with scalable, purpose-built cybersecurity solutions
Learn MoreFederalProtect Federal Agencies and Networks with scalable, purpose-built cybersecurity solutions
Learn More - Industries
- Use Cases
-
-
Partners
-
Partner Portal
Access to deal registration, MDF, sales and marketing tools, training and more
Learn MorePartner PortalAccess to deal registration, MDF, sales and marketing tools, training and more
Learn More - SonicWall Partners
- Partner Resources
-
-
Support
-
Support Portal
Find answers to your questions by searching across our knowledge base, community, technical documentation and video tutorials
Learn MoreSupport PortalFind answers to your questions by searching across our knowledge base, community, technical documentation and video tutorials
Learn More - Support
- Resources
- Capture Labs
-
- Company
- Contact Us
Enabling Post-Connection Scripts to Run Without User Intervention
03/26/2020 
10 People found this article helpful
505,105 Views
Description
Enabling Post-Connection Scripts to Run Without User Intervention
Resolution
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
- Run Group Policy on your local computer: in the Start > Run box, type gpedit.msc.
- In the Group Policy Editor, navigate to Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options.
- 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
- In the Group Policy Editor, navigate to Computer Configuration > Windows Settings > Security Settings > Local Policies > User Rights Assignment.
- Set Access this computer from the network to at least allow Everyone and anonymous logon.
- The guest account should be set with a blank password in Computer Management's Users and Groups.
- 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.
Related Articles
- How to download Client Installation package and the access agents from the appliance using WinSCP
- SMA 1000: How to update Advanced EPC Signatures to the Latest Version
- If OTP is enabled, NX disconnects after SMA100 Connect Agent installation
YES
NO