Another question for the IT pros...
 

I am using a MS Surface Pro (SP) running Win10. I have the SP configured with their dock and have an ethernet cable plugged directly into the dock/SP. I am using Firefox as a browser.

The problem is when I try to reach motorsportreg.com (MSR) I continually get an error message that the MSR server has timed out. The same thing happens if I use IE as a browser on the SP. And when using both my iPhone and iPad on the condo's wifi the same thing happens using Safari as the browser.

This is the only website that I have tried where this happens and I am on the computer many hours of the day at many different sites.

The interesting thing is that if I turn the wifi off, my iPhone and iPad reach MSR immediately using the local cell provider (Cox, here in the Scottsdale, AZ area). I spoke with MSR yesterday and they assured me that their system is up and running and a colleague in the PHX area said he had accessed MSR just minutes after I told him I was still having problems.

So the question is: what would cause this problem and how do I fix it?

Might be a name resolution issue. Can you reach the server by using it's IP address?

T-Rex

Thanx for your quick response KC911.

I don't know the IP address of MSR; however when I just did a Google search on "what is the IP address of motorsportreg.com" I got a list of results, the first of which was a notice from MSR, dated October 1, 2019, addressing an issue "DNS Server Issues" which as it first paragraph was "Beginning yesterday at 3:00pm Pacific time we began receiving reports of intermittent access problems with MotorsportReg.com. Initially it appeared to be a routing issue but as we worked with our vendors to peel back the layers of the onion we found it was a problem with a DNS server. For a small percentage of our users this made the site unavailable and we are very sorry for the interruption."

So clearly there have been some problems with reaching MSR and the MSR rep I spoke with yesterday was either unaware of this problem from just a couple of months ago or was disingenuous in her answer.

Along with getting the IP address and trying it, run a trace route (tracert.exe) to that name and also the IP address to see what the times for the various hops are and what the last one or two at the website.

Try the whole URL:

https://www.motorsportreg.com/

also https://69.63.143.195

David,
I tried both of those with the same no-joy results, i.e., I get the server timed out error message.

John: I'm afraid that I don't know how to run tracert.exe command.

On your surface, open a command prompt.
Click start and start typing "Command Prompt" until it shows up as something to choose.
At the "C:\>" prompt, type "Tracert www.motorsportreg.com"
Here's part of my result, I'm leaving out the first few hops.

5 2 ms 2 ms 2 ms vaonet-air-gw.direct.airstreamcomm.net [64.33.129.130]
6 3 ms 3 ms 3 ms 10ge2-13.core1.msn1.he.net [216.66.73.241]
7 7 ms 7 ms 8 ms 100ge4-1.core1.chi1.he.net [184.105.65.225]
8 8 ms 8 ms 8 ms level3-as3356.100gigabitethernet6-2.core1.chi1.he.net [216.66.73.246]
9 * * * Request timed out.
10 29 ms 29 ms 29 ms edge-web-ho.ear3.washington1.level3.net [4.59.144.222]
11 235 ms 30 ms 29 ms balt1-c1r4.edgehosting.net [68.169.0.4]
12 30 ms 29 ms 29 ms 69.63.143.195

Trace complete.

Now then, two questions -
Are you married?
How tech savvy is your wife?

She could have blocked motorsportreg.com in your router to keep you home weekends.

Well it doesn't sound like you have a resolution issue.

Since you can get to the server with one service provider (COX) and not the other (condo?), I'm thinking that maybe this is being blocked by the condo SP. Either globally, or at the router as rockfan suggests.

Do you control the router? Do you have any "nanny" filters configured?

Just checking back in....

Don't think DNS resolution has been eliminated for the OP....yet. Keep in mind that ICMP (tracert, pings) are not TCP like the browser traffic....could be port related too.

....pssst....it's DNS ;)....

Good luck!

How would DNS resolution factor in if he tries to hit https://69.63.143.195

I missed that post ;)....bad eyez :)

Ok, I was able to do the Tracert (thanx Rockfan for showing me how to do that) and here is what I got:

http://forums.pelicanparts.com/uploa...1576186214.jpg

I have no idea what this means...

And Mrs. Balloonmeister is not tech savvy. :)

(i got a bad certificate warning when i try to get to that site using the IP or its url)

DNS = Domain Name Server - it translates human readable names to ip address. When you type the domain name in the browser, the system will hit DNS to find the IP address for that name, then go to the IP address. If you enter the IP address instead then it just goes directly to the server with that IP address. This is an extreme simplification of the process but that's the gist of it.

Using different networks will point you to different DNS servers.

Maybe DNS cache is stale. at a command prompt type ifconfig /flushdns and see if the works.

If not at a command prompt type nslookup <website name>

Do this for both your cox network and the other one you mentioned and post your results.

URL loads fine for me. The IP will show bad certificate because the cert is registered to the domain name.

Most likely the router/firewall at your site/home blocking it. If it works on cell, but not on your wireless it's probably a local setting on wireless or firewall

This is correct.

The internet is like a road system with turns, on and off ramps, etc....

The mobile devices when off WIFI are driving to the destination from a different starting point so they are taking different roads.

The condo WIFI takes OP on a route that has a bridge out.

He can try changing the DNS his Surface uses from what is most likely the ISP's DNS to to a public DNS like google.

On the Cox network in the condo:



http://forums.pelicanparts.com/uploa...1576204172.jpg

show me the name in 69.63.143.195 . That's right it's not there. That's because I already ''resolved" it for him. 69.63.143.195 IS THE IP ADDRESS OF THE WEB SERVER. https://www.motorsportreg.com/ = https://69.63.143.195

No further resolution is needed. If he can't get to https://69.63.143.195 (which he can't) it's not a DNS problem. Period.

Reread post #6

Sorry the nslookup command in my post should have been nslookup motorsportreg.com. the name was filtered out due to the way I typed it.