I was having trouble starting my training videos. The root cause was that I had to clear cookies and history in my Chrome browser.
Prior to that I tried to see if was an issue with my service provider or a connectivity issue across the internet. My reason for going into detail is that the process of gathering information and troubleshooting is not always a 1 step process. Also there is creativity along with technical skill to navigate. I have done this for awhile and it is just a reminder to realize that technical, combined with creative use of commands and knowledge makes for a very exciting and challenging career path.
Here goes:
==========
Went to google and searched for "nslookup" to find related domain and ip addr information for tamuk.quickstart.com. The command nslookup is used to go from ip addr to domain or from domain to ip addr. This is a unix/linux command.
(found http://www.kloth.net/services/nslookup.php where you put in domain and get ip addr and receive good information)
Using the domain of "tamuk.quickstart.com" located the domains supporting the servers on the east coast. Along with the ip addr of the supporting servers (or virtual machines):
elb.amazonaws.com.
Name: qs-prod1-1938945103.us-east-1.elb.amazonaws.com
Address: 34.192.133.2
Name: qs-prod1-1938945103.us-east-1.elb.amazonaws.com
Address: 52.22.116.237
AWS is the acronym for Amazon Web Service. This led be to gather that Amazon was the cloud and the cloud location was on the east coast.
I then decided to get info on the servers in the domain by opening a dos prompt in widows 10 (not using the .net framework where I can use Powershell), I did this by typing in "cmd" in the lower left hand corner window that says "Type here to search). I then performed a traceroute (tracrt in windows "dos speak") to one of the ip addr.
-------------------------------------------------------
It appears you need the .net running to use power shell.
Will follow up during Q&A tonight at 6P CST 9/19
-------------------------------------------------------
Looks to me that the data center for AWS us-east is in DC and I took a path through Charlotte, NC (I am in Raleigh), then a firewall stopped it at an unkown address.
:\Users\MainUser>tracert 52.22.116.237
Tracing route to ec2-52-22-116-237.compute-1.amazonaws.com [52.22.116.237]
over a maximum of 30 hops: