- Le plus récent
- Le plus de votes
- La plupart des commentaires
I can RDP and everything just fine
and
can easily ping it and get a response
These show that the Windows instance is responding to requests on port 3389 and to ICMP requests.
anything like telnet or ssh are entirely non functional
You wouldn't expect an EC2 instance running Windows to respond to SSH (port 22) or telnet (default port 23), there needs to be a service listening on that port. netstat -aof
will show which process(es) are listening on which port(s).
To go into more detail, I'm writing a server/client program in .NET, and the machine is actively refusing ALL requests i'm making using this program.
I'm guessing the server portion is running on the EC2 (as this is the host that you're trying to make connections into). Which port is it listening on?
Please verify that there is "server" side of the application that you wrote is running and there is service listening on the specific port you connecting to per previous answer
Contenus pertinents
- demandé il y a un an
- demandé il y a un an
- demandé il y a 7 mois
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 2 ans
are you able to bring up second instance of ec2 in the same VPC and connect from it to your 1st instance?
If you writing the .net client server application, assuming you running a server application part on ec2 you trying to connect to? Are you able to verify that there is a process listening on the specific port (using netstat) like Steve Suggested