3 Risposte
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
0
If you can consistently do that outside your office network, most likely it's the issue with your corp network that's blocking traffic. You should contact your network admin.
One way to try to troubleshoot is using tracert command and optionally enable and check VPC flowlogs.
If you were not able to see the traffic coming in in the VPC flowlog, it might suggest the packet is dropped before reaching AWS.
con risposta 2 anni fa
0
This is the tracert on machine connected to network with the error (while error occurs) https://i.ibb.co/QmwXQFj/err.png
con risposta 2 anni fa
Contenuto pertinente
AWS UFFICIALEAggiornata 2 anni fa- AWS UFFICIALEAggiornata 3 anni fa
- AWS UFFICIALEAggiornata 4 mesi fa
But it's not only from my office network that problem occurs, also from other specific networks. I have enabled the flow log and this is the result (i.ibb.co/0rBTLDS/Cattur2.png). On 31-01-2022 from 3:14 to 3:20 GMT + 01: 00 approximately the problem occurred on a machine with ip highlighted in blue in the file; on the log everything looks ok. As soon as I am able to replicate the error I will run tracert for more info
The flowlog's record shows port 443 which generally is for HTTPS traffic, not SSH (22).