I’m looking up what it is now.
2 Likes
type CMD into your windows search, to start Command Prompt. Looks like an old DOS window, and type in …
tracert e-liquid-recipes.com
2 Likes
We recently bought the apparatus to install Starlink so as soon as the hubs can set it up, we will say good freaking riddance to Century Link. Century Link was the ONLY option for us rural folks and just recently, Starlink has come into our area.
2 Likes
Well you’re clearly ON, or you wouldn’t be typing here LOL. I would PING, or TRACERT the URL and see what’s failing on your end, or backbone provider.
1 Like
Looks like you forgot the PING in the last screenshot @KC111, BUT, if you can’t trace route it through your provider, there’s a 101% chance, it will FAIL pinging as well. Looks like it’s on your end, OR, your providers end.
Try your cell phone, OR, tether (hotspot) your laptop to your cell and see if it goes through.
1 Like
How do I Ping?
I don’t have a phone.
2 Likes
CMD
ping e-liquid-recipes.com
1 Like
I truly appreciate you helping an incompetent computer idiot over here, but this might be an issue for my IT guy and I don’t want to pay for his services just for access to e-liquid recipes. I will make a note for him to look at it when I do my yearly computer check up at the end of the year.
2 Likes
@KC111 it’s interesting that you can hit the forums, but not the root site. Run a trace route on the forum side:
CMD
Tracert forum.e-liquid-recipes.com
You should at least get something similar to this. Tracing every hop …
Tracing route to forum.e-liquid-recipes.com [146.185.152.96]
over a maximum of 30 hops:1 1 ms <1 ms <1 ms Fios_Quantum_Gateway.fios-router.home [192.168.1.1]
2 18 ms 6 ms 7 ms lo0-100.PHLAPA-VFTTP-342.verizon-gni.net [108.2.140.1]
3 13 ms 12 ms 13 ms B3342.PHLAPA-LCR-21.verizon-gni.net [100.41.137.118]
4 * * * Request timed out.
5 * * 10 ms verizonwireless-gw.customer.alter.net [63.65.77.26]
6 14 ms 14 ms 14 ms nyk-bb1-link.ip.twelve99.net [62.115.121.158]
7 * * * Request timed out.
8 84 ms 86 ms 86 ms slou-b2-link.ip.twelve99.net [62.115.112.63]
9 87 ms 86 ms 92 ms digitalocean-ic-306495.ip.twelve99-cust.net [62.115.44.254]
10 90 ms 88 ms 87 ms 138.197.244.89
11 85 ms 86 ms 85 ms 138.197.250.59
12 * * * Request timed out.
13 * * * Request timed out.
14 98 ms 95 ms 96 ms 146.185.152.96Trace complete.
1 Like
Well you shouldn’t have to pay.
You mentioned Century Link, is that a local cable provider ? If so, the issue may lie with them. I have had routing issues CAUSED by Verizon, OR, the backbone Level 3. Tracing can tell you where the problem is.
I wonder if you can ping or trace route the raw IP address, ruling out a DNS issue …
95.85.24.224
1 Like
Yeah Century Link truly sucks, we didn’t have any other option for the longest time so as soon as we found out Starlink was going to service our area, we jumped on that train.
2 Likes
No no @KC111 that’s GREAT you got the trace to run on the forums. GREAT. Now we have to figure out why the main site won’t.
If your DNS gets @#$#$%%^ up (Domain Name Server) get fragged, you could be typing in the name, but NOT getting sent correctly there.
2 Likes
I am so !@#$! sorry, but I do NOT speak Klingon! What you typed is all gibberish to me.
2 Likes
Hehe, ok, the trace you DID run, is good, shows your local hops, then onto your “backbone” (internet backbone) i.e. Level3, which hands off ot Twelve99, then some destination firewalled or cloaked hops, then ending at the host.
If you trace, and it stops mid way, we know WHO is to blame.
Now, BACK to the whole recipe site thing.
I wonder if you can PING, or TRACE ROUTE direct to the IP, NOT using the domain name.
95.85.24.224
i.e.
CMD
ping 95.85.24.224
and
tracert 95.85.24.224
1 Like
You’re doing good …
1 Like
All I saw was blah blah blah, LOL!
I will copy and paste CMD
ping 95.85.24.224 and tracert 95.85.24.224 and display what it says, but dudette…I have no $ to pay you at this time.
2 Likes