I used the RUN(Rasdial...) command to connect to a remote server; is there any way I can test the connection after the command is issued to see if the connection has been made?

Try pinging some server (Ping)

By the way, why don't you use RASDial statement?

: I used the RUN(Rasdial...) command to connect to a remote server; is there
: any way I can test the connection after the command is issued to see if
: the connection has been made?

: Try pinging some server (Ping)

: By the way, why don't you use RASDial statement?

hmm...
Converting functionality from Windows scheduler, using the rasdial.exe; one of those "if it works, don't mess with it" things. Having glanced at the RAS commands available in 24x7, though, I'd rather use those than start a seperate process.

Thanks!

I believe the change is minimal
RASDial instead of Run "rasdial.exe"
and
RASHangup at the end when done rather than kill the "rasdial.exe"

Also please note that RASDial statement is synchronous, meaning that it does not return the control until the connection is established of failed so you don't have to loop and wait and check for it.

BTW, there is an answer in another message thread, for your question about what was changed in v3.1.2

: hmm...
: Converting functionality from Windows scheduler, using the rasdial.exe; one
: of those "if it works, don't mess with it" things. Having
: glanced at the RAS commands available in 24x7, though, I'd rather use
: those than start a seperate process.

: Thanks!