• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Website cannot be viewed by half the world

N

NGA

Junior Member
I work for the company National Gaming Association (NGA) and the problem that I have right now is that there are alot of people on some highspeed broadband that CANNOT see our site, but there's also alot of other people on different highspeed broadbands that CAN see our site. I was wondering what could be the problem. The company website is www.ngasports.com I thought it was my DNS Server at first but if you do a check on my DNS Server at www.dnsreport.com and put in ngasports.com as the result. My DNS Server is configured correctly. I really seriously need help. I'm all out of ideas what exactly could be the problem. I didn't have this problem before. Everyone was able to view this site. So please lend me some hints on what exactly could be the problem. Thank you
 
Did you try to re-host a mirror to see if its the coding? I can't see your page so really can't give all that detailed advice...
 
Appears to be a problem with your DNS daemons, or with some part of the Internet.

C:\Documents and Settings\Administrator>nslookup ngasports.com
Server: my.dns.server
Address: xxx.xxx.xxx.xxx

DNS request timed out.
timeout was 2 seconds.
*** Request to my.dns.server timed-out

C:\Documents and Settings\Administrator>nslookup ngasports.com NGA.OGEXPO.COM
DNS request timed out.
timeout was 2 seconds.
*** Can't find server name for address 216.193.197.210: Timed out
Server: UnKnown
Address: 216.193.197.210

DNS request timed out.
timeout was 2 seconds.
Name: ngasports.com
Address: 216.193.197.210


C:\Documents and Settings\Administrator>nslookup ngasports.com NGA1.OGEXPO.COM
*** Can't find server name for address 216.193.197.210: Server failed
Server: UnKnown
Address: 216.193.197.210

DNS request timed out.
timeout was 2 seconds.
Name: ngasports.com
Address: 216.193.197.210
Click to expand...

I can't tracert or pathping because I'm behind a transparent proxy (or maybe my ISP is just blocking that port).
 
Microsoft(R) Windows DOS
(C)Copyright Microsoft Corp 1990-2001.

C:\DOCUME~1\HERMDO~1>tracert ngasports.com

Tracing route to ngasports.com [216.193.197.210]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms ***.***.**.*
2 9 ms 18 ms 10 ms 10.2.0.1
3 13 ms 8 ms 10 ms 24-113-0-1.wavecable.com [24.113.0.1]
4 19 ms 19 ms 18 ms sl-gw6-tac-8-0-TS10.sprintlink.net [160.81.243.1
01]
5 19 ms 19 ms 36 ms sl-bb21-tac-11-2.sprintlink.net [144.232.17.2]
6 35 ms 49 ms 51 ms sl-bb22-tac-15-0.sprintlink.net [144.232.17.94]

7 35 ms 26 ms 30 ms sl-bb20-sea-0-0.sprintlink.net [144.232.9.150]
8 23 ms 19 ms 19 ms so-3-0-0.gar1.Seattle1.Level3.net [209.0.227.133
]
9 19 ms 21 ms 21 ms so-7-0-0.mp1.Seattle1.Level3.net [64.159.1.81]
10 51 ms 50 ms 49 ms so-1-0-0.bbr1.LosAngeles1.Level3.net [209.247.9.
113]
11 50 ms 51 ms 50 ms so-7-0-0.gar1.LosAngeles1.Level3.net [209.247.9.
214]
12 52 ms 52 ms 47 ms ge2-0.cr02.lax01.mzima.net [63.209.80.78]
13 51 ms 65 ms 49 ms ge1-1.cr03.lax01.mzima.net [64.235.224.150]
14 47 ms 63 ms 70 ms ge0-corpcolo.cust.lax01.mzima.net [64.235.224.22
6]
15 50 ms 51 ms 50 ms ngasports.com [216.193.197.210]
16 56 ms 49 ms 50 ms ngasports.com [216.193.197.210]

Trace complete.

C:\DOCUME~1\HERMDO~1>pathping ngasports.com

Tracing route to ngasports.com [216.193.197.210]
over a maximum of 30 hops:
0 hermdogg.cedarcomm.com [***.***.**.*]
1 ***.***.**.*
2 10.2.0.1
3 24-113-0-1.wavecable.com [24.113.0.1]
4 * sl-gw6-tac-8-0-TS10.sprintlink.net [160.81.243.101]
5 sl-bb21-tac-11-2.sprintlink.net [144.232.17.2]
6 sl-bb22-tac-15-0.sprintlink.net [144.232.17.94]
7 sl-bb20-sea-0-0.sprintlink.net [144.232.9.150]
8 so-3-0-0.gar1.Seattle1.Level3.net [209.0.227.133]
9 so-7-0-0.mp1.Seattle1.Level3.net [64.159.1.81]
10 so-1-0-0.bbr1.LosAngeles1.Level3.net [209.247.9.113]
11 so-7-0-0.gar1.LosAngeles1.Level3.net [209.247.9.214]
12 ge2-0.cr02.lax01.mzima.net [63.209.80.78]
13 ge1-1.cr03.lax01.mzima.net [64.235.224.150]
14 ge0-corpcolo.cust.lax01.mzima.net [64.235.224.226]
15 ngasports.com [216.193.197.210]
16 ngasports.com [216.193.197.210]

Computing statistics for 400 seconds...


At which point it died. I don't much about this kinda stuff, maybe Ryoga can make some sense of it?
 
Well, pathping and tracert look fine, so there's no obvious loss of communication somewhere in the middle. What you'd be looking for would be some hop in the middle with a time-out or destination not found error.

Hops 15 and 16 concern me, however. Maybe it's just a snafu with Windows, but hop 16 shouldn't be there. Is your network routing table set up correctly?
 
Kept the command line open and it finally finished.. Does hop 12 mean anything, Ryoga?


C:\DOCUME~1\HERMDO~1>pathping ngasports.com

Tracing route to ngasports.com [216.193.197.210]
over a maximum of 30 hops:
0 ***********
1 ***.***.**.*
2 10.2.0.1
3 24-113-0-1.wavecable.com [24.113.0.1]
4 * sl-gw6-tac-8-0-TS10.sprintlink.net [160.81.243.101]
5 sl-bb21-tac-11-2.sprintlink.net [144.232.17.2]
6 sl-bb22-tac-15-0.sprintlink.net [144.232.17.94]
7 sl-bb20-sea-0-0.sprintlink.net [144.232.9.150]
8 so-3-0-0.gar1.Seattle1.Level3.net [209.0.227.133]
9 so-7-0-0.mp1.Seattle1.Level3.net [64.159.1.81]
10 so-1-0-0.bbr1.LosAngeles1.Level3.net [209.247.9.113]
11 so-7-0-0.gar1.LosAngeles1.Level3.net [209.247.9.214]
12 ge2-0.cr02.lax01.mzima.net [63.209.80.78]
13 ge1-1.cr03.lax01.mzima.net [64.235.224.150]
14 ge0-corpcolo.cust.lax01.mzima.net [64.235.224.226]
15 ngasports.com [216.193.197.210]
16 ngasports.com [216.193.197.210]

Computing statistics for 400 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 ***************
0/ 100 = 0% |
1 1ms 0/ 100 = 0% 0/ 100 = 0% ***.***.**.**
0/ 100 = 0% |
2 10ms 1/ 100 = 1% 1/ 100 = 1% 10.2.0.1
0/ 100 = 0% |
3 10ms 1/ 100 = 1% 1/ 100 = 1% 24-113-0-1.wavecable.com [24.113.0
.1]
0/ 100 = 0% |
4 27ms 0/ 100 = 0% 0/ 100 = 0% sl-gw6-tac-8-0-TS10.sprintlink.net
[160.81.243.101]
0/ 100 = 0% |
5 26ms 0/ 100 = 0% 0/ 100 = 0% sl-bb21-tac-11-2.sprintlink.net [1
44.232.17.2]
0/ 100 = 0% |
6 28ms 1/ 100 = 1% 1/ 100 = 1% sl-bb22-tac-15-0.sprintlink.net [1
44.232.17.94]
0/ 100 = 0% |
7 28ms 0/ 100 = 0% 0/ 100 = 0% sl-bb20-sea-0-0.sprintlink.net [14
4.232.9.150]
0/ 100 = 0% |
8 30ms 0/ 100 = 0% 0/ 100 = 0% so-3-0-0.gar1.Seattle1.Level3.net
[209.0.227.133]
0/ 100 = 0% |
9 32ms 0/ 100 = 0% 0/ 100 = 0% so-7-0-0.mp1.Seattle1.Level3.net [
64.159.1.81]
0/ 100 = 0% |
10 58ms 0/ 100 = 0% 0/ 100 = 0% so-1-0-0.bbr1.LosAngeles1.Level3.n
et [209.247.9.113]
0/ 100 = 0% |
11 59ms 2/ 100 = 2% 2/ 100 = 2% so-7-0-0.gar1.LosAngeles1.Level3.n
et [209.247.9.214]
0/ 100 = 0% |
12 --- 100/ 100 =100% 100/ 100 =100% ge2-0.cr02.lax01.mzima.net [63.209
.80.78]
0/ 100 = 0% |
13 56ms 0/ 100 = 0% 0/ 100 = 0% ge1-1.cr03.lax01.mzima.net [64.235
.224.150]
0/ 100 = 0% |
14 56ms 0/ 100 = 0% 0/ 100 = 0% ge0-corpcolo.cust.lax01.mzima.net
[64.235.224.226]
0/ 100 = 0% |
15 57ms 0/ 100 = 0% 0/ 100 = 0% ngasports.com [216.193.197.210]
0/ 100 = 0% |
16 59ms 0/ 100 = 0% 0/ 100 = 0% ngasports.com [216.193.197.210]

Trace complete.
 
Just wondering, is this one particular highspeed broadband service that this happens with? Are you using any web site tracking tool that tells you number of visitors/hits to the site? If so, I wonder whether that might give a clue to the problem, such as showing that the problem occurs when a high number of hits occur at the same time.

I viewed it via my Sprint DSL line.
 
please tell me who is your provider. And let me know if you can ping 216.193.197.210 and get a reply. Or if you can ping our name server nga.ogexpo.com. Thank you
 
please tell me who is your provider. And let me know if you can ping 216.193.197.210 and get a reply. Or if you can ping our name server nga.ogexpo.com. Thank you
Click to expand...
Are you talking to me? Yes, I can ping your site. Here's the results:

F:\DOCUME~1\DAVIDD~1>ping 216.193.197.210

Pinging 216.193.197.210 with 32 bytes of data:

Reply from 216.193.197.210: bytes=32 time=120ms TTL=109
Reply from 216.193.197.210: bytes=32 time=119ms TTL=109
Reply from 216.193.197.210: bytes=32 time=122ms TTL=109
Reply from 216.193.197.210: bytes=32 time=121ms TTL=109

Ping statistics for 216.193.197.210:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 119ms, Maximum = 122ms, Average = 120ms


F:\DOCUME~1\DAVIDD~1>ping nga.ogexpo.com

Pinging nga.ogexpo.com [216.193.197.210] with 32 bytes of data:

Reply from 216.193.197.210: bytes=32 time=118ms TTL=109
Reply from 216.193.197.210: bytes=32 time=118ms TTL=109
Reply from 216.193.197.210: bytes=32 time=121ms TTL=109
Reply from 216.193.197.210: bytes=32 time=119ms TTL=109

Ping statistics for 216.193.197.210:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 118ms, Maximum = 121ms, Average = 119ms

__________________________________________________
My DSL service is a Sprint/Earthlink package. Sprint is my telephone service provider, and I pay them for my DSL service. Earthlink is the underlying ISP.
 
Now as for the guys who can't view the site, if you switch your dns to 4.2.2.2 you will be able to view our site with no problem whatsoever. I've been trying to figure out exactly what is going on. My coworker has comcast cable at home. He can't view our website. But he's able to view it if he types in nga.ogexpo.com which redirects to the ip of ngasports.com. By doing that it tends to give him lag spikes. So the site doesn't load as fast and efficiently as it should. He even does a traceroute to the site. He gets 1 timeout. But right when he switches to the 4.2.2.2 dns server. Everything works 100% correctly. And I tell him to do a traceroute. It's the same identical path. But now he's able to view everything efficiently. So I am to believe it is his provider's DNS Server. So for those of you who can't view it. I believe it is your provider's DNS server that is having problem. From what I found out last night. One of Comcast's DNS server takes about 24 hours to refresh. Which is way too long than the recommended time. So please give me your feedback. Give me the IP of your DNS Server so I can trace exactly what is the problem. Thank you
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top