Question Comcast Router blocking EVGA Forum's...

_dawn_chorus_

Honorable
Aug 30, 2017
558
56
11,090
So EVGA forums have been giving me a "cannot connect to server" type of error for a couple months now, I have narrowed it down to being on comcast and my router, as the only way I can access it is on my phone with wifi off. None of my 3 computers on any browser, nor my phone will load the page on wifi/ethernet.

So I went into router settings and there is no parental block..
what could possibly be causing this?? Where should I begin to look. It seems to only be the EVGA forum that won't work which is super strange.
 

rcfant89

Distinguished
Oct 6, 2011
546
3
19,015
Pull up command prompt and type "ping forums.evga.com"

Should say:
C:\Users\XXXXXX>ping forums.evga.com

Pinging e754.f.akamaiedge.net [104.121.108.222] with 32 bytes of data:
Reply from 104.121.108.222: bytes=32 time=29ms TTL=54
Reply from 104.121.108.222: bytes=32 time=23ms TTL=54
Reply from 104.121.108.222: bytes=32 time=30ms TTL=54
Reply from 104.121.108.222: bytes=32 time=29ms TTL=54

Ping statistics for 104.121.108.222:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 23ms, Maximum = 30ms, Average = 27ms

If that doesn't work, try pinging by IP (104.121.108.22). If that does work, it means DNS isn't telling your PC what the address is.
 

_dawn_chorus_

Honorable
Aug 30, 2017
558
56
11,090
Pull up command prompt and type "ping forums.evga.com"

Should say:
C:\Users\XXXXXX>ping forums.evga.com

Pinging e754.f.akamaiedge.net [104.121.108.222] with 32 bytes of data:
Reply from 104.121.108.222: bytes=32 time=29ms TTL=54
Reply from 104.121.108.222: bytes=32 time=23ms TTL=54
Reply from 104.121.108.222: bytes=32 time=30ms TTL=54
Reply from 104.121.108.222: bytes=32 time=29ms TTL=54

Ping statistics for 104.121.108.222:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 23ms, Maximum = 30ms, Average = 27ms

If that doesn't work, try pinging by IP (104.121.108.22). If that does work, it means DNS isn't telling your PC what the address is.

This is what I got:

Pinging e754.f.akamaiedge.net [23.57.47.82] with 32 bytes of data:
Reply from 23.57.47.82: bytes=32 time=40ms TTL=53
Reply from 23.57.47.82: bytes=32 time=36ms TTL=53
Reply from 23.57.47.82: bytes=32 time=36ms TTL=53
Reply from 23.57.47.82: bytes=32 time=37ms TTL=53

Ping statistics for 23.57.47.82:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 36ms, Maximum = 40ms, Average = 37ms
 

_dawn_chorus_

Honorable
Aug 30, 2017
558
56
11,090
Pull up command prompt and type "ping forums.evga.com"

Should say:
C:\Users\XXXXXX>ping forums.evga.com

Pinging e754.f.akamaiedge.net [104.121.108.222] with 32 bytes of data:
Reply from 104.121.108.222: bytes=32 time=29ms TTL=54
Reply from 104.121.108.222: bytes=32 time=23ms TTL=54
Reply from 104.121.108.222: bytes=32 time=30ms TTL=54
Reply from 104.121.108.222: bytes=32 time=29ms TTL=54

Ping statistics for 104.121.108.222:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 23ms, Maximum = 30ms, Average = 27ms

If that doesn't work, try pinging by IP (104.121.108.22). If that does work, it means DNS isn't telling your PC what the address is.
Also I just discovered if I turn on my Kaspersky VPN trial I can get on the website... what does that tell us?