RDM Crashes on unsuccessful VPN connection

Published 10 years ago

Admittedly I caused this, by killing the host entry in my DNS for the VPN site, but after running this

Executable: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
Opening Arguments: -WindowStyle hidden -command "C:\Shared\_0\JPTs\OpenVPN.cmd connect $VPN_HOST$ $VPN_USERNAME$ $VPN_PASSWORD$"
(This was the best I could do to avoid a DOS Window from opening -- it now just flashes open the closes)

with the following Timeouts:
Wait Interval: 30 sec
For IP on Adapter: RMxxxn_VPN-NIC_xxx.xxx.xxx.xxx-(SCxxxn) #4
Wait for maximum of: -1 sec Then delay: -1 ms
(so many timeouts, not sure which one to use)

The first 30 secs counted down, then RDM waited awhile, then stopped responding. Had to restart.

Sue

All Comments (6)

Erica Poirier

Published 10 years ago

Hello,

I have been able to reproduce your issue.

A ticket has been sent to our engineering department.

As a workaround, could you please try to set the After Execute Wait option to -1 sec. instead of using the For IP on Adapter option.

Best regards,

Érica Poirier

Hubert Mireault

Published 10 years ago

Hello,

We should have a fix for this in the next minor version of RDM. Thank you for the bug report!

Regards,

Hubert Mireault

mgoldweber

Published 6 years ago

Hello,

I'm using RDM Free, version 2020.1.20.064 bit on Windows 7. The program crashes when trying to use when I'm connected to the company network through VPN. Is there a work around or a setting I can change to fix this problem?

Thanks,
Mike Goldweber

Jeff Dagenais

Published 6 years ago

@Mike Goldweber,

Do you have something relevant in Event Viewer regarding those crashes?

Best regards,

Jeff Dagenais

mgoldweber

Published 6 years ago

Hi Jeff,

Yes, I did have Event Viewer logs for this. Here are the last two entries:

Faulting application name: RemoteDesktopManagerFree.exe, version: 2020.1.20.0, time stamp: 0x5e8e2b74
Faulting module name: ntdll.dll, version: 6.1.7601.24549, time stamp: 0x5e44cd8b
Exception code: 0xc0000374
Fault offset: 0x00000000000bf272
Faulting process id: 0x17f0
Faulting application start time: 0x01d61d95aff48f65
Faulting application path: C:\Program Files (x86)\Devolutions\Remote Desktop Manager Free\RemoteDesktopManagerFree.exe
Faulting module path: C:\windows\SYSTEM32\ntdll.dll
Report Id: c4727db5-898a-11ea-a26a-648099d367a5

Faulting application name: RemoteDesktopManagerFree.exe, version: 2020.1.20.0, time stamp: 0x5e8e2b74
Faulting module name: ntdll.dll, version: 6.1.7601.24549, time stamp: 0x5e44cd8b
Exception code: 0xc0000374
Fault offset: 0x00000000000bf272
Faulting process id: 0x17f0
Faulting application start time: 0x01d61d95aff48f65
Faulting application path: C:\Program Files (x86)\Devolutions\Remote Desktop Manager Free\RemoteDesktopManagerFree.exe
Faulting module path: C:\windows\SYSTEM32\ntdll.dll
Report Id: c4727db5-898a-11ea-a26a-648099d367a5

Please let me know if you need addition info. Thank you for helping me.

Best regards,
Mike Goldweber
mgoldweber@nsre.com

Jeff Dagenais

Published 6 years ago

Hello,

The faulting module path: C:\windows\SYSTEM32\ntdll.dll is deep in Windows and not associated directly to RDM.
Do you have something else in Event Viewer?

On a side note, I would suggest starting by performing a .Net repair and SFC Scannow as explained in this help article
https://help.remotedesktopmanager.com/troubleshooting_csf.html

Best regards,

Jeff Dagenais