Problems with "connect if unable to ping" option
I have RD connections set up that require vpn access first. I have the "connect if unable to ping" option selected for my vpn which brings me to my vpn log in screen. I log in - and it continues on to connect to the rd.
I then close my RD session, but decide I want to connect to that same server again. On my end, I should not have to connect to my vpn again & log in - it keeps me logged in for 8 hours. However, when i connect to the server again - it tries to ping the RD IP, and it still brings up my vpn log in screen. I dont have to log in, though. If I just leave the log in screen up, the RD connection continues on & logs in. Its acting like its failing to ping - thus bringing up my vpn log in screen.
I can actually ping the server - so the pinging isn't the problem. Its just acting like it can't ping it.
I'm using a vista machine. It works fine for 2 other people in my office who are running xp & windows 7.
Any thoughts/help would be greatly appreciated!
All Comments (7)
Hi,
I have no idea what might be the problem, maybe the ping timeout is too short. Can you try to increase it, it's located in the advanced tab of the application options. You can also try to ping it within the application (not from command line) to see if you get an error.
Let me know
David Hervieux
Devolutions inc.
David Hervieux
Thanks for your quick response!
I tried pinging from the application and I'm getting DNS Error, unable to resolve the host name. I'm guessing there might be firewall issues if it can't ping through the applicatin but can through windows? I added the program to the allowed programs in windows firewall & tried running as an administrator, but Im still getting the error. I'm going to check with some people here in the office for some more firewall trouble shooting.
Hi,
Have you found something, maybe .NET and Windows does not resolve the dns the same way?
Let me know
David Hervieux
Devolutions inc.
David Hervieux
It appears that the RDM ping only supports host names, while windows ping supports IP addresses. I'm not sure if that's the OP's issue, but we're having that problem (Enterprise Edition 5.6.3.2). We use IP addresses for some things.
Thanks!
Drew
Example:
I try to ping 10.130.6.66 and I get:
Pinging 10.130.6.66 [208.69.36.132] with 32 bytes of data.
It must be treating my IP address as a hostname then trying to do the lookup or something?
edited by Drew on 12/1/2009
Hi,
Watch for the new beta to I will release in a few hour. I tried something, let me know if it works.
David Hervieux
Devolutions inc.
David Hervieux
Worked perfectly. And I found out who started this thread, she's a coworker! So I think it'll work for her too.
Thanks!
Great,
I was unable to find the solution until you gave me your details and I found a new way of resolving the host (when it's already an IP).
Thank you very much, I'm sure that it will be useful for many people.
David Hervieux
Devolutions inc.
David Hervieux