Post-Connection Script Fails to Run with Connect Tunnel
When using a post-connection script available from a file share (for example, \sharescript.bat) with Connect Tunnel, the script doesn't launch once the tunnel has been established.
The reason the script may not work is because Connect Tunnel is not able to add a route quickly enough for the system to connect to the backend file share server.
Connect Tunnel and OnDemand Tunnel typically add routes to servers when the server is accessed by a user. When a host resource has been created on the appliance and is accessed for the first time, the tunnel client adds a route to the server when the tunnel is established. This process takes a litle time; to ensure that the system can connect to the back-end server quickly, create a host resource for that server in AMC.