Open VPN 'Connect if unable to ping/scan' doesn't run before connect event.

Open VPN 'Connect if unable to ping/scan' doesn't run before connect event.

avatar

RDM Enterprise 12.0.8.0

SQL data source 1.284

I have an RDP connection with the following config

General > Computer > 192.168.80.1

VPN > Open > Inherited

Parent group 'Physical Servers'

VPN > Open > Inherited

Parent group 'Emerald'

VPN > Open > Connect if unable to ping/scan

VPN > Type > Session

VPN > Settings > Session with session entry specified

VPN connection

Credentials > Credential repository with entry specified

VPN Type > Microsoft VPN

VPN name VPN1

RAS phone number 'VPN IP address specified'

Phonebook document > Phonebook entry specified

Events > Before Connect > Command line > Command: C:\Windows\System32\rasdial.exe VPN1 /disconnect

we have multiple vpn's all called VPN1 so we do not have to update the phonebook document, we just specify the IP in the RAS phone number field.

The remote networks all have different ip range, eg 192.168.50.0, 192.168.80.1 and so on

and I have confirmed if I ping 192.168.80.1 I get request timed out

When I open the RDP session

I am prompted pinging host 192.168.80.1

then pinging host for vpn connection

then connecting to 192.168.80.1 with the rotating dots before being prompted with a Connection box

I enabled the performance profiling debug log and I don't know if it is because I specified the wrong options with debug level 2369 but the log goes crazy Tree view is loading 1936 connections: when I click connect on the RDP entry Loading connections before stopping and showing:

OpenConnection: Opening VPN

OpenVPN: Finding Opener

OpenVPN: Preparing Dynamic Port

OpenVPN: vpnOpener.Open

OpenVPN: Result is Not Null

OpenVPN: Result is not opened or is ready

OpenConnection: Opened VPN

Opening in Console / Admin mode

Remote Desktop can’t connect to the remote computer for one of these reasons:

1) Remote access to the server is not enabled

2) The remote computer is turned off

3) The remote computer is not available on the network

Make sure the remote computer is turned on and connected to the network, and that remote access is enabled.

RDP - Disconnect:516 / exDiscReasonNoInfo

Remote Desktop can’t connect to the remote computer for one of these reasons:

1) Remote access to the server is not enabled

2) The remote computer is turned off

3) The remote computer is not available on the network

Make sure the remote computer is turned on and connected to the network, and that remote access is enabled.

RDP - Disconnect:516 / exDiscReasonNoInfo

It does not seem to run the before connect command or open the vpn

I have sent the trace to support if it is of any help.

All Comments (3)

avatar

Hello Paul,

I send you a additional question by email. I will post the results of our test here after received your answer.

Best Regards,

David Grandolfo

avatar

Hi David

Part of this issue is related to a previous ticket I raised that was never resolved.

https://forum.devolutions.net/topic26930-rdp-session-not-reconnecting-vpn-when-unable-to-ping.aspx

I replied to your email did you receive it?

avatar

Hello Paul,

I'm really sorry to see that your old post wasn't updated. I just send you multiple questions by email. If with these questions I didn't find the problem, could we schedule a go-to-meeting call together ? So after your answer I will send you an email with my calendar information to schedule a date for you.

Best regards,

David Grandolfo