Embeded sessions cannot connect

Sorry forgot to mention, using version 5.5.0.2

Hi,
For the price, it's not in the planned to change for this year. For the connection issue, can you check if you get an error in the application log, it's located in the help menu. Also, can you try with the ip address or the machine name. I looking for clue because I really don't know. When you connect embedded, RDM use the Microsoft Active X and when you connect externally, it use mstsc.exe.

I will try to investigate for VNC, but can you tell me if you use UltraVNC externally, does it work ?

David Hervieux
Devolutions inc.

Hi,

My connection log of what i tried (intermitantly):

[6/23/2009 3:48:30 PM] Connecting to ANDROMEDA-2 (Microsoft Remote Desktop Host)
[6/23/2009 3:48:35 PM] Disconnected from ANDROMEDA-2 (Microsoft Remote Desktop Host)
[6/23/2009 3:48:56 PM] Connecting to ANDROMEDA-2 (Microsoft Remote Desktop Host)
[6/23/2009 3:48:56 PM] Disconnected from ANDROMEDA-2 (Microsoft Remote Desktop Host)
[6/23/2009 3:49:44 PM] Connecting to ANDROMEDA-2 (Microsoft Remote Desktop Host)
[6/23/2009 3:49:44 PM] Disconnected from ANDROMEDA-2 (Microsoft Remote Desktop Host)
[6/23/2009 3:50:44 PM] Connecting to ANDROMEDA-2 (Microsoft Remote Desktop Host)
[6/23/2009 3:50:45 PM] Disconnected from ANDROMEDA-2 (Microsoft Remote Desktop Host)
[6/23/2009 7:05:29 PM] Connecting to 192.168.27.16 (VNC)
[6/23/2009 7:06:01 PM] Disconnected from 192.168.27.16 (VNC)
[6/23/2009 7:06:13 PM] Connecting to 192.168.27.16 (VNC)
[6/23/2009 7:07:09 PM] Disconnected from 192.168.27.16 (VNC)

My error log:

System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: An attempt was made to access a socket in a way forbidden by its access permissions 72.167.232.95:80
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.InternalConnect(EndPoint remoteEP)
at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception)
--- End of inner exception stack trace ---
at System.Net.HttpWebRequest.GetResponse()
at Devolutions.Private.UpdateManager.DoCheckForUpdate()
at Devolutions.Private.UpdateManager.CheckForUpdate()System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: An attempt was made to access a socket in a way forbidden by its access permissions 72.167.232.95:80
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.InternalConnect(EndPoint remoteEP)
at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception)
--- End of inner exception stack trace ---
at System.Net.HttpWebRequest.GetResponse()
at Devolutions.Private.UpdateManager.DoCheckForUpdate()
at Devolutions.Private.UpdateManager.CheckForUpdate()System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: An attempt was made to access a socket in a way forbidden by its access permissions 72.167.232.95:80
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.InternalConnect(EndPoint remoteEP)
at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception)
--- End of inner exception stack trace ---
at System.Net.HttpWebRequest.GetResponse()
at Devolutions.Private.UpdateManager.DoCheckForUpdate()
at Devolutions.Private.UpdateManager.CheckForUpdate()System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: An attempt was made to access a socket in a way forbidden by its access permissions 72.167.232.95:80
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.InternalConnect(EndPoint remoteEP)
at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception)
--- End of inner exception stack trace ---
at System.Net.HttpWebRequest.GetResponse()
at Devolutions.Private.UpdateManager.DoCheckForUpdate()
at Devolutions.Private.UpdateManager.CheckForUpdate()

My Application log:
Info[6/23/2009 3:50 PM] Another instance found

From the Connection log, when connects it pretty much disconnects. From the error log, that is my firewall blocking the WAN (is normal) Machines that I connect to are on the LAN. Application log, had another std version running but otherwise it is blank. That std version is no longer present and RDM box has been rebooted.

Also have tried by name and IP with and without ports as required. Externally I have no issue, externally using mstsc.exe or ultraVNC (v1.0.5.6) vncviewer.exe or selecting Edit|Open|Open Session (External). Problem lies when Embeded is selected or Edit | Open Session or | Edit |Open Session (Embeded) is selected.

Hope this helps, If required I will setup so you remote access and we can go through it together...if it helps ( early next week?)

Regards,

H

Hi,
What I see in the error log is not related to the diconnection problem, you should disable in the option the Check For Update, this is the cause of this error. Can you tell me on what OS your try to connect ? Also is it possible to try the same configuration on a 32 bits ?

Thank you

David Hervieux
Devolutions inc.

Hi,

Odd, I do recall disabling "Check for update" in v5.5.0.2 and v5.5.0.3. I am aware this is the cause of the errors in the error log. Looks like the seting is not being saved.....another issue?. As for the OS,
using Vista Ultimate 64bit SP2 8GB on C2D 3.0 aka E8400, fully updated. As for trying 32bit, that I would have to do on the weekend and set up a box for that.

An additional note, when using uVNC, it say connected but do not see the password window. It is not buried behind any window. But when using uVNC externally, pwd window does show up in the task bar not in front of the VNCviewer window, when using RDM....another issue? Need to get any pwd dialog boxes to come to the front. This happens in both v5.5.0.2 and v5.5.0.3

Regards,

H

You connect from Vista 64 to another Vista 64 ?

David Hervieux
Devolutions inc.

Hi,
Checked for the auto update, you're right, it's an old bug. For the password window, it's harder, I don't have the control for this application (vncviewer.exe). Do you have an idea ?

David Hervieux
Devolutions inc.

no idea at all as to how to get a dialog box of and active window to come to the front, suspect it would be an OS issue?

Maybe you can check if the option "Always on top" is set to true. It's in the first tab of Remote Desktop Manager. Try to uncheck this settings. I didn't got the answer about : You connect from Vista 64 to another Vista 64 ?

Also for the embedded problem, an you try this special version

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

And set the debug level to 1 in the option. After that connect with RDP and check your application log, You should get the deconnection error code and maybe more info

David Hervieux
Devolutions inc.

using v5.5.0.4

When "Always on top" is selected, the main interface stays on top, if any dialog box come up the are in the back, unfortunately is is more of a hinderance (covers anything else). So left it unchecked.

Machines I ty to connect are Vista64-Vista 64 and Vista64-XPSP3 (all fully updated)

Debug Level? Sorry do not see it at all. Went to File|Option.....where to go from there, went through all tabs. Application Log is blank, this time update check box seems to stay off

v5.5.0.4 does allow me to embed uVNC but embeded machine is too big, sizing in window in pane is off. I think, interface, layout and sizing needs work but that I suggest to do later after all the connectivity issues are sorted.

As for MS Remote Desktop Session, still no luck same as v5.5.0.3 and v5.5.0.2

OK found the debug level setting.....took a bit...it is under File|Option|Advanced Tab

Error in Application Log is
Info[6/24/2009 10:38 AM] RDP - Disconnect:516

Maybe this will help? http://www.scribd.com/doc/2712802/Keeping-Up-With-Terminal-Services

It maybe a ActiveX related issue?

Not a programer, in case you are wondering.

Hi,
the error we have is described here: http://msdn.microsoft.com/en-us/library/aa382170(VS.85).aspx

It's a Window socket error :

disconnectReasonSocketConnectFailed

Do you know if something in the configuration can cause that ? Is it possible that your firewall reject Remote Desktop Manager connection ? For the VNC, I recompiled the library for 64 bits.

David Hervieux
Devolutions inc.

Great, we're finding ways to answers!

When I get back tonight, I'll have a look at the logs with all firewalls in place and again without.....will send you full logs from RDM and any relivant Firewall details.

For uVNC, im using the 64bit binaries from the uVNC site (http://www.uvnc.com/download/1055/) only the viewer http://www.uvnc.com/download/1055/1055viewer.html (X64)

H