Sign in with
Sign up | Sign in
Your question

Having trouble getting RDP to work form android to Win 7

Tags:
  • Remote Desktop
  • Windows 7
  • Android
  • Networking
  • Remote Access
Last response: in Networking
Share
March 24, 2014 1:08:41 PM

I am connecting from a Galaxy SIII to Windows 7 Pro using the Microsoft RDP app for Android. It connects just fine when the wifi is enabled on my phone and I am connected to the local network. But when I disable wifi, trying to emulate a true remote connection, after I grant a security certificate exception ( which it asks me to do regardless of whether or not wi-fi is enabled on my phone) it gives me the error TLS1_ALERT_INTERNAL_ERROR.

It may be of note that I have entered the ID of the computer by IP and when it asks for the certificate exemption it has the correct computer name, so I know it is getting as to the computer, but it is not completing the connection.

Port forwarding has been set on the router for port 3389, firewall has been verified for port 3389.

Any ideas how to resolve this?

More about : trouble rdp work form android win

March 28, 2014 11:52:29 AM

thirdrev said:
I am connecting from a Galaxy SIII to Windows 7 Pro using the Microsoft RDP app for Android. It connects just fine when the wifi is enabled on my phone and I am connected to the local network. But when I disable wifi, trying to emulate a true remote connection, after I grant a security certificate exception ( which it asks me to do regardless of whether or not wi-fi is enabled on my phone) it gives me the error TLS1_ALERT_INTERNAL_ERROR.

It may be of note that I have entered the ID of the computer by IP and when it asks for the certificate exemption it has the correct computer name, so I know it is getting as to the computer, but it is not completing the connection.

Port forwarding has been set on the router for port 3389, firewall has been verified for port 3389.

Any ideas how to resolve this?


m
0
l
March 28, 2014 11:53:39 AM

I am having the exact same issue on my new Galaxy Note 3, been working on it for 5 hours, no luck yet.
m
0
l
!