Hi
I have found a problem with Shrew Soft VPN and "After execute wait" - "for ip on adapter"
The setup is as follows
An RDP-connection is setup to open the vpn (existing VPN-session).
The vpn is setup to wait for ip on the adaptername given.
I start the RDP-connection.
The vpn is launched and connects.
The adaptername is detected.
ERROR The RDP-connection fails.
Now I add TIMEOUT /T 10 as an After connect command
I start the RDP-connection.
The vpn is launched and connects.
The adaptername is detected.
The TIMEOUT starts counting down in a dos-window
ERROR The RDP-connection fails.
The TIMEOUT finishes countingdown and closes the dos window.
It seems to me that the after connect commands are launched in separate process.
Connection sequences must be launched synchronosly, especially if the purpose is to have a delay or to add static routes since they have to be in place before the vpn connection is utilized by the calling rdp.
I have not yet confirmed if this bug is limited to the shrew soft VPN or if it is general in the "After execute wait" module.
See attached screenshot.
/Magnus
edited by magpet on 11/14/2013
2013-11-14 17-58-59.jpg
2013-11-14 17-32-54.jpg
2013-11-14 18-01-20.jpg
This is a tricky one because sometime we use the after command to send some keystroke to the VPN dialog. I think that I could add a setting to make it sequential.
David Hervieux
Hi
Well, the problem is that the rdp connection continues right away without waiting for the after commands and I can't see that it ever should do that, should it?
BTW, out of curiosity, what keystroke commands do you send?
/Magnus
Some VPN does not allow us to send the password, so we use the after command to send the username and password.
David Hervieux