那些遇到过的问题

如何指定 RDP 响应的端口？

Ken*_*rav 5 remote-desktop cygwin port-forwarding ssh-tunnel reverse-tunnel

我需要想办法强制RDP（远程桌面）响应特定端口而不是 RHP（随机高端口）。我不是在问如何更改RDP“侦听”端口，而是相反。

我正在尝试SSH在两个系统之间建立一个实验性的正​​向/反向隧道。我使用第三个系统作为枢轴点来隐藏我在转发隧道上的 IP。但我希望我通过转发 SSH 隧道远程进入的系统通过单独的反向SSH隧道将响应发送到“指定”端口而不是 RHP。基本思想是我希望能够控制我想要侦听和/或接收的端口，并且我不希望任何事情都是随机的。话虽如此，这是我设置的快照。

编辑：图像中的所有 IP 地址都已更改，这将使您稍后阅读我编辑到问题中的日志时感到困惑。新的 IP 地址是：

  • KGRAVES - 10.0.10.113
  • 恶魔之光 - 10.0.10.121
  • 杜克劳 - 10.0.10.120

在此处输入图片说明

正如您在最后一步所看到的，我的RDP会话SSH正像我想要的那样通过反向隧道发送回。所以我的RDP会话有两个管道。但它是在 RHP 上发回的，我不知道如何告诉它将它发送到特定端口，:44444例如。

有谁知道如何做到这一点？

我需要以特定方式完成此操作。这些是我必须使用的端口。我已经设置Duclaw监听RDP端口1337而不是3389. 我知道这绝不是最简单的方法。

我需要远程桌面连接“出现”，就好像它来自devilsmilk. 但我想duclaw直接将响应发送回，kgraves-pc而无需通过devilsmilk. 因此，为了kgraves-pc在RDP会话被发送到localhost其随后经由转发ssh隧道通过devilsmilk向duclaw，但RDP其响应于该连接被接收的分组是直接从接收到的Duclaw。

我的命令如下，除了我从另一个终端执行的连接之外，所有命令都是从完全相同的CYGWIN ssh控制台执行的：kgraves-pcmstscCYGWINkgraves-pc

CNO\kgraves@KGRAVES ~
$ ssh -vg -L 3333:localhost:6666 misfitred@devilsmilk
OpenSSH_6.1p1, OpenSSL 1.0.1c 10 May 2012
debug1: Reading configuration data /etc/ssh_config
debug1: Connecting to devilsmilk [10.0.10.121] port 22.
debug1: Connection established.
debug1: identity file /home/kgraves/.ssh/id_rsa type 1
debug1: identity file /home/kgraves/.ssh/id_rsa-cert type -1
debug1: identity file /home/kgraves/.ssh/id_dsa type -1
debug1: identity file /home/kgraves/.ssh/id_dsa-cert type -1
debug1: identity file /home/kgraves/.ssh/id_ecdsa type -1
debug1: identity file /home/kgraves/.ssh/id_ecdsa-cert type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.3
debug1: match: OpenSSH_5.3 pat OpenSSH_5*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.1
key_read: uudecode devilsmilk ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAwVZRlnAgPRPxTx           cbTPALg5XPpOnAMhJabQ3Dv/7a95eqe5l7XnKRciYQZ41B61DRgXCzC/M9ObknMR79zG0mkSl+jQTGJ7           klol7nw0+U1dNFknv4fOn+YGAsqECclWEow3OK5xRcla5eBekRGWjrZ7Wbs4F3FeKGQNqU/OuGvdSaQb           3nqgLPGTZfRhNtykQvpNzXw5cjO7XvM0BBv9di4JblLx9Fk3iq2KwdgWmK9uFDPYjU1gkHR8hk+bns1t           16KFcyDKnzhR1CblU6JT/wlBtnFa11no1UJBEHC2UQy8trwkMU6NqUt0X+D/XqW5F6+uWNc/dY97CCky           9HdfWNGQ==
 failed
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr hmac-md5 none
debug1: kex: client->server aes128-ctr hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Server host key: RSA b5:d6:eb:64:50:2f:40:04:32:10:bb:4f:a8:d3:f5:37
key_read: uudecode devilsmilk ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAwVZRlnAgPRPxTx           cbTPALg5XPpOnAMhJabQ3Dv/7a95eqe5l7XnKRciYQZ41B61DRgXCzC/M9ObknMR79zG0mkSl+jQTGJ7           klol7nw0+U1dNFknv4fOn+YGAsqECclWEow3OK5xRcla5eBekRGWjrZ7Wbs4F3FeKGQNqU/OuGvdSaQb           3nqgLPGTZfRhNtykQvpNzXw5cjO7XvM0BBv9di4JblLx9Fk3iq2KwdgWmK9uFDPYjU1gkHR8hk+bns1t           16KFcyDKnzhR1CblU6JT/wlBtnFa11no1UJBEHC2UQy8trwkMU6NqUt0X+D/XqW5F6+uWNc/dY97CCky           9HdfWNGQ==
 failed
The authenticity of host 'devilsmilk (10.0.10.121)' can't be established.
RSA key fingerprint is b5:d6:eb:64:50:2f:40:04:32:10:bb:4f:a8:d3:f5:37.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'devilsmilk' (RSA) to the list of known hosts.
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: Roaming not allowed by server
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,password,keyboard-interacti           ve
debug1: Next authentication method: publickey
debug1: Offering RSA public key: /home/kgraves/.ssh/id_rsa
debug1: Authentications that can continue: publickey,password,keyboard-interacti           ve
debug1: Trying private key: /home/kgraves/.ssh/id_dsa
debug1: Trying private key: /home/kgraves/.ssh/id_ecdsa
debug1: Next authentication method: keyboard-interactive
Password:
debug1: Authentication succeeded (keyboard-interactive).
Authenticated to devilsmilk ([10.0.10.121]:22).
debug1: Local connections to *:3333 forwarded to remote address localhost:6666
debug1: Local forwarding listening on :: port 3333.
debug1: channel 0: new [port listener]
debug1: Local forwarding listening on 0.0.0.0 port 3333.
debug1: channel 1: new [port listener]
debug1: channel 2: new [client-session]
debug1: Requesting no-more-sessions@openssh.com
debug1: Entering interactive session.
Last login: Wed Jan 30 16:13:02 2013 from kgraves.cno.local
[misfitred@devilsmilk ~]$ ssh -vg -L 6666:localhost:1337 kgraves@duclaw
OpenSSH_5.3p1, OpenSSL 1.0.0-fips 29 Mar 2010
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Connecting to duclaw [10.0.10.120] port 22.
debug1: Connection established.
debug1: identity file /home/misfitred/.ssh/id_rsa type 1
debug1: Remote protocol version 2.0, remote software version OpenSSH_6.1
debug1: match: OpenSSH_6.1 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_5.3
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr hmac-md5 none
debug1: kex: client->server aes128-ctr hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host 'duclaw' is known and matches the RSA host key.
debug1: Found key in /home/misfitred/.ssh/known_hosts:3
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,password,keyboard-interacti           ve
debug1: Next authentication method: publickey
debug1: Offering public key: /home/misfitred/.ssh/id_rsa
debug1: Authentications that can continue: publickey,password,keyboard-interacti           ve
debug1: Next authentication method: keyboard-interactive
debug1: Authentications that can continue: publickey,password,keyboard-interacti           ve
debug1: Next authentication method: password
kgraves@duclaw's password:
debug1: Authentication succeeded (password).
debug1: Local connections to *:6666 forwarded to remote address localhost:1337
debug1: Local forwarding listening on 0.0.0.0 port 6666.
debug1: channel 0: new [port listener]
debug1: Local forwarding listening on :: port 6666.
debug1: channel 1: new [port listener]
debug1: channel 2: new [client-session]
debug1: Requesting no-more-sessions@openssh.com
debug1: Entering interactive session.
debug1: Sending environment.
debug1: Sending env LANG = en_US.UTF-8
Last login: Wed Jan 30 15:55:29 2013 from devilsmilk.cno.local
"tty" option detected in CYGWIN environment variable.
CYGWIN=tty is no longer supported.  Please remove it from your
CYGWIN environment variable and use a terminal emulator like mintty,
xterm, or rxvt.

kgraves@DUCLAW ~
$ ssh -vg -R 3333:devilsmilk:6666 kgraves@kgraves
OpenSSH_6.1p1, OpenSSL 1.0.1c 10 May 2012
debug1: Reading configuration data /etc/ssh_config
debug1: Connecting to kgraves [10.0.10.113] port 22.
debug1: Connection established.
debug1: identity file /home/kgraves/.ssh/id_rsa type 1
debug1: identity file /home/kgraves/.ssh/id_rsa-cert type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_6.1
debug1: match: OpenSSH_6.1 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.1
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr hmac-md5 none
debug1: kex: client->server aes128-ctr hmac-md5 none
debug1: sending SSH2_MSG_KEX_ECDH_INIT
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ECDSA de:1c:37:d7:84:0b:f8:f9:5e:da:11:49:57:4f:b8:f1
debug1: Host 'kgraves' is known and matches the ECDSA host key.
debug1: Found key in /home/kgraves/.ssh/known_hosts:3
debug1: ssh_ecdsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: Roaming not allowed by server
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,password,keyboard-interacti           ve
debug1: Next authentication method: publickey
debug1: Offering RSA public key: /home/kgraves/.ssh/id_rsa
debug1: Authentications that can continue: publickey,password,keyboard-interacti           ve
debug1: Next authentication method: keyboard-interactive
debug1: Authentications that can continue: publickey,password,keyboard-interacti           ve
debug1: Next authentication method: password
kgraves@kgraves's password:
debug1: Authentication succeeded (password).
Authenticated to kgraves ([10.0.10.113]:22).
debug1: Remote connections from LOCALHOST:3333 forwarded to local address devils           milk:6666
debug1: channel 0: new [client-session]
debug1: Requesting no-more-sessions@openssh.com
debug1: Entering interactive session.
debug1: remote forward failure for: listen 3333, connect devilsmilk:6666
Warning: remote port forwarding failed for listen port 3333
debug1: All remote forwarding requests processed
Last login: Wed Jan 30 16:21:12 2013 from duclaw.cno.local
"tty" option detected in CYGWIN environment variable.
CYGWIN=tty is no longer supported.  Please remove it from your
CYGWIN environment variable and use a terminal emulator like mintty,
xterm, or rxvt.
_____________________________________________________________________________
##From separate CYGWIN Terminal##
CNO\kgraves@KGRAVES ~
$ mstsc /v:localhost:3333 /f

CNO\kgraves@KGRAVES ~
$
_____________________________________________________________________________

kgraves@KGRAVES ~
$ debug1: Connection to port 3333 forwarding to localhost port 6666 requested.
debug1: channel 4: new [direct-tcpip]
debug1: Connection to port 6666 forwarding to localhost port 1337 requested.
debug1: channel 4: new [direct-tcpip]
debug1: channel 4: free: direct-tcpip: listening port 3333 for localhost port 66                          66, connect from ::1 port 49496, nchannels 5
debug1: channel 4: free: direct-tcpip: listening port 6666 for localhost port 13                          37, connect from 127.0.0.1 port 48808, nchannels 5
debug1: Connection to port 3333 forwarding to localhost port 6666 requested.
debug1: channel 4: new [direct-tcpip]
debug1: Connection to port 6666 forwarding to localhost port 1337 requested.
debug1: channel 4: new [direct-tcpip]
$ debug1: channel 3: free: direct-tcpip: listening port 3333 for localhost port 6666, conne               ct from ::1 port 49495, nchannels 5
debug1: channel 3: free: direct-tcpip: listening port 6666 for localhost port 1337, connect                from 127.0.0.1 port 48807, nchannels 5
$
Run Code Online (Sandbox Code Playgroud)

已建立远程桌面连接。正如你可以看到它看起来好像它是来自devilsmilk上duclaw。但据kgraves-PC它说是从Devilsmilk. 所以我之前认为正在发生的事情实际上不是。我以为Duclaw是通过单独的路径将会话发送RDP回，kgraves但事实证明并非如此。我不确定上次它是否有效并且我有不同的设置，或者我是否在想象一些事情。但是现在我在我的 ssh 服务器出现问题后重新配置并备份并运行它绝对不再这样做了。

在此处输入图片说明

这是在会话期间wireshark运行kgraves-pc的RDP：

在此处输入图片说明

所以我的问题仍然是我希望 Duclaw 通过一个完全独立的反向隧道将 RDP 会话发送回 Kgraves-pc。这就是我需要发生的事情，但不知道该怎么做。

我不仅需要duclaw将它直接发送回一个单独的隧道kgraves-pc而不经过它，devilsmilk而且我还需要控制它发送到哪个临时端口。我希望它将它发送到端口:44444而不是随机的临时端口。它:48809在ssh上面的详细调试打印中随机使用。

希望这可以解决问题，如果不是……抱歉让您更加困惑。

Joh*_*Siu 3

要求

我需要远程桌面连接“看起来”就像来自 Devilsmilk 一样。但我希望 duclaw 将响应直接发送回 kgraves-pc，而不需要经过 Devilsmilk。因此，对于 kgraves-pc，RDP 会话将发送到本地主机，然后通过 ssh 隧道通过 Devilsmilk 转发到 duclaw，但响应该连接而接收的 RDP 数据包是直接从 Duclaw 接收的。

答案 - 由于 TCP 通信的性质，不可行

我认为这是不可行的，至少仅使用 ssh 隧道是不可行的。

让我们看看想要/请求的数据包流：

  1. kgraves-pc 启动对 localhost:3333 的 RDP 请求，这是通往 Devilsmilk:6666 的隧道
  2. Devilsmilk:6666 依次隧道到 duclaw:1337
  3. duclaw:1337 RDP 回复数据包发送至 kgraves-pc

上述数据包流不会发生，至少在正常情况下不会发生。让我们为上面的流程提供更多细节：

  1. kgraves-pc 启动对 localhost:3333 的 RDP 请求，这是通往 Devilsmilk:6666 的隧道

    此时，kgraves-pc RDP 客户端期望返回来自 localhost:3333 的数据包，仅此而已。

  2. Devilsmilk:6666 依次隧道到 duclaw:1337

    此时，对于 duclaw RDP 服务器，请求来自 localhost(duclaw ifself)，它会直接回复它。

  3. duclaw:1337 RDP 回复数据包发送至 kgraves-pc

    根据上面的（2），这条路径根本不会发生。

原始答案（不是OP想要的）

在 上kgraves-pc，SSH 命令通过隧道来实现 OP 要求。

ssh user@devilsmilk -L 3333:localhost:3389 -L 6666:10.0.10.130:3389 -R 23389:localhost:3389
Run Code Online (Sandbox Code Playgroud)

-L 3333:localhost:3389启用 kgraves-pc RDP 到 Devilsmilklocalhost:3333

-L 6666:10.0.10.130:3389启用 kgraves-pc RDP 来 duclawlocalhost:6666

-R 23389:localhost:3389启用 duclaw RDP 到 kgraves-pcdevilsmilk:23389

  • 我更新了我的答案。在镜头中，我认为 ssh 隧道不可行。 (2认同)

归档时间：

查看次数：

2711 次

最近记录：

13 年 前
相关归档
退格在 Cygwin 中不起作用 29
使 RDP 忽略键盘媒体键 13
dropbox的纯命令行操作 9
Windows 7 x64 下的 Cygwin 6
在 Cygwin 上设置 SSH/Git 会产生“~/.ssh/config 上的错误权限” 6
为什么我通过 ssh 隧道的连接比到远程机器的其他连接慢得多？ 5
为什么 dd 不输出到 stdout？ 4
Fritz!Box 端口转发工作不正常 3
“ls *.py”和“ls *py”有什么区别？ 1
如何远程运行 Windows 批处理内部命令？ 1
难疑归档
如何在 Tmux 中交换两个窗格？ 297
ps aux 输出意义 260
与 macOS tar 相比，为什么使用 Python 的 tar 库时 tar.xz 文件要小 15 倍？ 240
在 bash 中，我如何逃避感叹号？ 217
如何确定哪个 /dev 是 USB 闪存驱动器？ 176
在我输入下一个字母之前，不会显示撇号和双引号 146
Inkscape - 圆角形状？ 122
更改连接 USB 设备的默认操作 121
从命令行创建 .zip 文件夹 - (Windows) 117
如何在 VIM 上的窗口之间切换？ 105