How to setup remote debugging on a remote desktop computer
-
Hi all, I want to setup remote debugging on a remote desktop computer. I got i working on a local network but i can't get it work on a remote desktop connection. I connect to a computer via remote desktop using MSTSC.exe running in adminstrator mode but when i can not attach a process on remote desktop computer because it can't find the computer. There are youtube videos explaining on how to remote debug but i can not find any info on how to set it up when connecting via remote desktop. For testing purpuses i have opened a big range of ports on my router but still cannot find the computer to attach a process. I can get access to the remote desktop computer and login as you would normally do but not via visual studio 2012 to attach to a process on that remote desktop computer. Can anyone help me please. Thanks
-
Hi all, I want to setup remote debugging on a remote desktop computer. I got i working on a local network but i can't get it work on a remote desktop connection. I connect to a computer via remote desktop using MSTSC.exe running in adminstrator mode but when i can not attach a process on remote desktop computer because it can't find the computer. There are youtube videos explaining on how to remote debug but i can not find any info on how to set it up when connecting via remote desktop. For testing purpuses i have opened a big range of ports on my router but still cannot find the computer to attach a process. I can get access to the remote desktop computer and login as you would normally do but not via visual studio 2012 to attach to a process on that remote desktop computer. Can anyone help me please. Thanks
If it works on the LAN, but not to the outside, then there is probably some firewall blocking the connection.
Marlon100 wrote:
For testing purpuses i have opened a big range of ports
You'll need port 135 (TCP). (Source[^])
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^][](X-Clacks-Overhead: GNU Terry Pratchett)
-
If it works on the LAN, but not to the outside, then there is probably some firewall blocking the connection.
Marlon100 wrote:
For testing purpuses i have opened a big range of ports
You'll need port 135 (TCP). (Source[^])
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^][](X-Clacks-Overhead: GNU Terry Pratchett)
Thanks for your reply. i have to give some more info about de remote computer. It is a windows server running virtual session with hyper-v. I connect this computer via a remote desktop connection and the computername is somthing like: 95.128.4.19:33920. By the way i have forwarded ports 100 to 8000 just for testing on the router. In visual studio 2012 i cannot attach to a process on that machine because it can't find 95.128.4.19:33920.
-
Thanks for your reply. i have to give some more info about de remote computer. It is a windows server running virtual session with hyper-v. I connect this computer via a remote desktop connection and the computername is somthing like: 95.128.4.19:33920. By the way i have forwarded ports 100 to 8000 just for testing on the router. In visual studio 2012 i cannot attach to a process on that machine because it can't find 95.128.4.19:33920.
Can you ping the remote computer if you use only the IP-address? I think that the port would be blocked on the server; I don't think these are available over the internet by default.
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^][](X-Clacks-Overhead: GNU Terry Pratchett)