On Sun, May 29, 2022 at 8:13 PM Greg Wooledge <g...@wooledge.org> wrote:
> On Sun, May 29, 2022 at 11:50:44PM +0000, Lee wrote: > > On 5/29/22, Greg Wooledge <g...@wooledge.org> wrote: > > > Second, I cannot ping this IP address, nor can I telnet to port 80 of > it. > > > > For whatever it's worth.. > > > > Pinging 69.30.225.10 with 32 bytes of data: > > Reply from 69.30.225.10: bytes=32 time=43ms TTL=53 > > Reply from 69.30.225.10: bytes=32 time=42ms TTL=53 > > Reply from 69.30.225.10: bytes=32 time=43ms TTL=53 > > Reply from 69.30.225.10: bytes=32 time=42ms TTL=53 > > Yes, it's working from here now, too. Changes definitely happened > on the OP's server's side. > > I did a TCPTraceRoute to your server on port 80 it makes it across all hops but says the port is closed on the server. tcptraceroute 69.30.225.10 Selected device wlo1, address 192.168.105.250, port 38109 for outgoing packets Tracing the path to 69.30.225.10 on TCP port 80 (http), 30 hops max 1 192.168.105.156 7.422 ms 3.828 ms 3.985 ms 2 17.sub-66-174-63.myvzw.com (66.174.63.17) 340.678 ms 692.027 ms 185.134 ms 3 194.sub-69-83-70.myvzw.com (69.83.70.194) 107.194 ms 596.305 ms 257.465 ms 4 * * * 5 242.sub-69-83-70.myvzw.com (69.83.70.242) 556.143 ms 57.157 ms 47.478 ms 6 * * * 7 * * * 8 * * * 9 153.sub-69-83-66.myvzw.com (69.83.66.153) 184.145 ms 61.027 ms 48.539 ms 10 * * * 11 * * * 12 * be3083.ccr41.dca01.atlas.cogentco.com (154.54.30.53) 445.471 ms 97.201 ms 13 be2891.ccr21.cle04.atlas.cogentco.com (154.54.82.249) 106.103 ms * * 14 * * * 15 * * be2831.ccr21.mci01.atlas.cogentco.com (154.54.42.165) 96.672 ms 16 be2546.rcr01.b073673-0.mci01.atlas.cogentco.com (154.54.30.242) 97.542 ms 89.655 ms * 17 * * * 18 * * * 19 100ge13-1.edge-a.clay.as33387.net (69.30.209.195) 725.149 ms 578.818 ms 414.786 ms 20 * * * 21 * * * 22 * server.pcstar1.com (69.30.225.10) [closed] 379.939 ms 413.809 ms
