All kinds of wonderful 3389 solutions for connecting

Tidy up a variety of 3389 not connected to the solution.

1, the most frequent occurrence of the 3389 port is not open.
How to see the port is not open. The easiest way to do this is to netstat-an see if there are any 127.0.0.1:3389. If there is an indication that the wood has been opened, there is an open 3389 terminal port (PS: This is the premise that the administrator does not have a very cheap modification of the terminal port.) ）

The second view is based on the command line. I like this way very much.
Reg Query " HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal server\wds\rdpwd\tds\tcp"

Last picture



Let's focus on the penultimate line. PortNumber REG_DWORD 0xd3d

The general meaning is that the terminal port is D3D (the 0x in front of PS:0XD3D is a 16-binary representation D3D after 16-conversion =3389)

This allows you to see if the terminal port is turned on by using the above method.

However, if you have Webshell and support a variety of components directly read the registry will do.

Solution: Open the 3389-port method There are a variety of I will write a single article. Please continue to pay attention to my blog


2, IP policy and firewall blocking (general administrator will be set up.) ）
Workaround: Disable Service
net stop SharedAccess
net stop PolicyAgent
Get


3. Intranet
Intranet can only LCX or run the Trojan. Personal comparison I prefer the second.


4, all kinds of other software firewall control
Give an example. Met a few days ago.

SECURERDP firewall a variety of restricted connection 3389 can even be accurate to limit the host name, IP, IP segment, MAC address, and so on.

Break through the SECURERDP method.
Delete Wtsfilter.dll Delete registry key hkey_local_machine/software/terminalsoft/wtsfilter or ren get rid of Wtsfilter's name.
Method of deletion: echo y | Reg delete hkey_local_machine\software\terminalsoft\wtsfilter   This handy direct recommendation