Windows 10: Remote Desktop

I have recently upgraded from 7 Ultimate to 10 Pro. When I RDP to another Windows 7 Ultimate machine the application randomly closes, no error messages or anything. Anyone seen this before?

:)

 

WINDOWS PHONE 7 INCLUDE Remote Desktop connection & wifi???

What are you doing about IRAPP
?

See here:
http://www.coderebel.com/products/irapp-terminal-server

 

How do I Remote Control my Windows Phone 8 from my Windows 8 PC?

you are mixing a few things. windows RT can remote desktop into OTHER computers that SUPPORT remote desktop. you cannot remote desktop INTO a windows RT machine.

likewise, there is a remote desktop app for windows phone - but it only works to connect to computers that support remote desktop. not to remote into the phone.

 

I have this issue but not a solution. I use RDP to connect to local Hyper-V VMs and it drops connection a lot - it never did on 8 or 8.1. At least in my case (as the VMs are on the same disk) it can't be network...

 

It is a glitch that has been around since Windows XP. That is the biggest reason why everyone started to use Team Viewer. The other is that Microsoft refuses to patch a huge security hole in RDP.

 

So why then did it work perfectly fine in 7, 8 and 8.1? What is the "glitch" and what is the solution?

 

It never worked fine with 7 & 8. The problem with 10, is that it is bringing a whole new set of headaches. The 10525 is sad to fix some things and break others, wen they roll it out in Oct.

 

Not sure about the glitch, but I am running 10 Pro (fresh install) and remote into several Win7 and 8.1 Pro machines for hours at a time and have not had any issues with RDP crashing and/or closing

 

Too true on new headaches.

I have my work pc here setup for RDP, ports set on router, logon, etc. All has been good, then all of a sudden from my laptop either on the net, or even on the LAN, getting windows security logon failed for it.

At the same time using my Nexus 6 running 2X client I RDP just fine thru wifi on same LAN, or thru VZW.

I'll sort that eventually, but these are the kind of things that drive you nuts.

 

Faulting application name: mstsc.exe, version: 10.0.10240.16384, time stamp: 0x559f3878
Faulting module name: ntdll.dll, version: 10.0.10240.16430, time stamp: 0x55c59f92
Exception code: 0xc0000005
Fault offset: 0x000000000002a901
Faulting process id: 0x2204
Faulting application start time: 0x01d10319b94e00da
Faulting application path: C:\WINDOWS\system32\mstsc.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 0738340a-2822-4bdb-bb21-f3d0cbb556b1
Faulting package full name:
Faulting package-relative application ID: