No connection to M121 Atlas cluster

I’m unable to access the class cluster on Atlas (from the console).
I’m running on Windows 7 Pro, and was regularly able to access in all the previous courses I’ve taken.

I’ve tested for potential network issues with both

ping cluster0-shard-00-00-jxeqq.mongodb.net
from the console, which worked, and by opening
http://cluster0-shard-00-00-jxeqq.mongodb.nshare et:27017/
which opened a page saying:
It looks like you are trying to access MongoDB over HTTP on the native driver port.*
as I understand is expected in normal operating conditions.

This is what I try, and the outcome of the connection attempt (I’ve also used the tls option instead of ssl):

W:\myMongoDB\M121> mongo “mongodb://cluster0-shard-00-00-jxeqq.mongodb.net:27017,cluster0-shard-00-01-xeqq.mongodb.net:27017,cluster0-shard-00-02-jxeqq.mongodb.net:27017/aggregations?replicaSet=Cluster0-shard-0” --authenticationDatabase admin --ssl --username m121 --password aggregations --norc

2020-10-13T12:00:32.644+0200 W CONTROL [main] Option: ssl is deprecated. Please use tls instead.
MongoDB shell version v4.2.7
connecting to: mongodb://cluster0-shard-00-00-jxeqq.mongodb.net:27017,cluster0-shard-00-01-jxeqq.mongodb.net:27017,cluster0-shard-00-02-jxeqq.mongodb.net:27017/
aggregations?authSource=admin&compressors=disabled&gssapiServiceName=mongodb&replicaSet=Cluster0-shard-0
2020-10-13T12:00:32.790+0200 I NETWORK [js] Starting new replica set monitor for Cluster0-shard-0/cluster0-shard-00-00-jxeqq.mongodb.net:27017,cluster0-shard-00-01-jxeqq.mongodb.net:27017,cluster0-shard-00-02-jxeqq.mongodb.net:27017
2020-10-13T12:00:32.790+0200 I CONNPOOL [ReplicaSetMonitor-TaskExecutor] Connecting to cluster0-shard-00-00-jxeqq.mongodb.net:27017
2020-10-13T12:00:32.790+0200 I CONNPOOL [ReplicaSetMonitor-TaskExecutor] Connecting to cluster0-shard-00-02-jxeqq.mongodb.net:27017
2020-10-13T12:00:32.791+0200 I CONNPOOL [ReplicaSetMonitor-TaskExecutor] Connecting to cluster0-shard-00-01-jxeqq.mongodb.net:27017
2020-10-13T12:00:34.298+0200 I NETWORK [ReplicaSetMonitor-TaskExecutor] Confirmed replica set for Cluster0-shard-0 is Cluster0-shard-0/cluster0-shard-00-00-jxeqq.mongodb.net:27017,cluster0-shard-00-01-jxeqq.mongodb.net:27017,cluster0-shard-00-02-jxeqq.mongodb.net:27017
2020-10-13T12:00:39.303+0200 I NETWORK [js] Marking host cluster0-shard-00-01-jxeqq.mongodb.net:27017 as failed :: caused by :: Location40659: can’t connect to new replica set master [cluster0-shard-00-01-jxeqq.mongodb.net:27017], err: couldn’t connect to server cluster0-shard-00-01-jxeqq.mongodb.net:27017, connection attempt failed: NetworkTimeout: Error connecting to cluster0-shard-00-01-jxeqq
.mongodb.net:27017 (34.205.152.216:27017) :: caused by :: Socket operation timed out

*** It looks like this is a MongoDB Atlas cluster. Please ensure that your IP whitelist allows connections from your network.

2020-10-13T12:00:39.305+0200 E QUERY [js] Error: can’t connect to new replica set master [cluster0-shard-00-01-jxeqq.mongodb.net:27017], err: couldn’t connect to server cluster0-shard-00-01-jxeqq.mongodb.net:27017, connection attempt failed: NetworkTimeout: Error connecting to cluster0-shard-00-01-jxeqq.mongodb.net
:27017 (34.205.152.216:27017) :: caused by :: Socket operation timed out :
connect@src/mongo/shell/mongo.js:341:17
@(connect):2:6
2020-10-13T12:00:39.312+0200 F - [main] exception: connect failed
2020-10-13T12:00:39.313+0200 E - [main] exiting with code 1

W:\myMongoDB\M121>

It could be temporary netwrok issue or a firewall issue
Did you try from another location or different internet connection like your mobile hotspot

Try mongo 4.0 with the original string (keeping ssl). It worked for me