R
R
RJ942017-11-07 08:23:27
Windows
RJ94, 2017-11-07 08:23:27

How to connect to a remote PC through a terminal server via RDP in one operation (win)?

Hello. Is it possible to somehow set up a standard RDP connection in win7 so that you can immediately get to a physical remote PC through a terminal server? How it works now: a user from home, via the regular Internet without any tunnels and private networks, launches mstsc (saved in a file on the desktop) and writes the address and port to connect to the terminal server. It gets to the terminal, starts mstsc again from the terminal and writes the name of your working PC there from the internal grid. And working. You can somehow exclude " runs mstsc again"and push it into the first shortcut of the saved connection right on the desktop of your home PC? There are no Linux, radmins and other things and it's unnecessary. I tried to register the executable program "mstsc / v:% PC-name%" in the shortcut settings, but it does not allow to execute, says that access is denied at runtime and see help.I repeat: if you already connect to the terminal and run "mstsc /v:%PC-name%" there, then everything is fine.

Answer the question

In order to leave comments, you need to log in

3 answer(s)
O
Oopss, 2017-11-07
@Oopss

On a remote router, forward the port to the "desired" computer, and it will connect immediately to the desired computer.

R
res2001, 2017-11-07
@res2001

1. mstsc has command line options that allow you to set the address and port of the server you are connecting to. But in fact, you just need to create an RDP file with the connection settings using the same mstsc, save the password once and then connect simply by double-clicking on the RDP file.
mstsc /? - for help
2. You can create a nested connection using the settings in the same RDP file on the Program tab - specify the command that will be executed when connecting to the server, this command will be mstsc with the appropriate parameters.
From some version of mstsc, Microsoft cut out the Program tab from the interface, but the ability to run the start command still remained - it was transferred to policies.

A
Artem @Jump, 2017-11-07
curated by the

Two solutions -

  • correct and safe is RDS deployment.
  • insecure but simpler, forward ports to the desired machines on the network, and make a shortcut directly to them.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question