RDP Port, Alternate Host (Auto detect ping)

RDP Port, Alternate Host (Auto detect ping)

avatar

Hey guys

I've found a bug in version 7.0.2.0 nad 7.0.3.0. The following scenarion. We have definied the main RDP addresse as example server.domain.lan (default rdp port) and under the option "more">"alternate hosts" we've definied the public adress as server01.url.com:33895, "auto detect (ping)".

Now if RDM want to connect to the alternate address it doesen't add the port (33895). If we set it to "autodetect (port scan)" all things works well. In the version 6.0 both of them (ping and port scan) worked in the same way. I think it must be a bug in the new version. Could you validate this?

Thx for your help.

All Comments (11)

avatar

Hi,
I tried to reproduce but I'm not sure if I did the right thing. Ping does not support a port, so I don't understand why this was working in the previous version. If you try to ping it from Cmd, does it work without the port?

David Hervieux

avatar

Hi David

I won't ping the port. I try to explain it in an other way.

We use under "General">"connection" the URL (as example) SRV01.contoso.lan and we use under "more">"alternate hosts" the URL customer.domain.com:33893. In the earlier version the ping check, checked only the first URL (in this example SRV01.contoso.com) if this URL wasn't avialable it connected to the URL under "more">"alternate hosts". The new Version don't ping the default URL, it pings everytime the URL under "more">"alternate hosts". And that isn't possible because the port.

Maybe you could talk with the App programmer. I think he changed something in this part of the App. If we know it's not a bug, it's a new fuction ;-) we could change our connections to port check. But we have to be sure it works now in that way, because it's a lot of work to change 500 connections.

Greets Kilian

avatar

Hi,
Thank you for the clarification. I think that I've found the bug. Could you try this new internal release?

http://remotedesktopmanager.com/download/Devolutions.RemoteDesktopManager.Bin.7.0.4.0.zip

David Hervieux

avatar

Hi David

Wow, that's fast :-). It works now, thank you so much. That's a great support!

Kilian

avatar

Hi,
this is not working for me.
I entered under Gerneral the local IP and under alternate hosts the IP (with and without :3389) and get a connectionerror.
when I connect to the alternate IP with RDP I get a connection, also with port scanning I get the connection (but I have to wait for the port scan timeout)
I have already "installed" version 7.0.4.0

best regards
Tobias

avatar

Hi,
You need to download the version 7.0.4.0 again. I just have updated the binaries and if you haven't downloaded it this morning, you don't have the fix. Make sure that you don't download the cached version.

David Hervieux

avatar

Hi,
I have downloaded it for about 10 minutes, but I try again.
edit: same error :( is it important that the alternate hosts is reachable through ping? in my case ping to the hosts isn't allowed by the firewall!
edited by schiesslt on 4/2/2012

best regards
Tobias

avatar

Hi,
Ping is the only way for us to detect the host. Do you have another idea?

David Hervieux

avatar

Hi,
is there the possibility to add a checkbox, that to the alternate host would be connected without a ping test?
E.g.: ping on the "general" host -> not reachable -> connect without any check to the alternate host (makes sense when only one alternate host is configured)

best regards
Tobias

avatar

I see what you mean but you could also select the option to prompt for the host on connect. Will this help you?

David Hervieux

avatar

Yes it would help, but is not such comfortable ;)
But I see that it is not really important to have this function.

best regards
Tobias