XPost: alt.comp.os.windows-10, alt.comp.os.windows-11   
   From: jj4public@outlook.com   
      
   On Thu, 30 Mar 2023 11:48:33 -0400, Andy Burnelli wrote:   
   >   
   > The problem as I see is it that there's _nothing_ you can do inside the   
   > command window that is connecting to the VPN service other than kill it.   
   >   
   > I must make it clear if you've never done it (although I thought it was   
   > obvious - so that's my mistake) that you run the command and up pops   
   > a window but there's _nothing_ you can do _in_ that window anymore.   
   >   
   > All you can do is control-C (or more gracefully, F4) that command window.   
   >   
   > If it works - you control-C (or more gracefully, F4) out when you want.   
   > If it fails - you control-C (or more gracefully, F4) out of that failure.   
      
   If all you can do is hitting CTRL+C or F4 even when it fails, it would mean   
   that, the VPN profile/setting is configured to retry connection error   
   indefinitely (either by software default, or set manually).   
      
   In order to differentiate between success result and failed result, the VPN   
   profile/setting should be configured not to retry indefinitely. So that, if   
   it fails (after a number of limited retries), it'll terminates itself. And   
   the next line in the batch file will only be executed when the connection   
   has failed. If it succeeds on making connection, then it'll never terminates   
   and the next line in the batch file will never be executed (without user   
   intervention).   
      
   There's one connection settings command line switch which involve connection   
   retry which is set to `infinite` by default:   
      
   --resolv-retry   
      
   That will prevent the program to never terminate when it fails to resolve   
   server name.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)