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
Related
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
I am consistently seeing a 3+ second delay when opening a connection to a Unidata server via OpenAsync and the ADO.NET provider by Rocket.
What can I do to diagnose this delay?
I use jdbc and odbc connections all the time, and three seconds just ain't right.
You can start by breaking things down into client, network, server.
On the client, is it the same if you use an IP address vs hostname? If different, then DNS delay. Do you have any antivirus or other software that might be delaying connections? Can you turn that off, or do a test from a freshly configured machine?
For network, can you ping the unidata server in millseconds? Are there firewalls in the way? Can you install wireshark and filter packets by destination? Is there a delay when you ssh? Is the server configured with LDAP/AD, or local authentication - could be connecting to another server to authenticate?
On the server, you can turn on uniobjects logging, then restart unirpcd. Do you have something in your LOGIN/UOLOGIN that is hanging up the remote connection?
$cat $UDTHOME/serverdebug
udcs 9 /tmp/udcs.log
I have successfully built the client and server modules from the Getting Started with Winsock tutorial.
I have a desktop and a laptop both connected to my wireless router – both running Windows 10.
Running the client module on the laptop, I am able to successfully transmit data back-and-forth to the desktop (running the server module) using the desktop's IP address.
Running the client module on the desktop with the laptop's IP address as the command line argument, I get an "Unable to connect to server!" message after a ten second delay.
If I try to run both modules on the desktop in separate console windows using the "localhost" command line argument, the client console displays "Bytes sent: 14" and hangs waiting for a response from the server – however this works if I use either the desktop name or the desktop IP address in place of "localhost".
I am able to run both modules on the laptop using either "localhost", the laptop name, or the laptop IP address as arguments.
I have gone through the same motions with port 27015 forwarded on the router and incoming and outgoing firewall exceptions added to both the desktop and the laptop – there is no difference either way.
Any assistance would be greatly appreciated as I cannot figure out why this works in one direction but not the other.
Thank you for the suggestions Karsten and Andriy. I first tried getting the two computers to ping each other and neither was successful. After researching online, I was able to get them to ping after turning on "echo requests" in the firewall settings, but my original problem persisted. I then tried turning off both firewalls and I was able to get my server and client programs to work both ways. That wasn't a great long-term solution, so I tried selectively disabling the firewalls and realized it was an issue on the laptop's end. I noticed that my "server.exe" program was in the allowed apps list twice – one instance granting private access and one granting public access – but only one instance was active. I deleted both and added "server.exe" again with both public and private access boxes checked, which solved my issue.
I have client server application that works with Firebird server. Everytime when clients connect to the server they(client apps) don't check if there is a network connection to the server so at this time my application sometimes freezes when the server computer is switched off or service has stopped, so first of all I need to check connection if remote host is switched on or at some port anything listening....
Before establishing the connection I need to check it and make sure server and service is running using Indy components.
Any ideas? also I can use IcmpClient to ping remote host and then establish connection but which is the most optimal way ?
If you just want to check if the server computer can be reached, you could do a "ping" to check that. However, if you want to check if a specific TCP port is open, then the only way to find that out is to actually do a proper connect, which leads to the "freezing" program while the connection times out if there is no-one listening on that port.
I have a virtual machine created from an linux image (and powered on). I want to be able to access its console in VCenter, but right now I am getting this error:
"A secure connection to the host could not be established"
The console is a black screen with nothing on it and no interaction. This happens for any VM in VSphere. Bizarrely I can telnet in to the console port 902, but there doesn't even appear to be any attempt to connect to the console (checking tcp/ip traffic in Task Manager).
SSHing in is not possible because the reason I wanted console access to begin with was to run commands to set up an IP address for this machine.
Some facts: Opening an external console window does nothing (same error). I'm running Windows XP Professional (out of VirtualBox if it matters). My colleague on the exact same setup (same version of XP, same version of VCenter) can connect to the console just fine.
Does this problem happen when you connect directly to the ESX/ESXi ?
if not you have connection problem beetween esx and vcenter.
you can find here a list of common ports :
http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=1012382&sliceId=1&docTypeID=DT_KB_1_1&dialogID=312218113&stateId=1%200%20312216906#vCenter 4.x
Turns out that when connecting to vcenter I needed to use https instead of http. Boy howdy, do I feel smart now.