Cisco VPNClient hangs from command line when connecting
Hi,
I'm trying to use Cisco's VPN client from the command line (DOS), to connect to a remote server.
I use a command line such as:
vpnclient connect "my connection" user myuser pwd mypassword
It all seems to work fine, except after connecting, it never returns back to the DOS prompt. The last thing it says is "Local LAN Access is disabled".
At this point, I am able to access the server, via file shares, so I know that it's connected.
But, I need it to return to the DOS prompt so that I can include it in a batch file. How can I make it do this?
I'm trying to use Cisco's VPN client from the command line (DOS), to connect to a remote server.
I use a command line such as:
vpnclient connect "my connection" user myuser pwd mypassword
It all seems to work fine, except after connecting, it never returns back to the DOS prompt. The last thing it says is "Local LAN Access is disabled".
At this point, I am able to access the server, via file shares, so I know that it's connected.
But, I need it to return to the DOS prompt so that I can include it in a batch file. How can I make it do this?
ASKER
How do I store the user and pwd on the profile?
In the Windows interface, a different username and password is shown to that which I pass in the command line. If I change the shown login to the command line one, it doesn't connect even through the Windows interface.
Usually, I double-click in the Windows interface the connection, and it then prompts for the login which I pass in the command line. That then connects me. Not sure why there's 2 logins, but it seems to require them both.
In the Windows interface, a different username and password is shown to that which I pass in the command line. If I change the shown login to the command line one, it doesn't connect even through the Windows interface.
Usually, I double-click in the Windows interface the connection, and it then prompts for the login which I pass in the command line. That then connects me. Not sure why there's 2 logins, but it seems to require them both.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I do not know the difference, but there is one, since the latter will output more info and wait. The former works because user and password are stored in the profile, which is write-protected to prevent any change like password removal by the VPN client on connect ;-).