My windows server 2016 is not connecting using RDP. It was working till yesterday but today it is not working. I had just rebooted the server and no other change was done. I am able to connect using Interactive Serial Console. Following are the findings:
Faulty server is not reachable from any other working server in the same subnet. Neither ICMP (ping) nor with TCP. For TCP, I checked with Test-NetConnection -Port 3389 and result was a failure.
Surprisingly, The faulty server is able to reach other servers with ping and Test-NetConnection on port 3389.
RDP is in running state. Verified by sc query SessionEnv, sc query TermService, sc query UmRdpService, sc query RpcSs, sc query RpcEptMapper. All these services are running. Also, restarted services.
Netstat -a shows that RDP is listening on port 3389.
netstat -a | findstr 3389
TCP 0.0.0.0:3389 IPADDRESS:0 LISTENING
TCP [::]:3389 IPADDRESS:0 LISTENING
UDP 0.0.0.0:3389 *:*
UDP [::]:3389 *:*
Verified No antivirus, windows firewall, security blockage.
Followed the steps given on https://cloud.google.com/compute/docs/troubleshooting/troubleshooting-rdp and output is PASSED. For NLA and SecureLayer the output was different and added the required changes to registry.
Can someone please help me to fix this? Is it possible to verify if RDP is broken?
Error screenshot when attempted RDP connect from server in same subnet:
by default windows desktop is blocked and disabled by windows firewall,
follow these steps to enable it
1.Open Windows Firewall (Start button > Windows System > Control Panel) - From the Control Panel Go to Systems and Security > Windows Defender Firewall.
2.From the Firewall, Click on the Allow and app or feature through Windows Defender Firewall link in the left pane.
3.Click Change settings and then check the box next to Remote Desktop, for both private and public networks.
4.Click OK to save the new settings.
you can refer this link for more details
Related
I have a server Google Cloud, it has been good working some years, but recently there was a problem, after restart server, I can not connect to its remote desktop, the prompt messagebox content is as follows:
Remote Desktop can’t connect to the remote computer for one of these reasons:
1.Remote access to the server is not enabled
2.The remote computer is turned off
3.The remote computer is not available on the network
But i check it is still on and has network connection, anybody help me?
update 1: I found the reason is port 3389 could not connect, but I tried the commands on command line still can't open port 3389
update 2: my team decided to destroy this server, close topic
I would like to ask if its possible to change listening port of Integrated Workspace Database server to be able to listen on interface of my machine so remote users can connect. I have Visual Studio 2017 - SSDT installed and Integrate Workspace listening on localhost:some port
I can connect to the port via PowerBI running on my local machine. I would like to enable it also for remote user.
I tried:
port forwarding, it is displayed in CMD proxy output but does not work
firewall is OFF
No other proxy or anything else is on the computer
Based on my further analysis you cannot change the port or set it to specific port, it always connects to the random free port. However what you can do is to use Port Forwarding on your machine
e.g. like this
netsh interface portproxy add v4tov4 listenport=3340 listenaddress=10.1.1.110 connectport=3389 connectaddress=127.0.0.1 - because it also listens on this loopback address
Adding an inbound Windows Firewall rule (via COM from C++) for local port 80 and addresses ANY, 127.0.0.1 or 0.0.0.0 does not block a local browser from accessing a local web server running on port 80. For debugging/testing purposes, I need to simulate loss of network connectivity between two programs running on the same computer. Is there a way to do this programmatically, on the command line, or with a tool?
In this question, they say allegedly there is no way to do this in the Windows Firewall:
How do I block localhost connections with the Windows 7/2008R2 firewall?
Is there a way, other than Windows Firewall, just to simulate loss of network connectivity between programs running on the same computer?
There is WIPFW -- a Windows port of FreeBSD's IPFW. However, I failed to get it to block localhost connections. Maybe you'll have more luck.
Alternatively, you can try a hack. If your programs establish a connection using the localhost host name instead of directly by the 127.0.0.1 IP address, you may change your hosts file to point the localhost name to some non-existing or otherwise unreachable address.
I'm using STS (SpringSource Tool Suite) which comes with VMware vFabric tc Server Developer Edition v2.6. The problem is, every time I start it, it shows the following error:
Port 8080 required by VMware vFabric tc Server Developer Edition v2.6
is already in use. The server may already be running in another
process, or a system process may be using the port. To start this
server you will need to stop the other process or change the port
number(s).
I don't have anything using that port that I know of. It has always worked fine until today.
I've also tried to change the port number but it doesn't accept the changes. If I change it to 8081, for example, and then restart STS it overwrites the port and sets it back to 8080.
Can anyone offer some ideas to fix this?
FYI I'm running STS in VirtualBox.
Thanks!
This applies to the latest STS version - 3.0.0
When you open STS, in the Package Explorer view (on the left), you should see a project folder called Servers.
Open Servers > VMware vFabric tc Server Developer Edition v2.7-config > catalina.properties
At the bottom of the file, you will see 2 properties defined:
bio.http.port
bio.https.port
Change bio.http.port to some other port than 8080 (e.g. 8081)
Change bio.https.port to some other port than 8443 (e.g. 8444)
Click 'Save'.
Now, when you do your right-click deploys to the built-in tc Server and start it up, it should run on the new port(s). Good luck!
In the Servers view, double click the server you wish to change the ports on. This brings up the Overview page.
Expand the Ports tab and enter your desired port settings.
The reason STS uses this configuration page is it allows you to configure a workspace server without altering the configuration in your server installation directory.
Or you might want to directly kill the zombie process still bound to that port with an oneliner:
sudo kill -9 `lsof -ti:8080`
In conjunction with Gareth's suggestion, this is what workerd for me:
In the Servers view, right click your server and click Monitoring -> Properties
Stop the monitor listening on port 8080.
Save changes and start the server.
How do I detect if a remote client is running Remote Desktop Protocol? and it is also accepting remote desktop connections ??
Like Open an port to detect HTTP and send request, receive request headers and see in request headers information about HTTP so I will know the person is running HTTP weather if he changed the port e.g: running HTTP 6551.
Attempt and make a connection with something that is RDP-connection aware (RDP is not HTTP). Of course, failing to establish an initial handshake is not proof that a connection can not be established. It could be blocked by a firewall, listening on another port, etc.
The MS-RDPBCGR specification, page 16 talks about connecting which in turn defers to X.224, go figure.
It'd likely just be easiest to use Wireshark and observe in-the-wild behavior to develop a minimal detection case. I suspect only the very initial portion of the handshake needs to be generated/replayed in order to "decide" that it's a listening RDP server.
(Or, perhaps use an existing RDP client which has this "test connect" functionality or the ability to be scripted.)
A fast way is to pen a shell and type
telnet IPADDRESS 3389
If you get a connection, chances are good that an RDP server is on the other side. RDP can run on any port, but TCP Port 3389 is set per default.
Windows 7 requires some extra steps to enable the telnet Client.
You could do netstat -a in the command line and see if the default port for remote desktop connection is listening, ie. TCP:3389 but thats only if the client hasn't changed the ports for MSTSC