A particular website page not diplaying

  • Thread starter Thread starter Guest
  • Start date Start date
It displays for me.

Is the browser giving a '404' (not found) message, or is it that nothing
displays?

If 'not found' then it might be a DNS issue at your ISP.

Try http://212.77.217.243 and see if that works. If so it's a DNS issue.
 
Do the following

1 start | run | cmd

2 "tracert 212.77.217.243" (without the quotes of course)

3 Post the results of the tracert.
hi Ian
thnks for ur reply, i tried http://212.77.217.243
page cannot be displayed it is showing
wht should be done now
plz explain
Click to expand...

--

Don't pay malware vendors - boycott Sony & Symantec for helping them

Please do not contact me directly or ask me to contact you directly for
assistance.

If your question is worth asking, it's worth posting.

If it’s not worth posting you should have done a search on
http://www.google.com/ http://www.google.com/grphp?hl=en&tab=wg&q= or
http://news.google.com/froogle?hl=en&tab=nf&ned=us&q= before wasting our
time.

If I sound hostile or arrogant you need to read the following before
posting a question "How To Ask Questions The Smart Way" at
(The site I've linked
to just has this article I think people should read before posting a
technical question.)
 
hi joe

c the result

C:\Documents and Settings\Sunita>TRACERT 212.77.217.243
Tracing route to 212.77.217.243
over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 221.222.222.6 2
17 ms 16 ms 16 ms 213.130.110.1 3 18 ms 16 ms
16 ms 172.24.17.17 4 19 ms 19 ms 16 ms
172.25.171.1 5 18 ms 21 ms 17 ms 172.25.161.2
6 16 ms 16 ms 16 ms 82.148.96.186 7
17 ms 19 ms 19 ms 82.148.96.181 8 19 ms 20 ms
20 ms 82.148.96.254 9 18 ms 19 ms 19 ms
212.77.216.2 10 * * * Request timed
out. 11 * * * Request timed out.
12 * * * Request timed out. 13 *
* * Request timed out. 14 * * *
Request timed out. 15 * * * Request timed
out. 16 * * * Request timed out.
17 * * * Request timed out. 18 *
* * Request timed out. 19 * * *
Request timed out. 20 * * * Request timed
out. 21 * * * Request timed out.
22 * * * Request timed out. 23 *
* * Request timed out. 24 * * *
Request timed out. 25 * * * Request timed
out. 26 * * * Request timed out.
27 * * * Request timed out. 28 *
* * Request timed out. 29 * * *
Request timed out. 30 * * * Request timed
out.
Trace complete.
 
sunitha wrote on 17-Jan-2006 2:46 AM:
TRACERT 212.77.217.243
Tracing route to 212.77.217.243
over a maximum of 30 hops
Click to expand...

1 <1 ms <1 ms <1 ms 221.222.222.6
2 17 ms 16 ms 16 ms 213.130.110.1
3 18 ms 16 ms 16 ms 172.24.17.17
4 19 ms 19 ms 16 ms 172.25.171.1
5 18 ms 21 ms 17 ms 172.25.161.2
6 16 ms 16 ms 16 ms 82.148.96.186
7 17 ms 19 ms 19 ms 82.148.96.181
8 19 ms 20 ms 20 ms 82.148.96.254
9 18 ms 19 ms 19 ms 212.77.216.2
10 * * * Request timed out.
11 * * * Request timed out.

212.77.216.2 is the last hop that has a route back to your destination.
That last hop router is registered to the Qatar ISP from a RIPE.NET
address block. Your destination is located in Qatar and for some reason,
routers between the Qatar ISP border router and your destination don't
know how to get back to your network. Obviously, they aren't using a
simple default route. But it is apparently a problem internal to the
Qatar ISP.

Ask your Chinese service provider to find out why you can't reach Qatar.
Your service provider goes through APNIC.NET to RIPE.NET and then to
Qatar. It might take a while to sort out, but the Qatar ISP network
engineers should be able to do it, it's just that they prefer to talk to
other ISP engineers not end-users.
 
I tried it on my computer & I got very similar results. I thought we
might have a failure in your Internet connection at one of the hops.

TRACERT 212.77.217.243

Tracing route to 212.77.217.243 over a maximum of 30 hops

1 * * * Request timed out.
2 33 ms 32 ms 33 ms slkc-dsl-gw10-202.slkc.qwest.net
[67.41.239.202]

3 33 ms 88 ms 33 ms slkc-agw1.inet.qwest.net [67.41.239.93]
4 38 ms 33 ms 33 ms slk-core-01.inet.qwest.net [205.171.131.21]
5 119 ms 50 ms 49 ms svx-core-01.inet.qwest.net [205.171.14.78]
6 50 ms 49 ms 124 ms sjp-brdr-01.inet.qwest.net
[205.171.214.134]
7 60 ms 50 ms 50 ms qwest-gw.sffca.ip.att.net [192.205.32.81]
8 112 ms 171 ms 118 ms 12.122.81.102
9 110 ms 110 ms 111 ms tbr1-cl3.la2ca.ip.att.net [12.122.10.26]
10 207 ms 110 ms 156 ms tbr1-cl20.dlstx.ip.att.net [12.122.10.49]
11 140 ms 166 ms 110 ms tbr2-cl12.hs1tx.ip.att.net [12.122.10.130]
12 231 ms 141 ms 110 ms tbr1-p013601.hs1tx.ip.att.net
[12.122.9.169]
13 172 ms 164 ms 109 ms tbr1-cl1476.ormfl.ip.att.net [12.122.4.102]
14 108 ms 191 ms 132 ms 12.122.81.161
15 292 ms 293 ms 292 ms 12.119.94.78
16 311 ms 348 ms 293 ms 82.148.97.65
17 383 ms 293 ms 292 ms 82.148.96.201
18 377 ms 292 ms 292 ms 82.148.96.181
19 293 ms 292 ms 293 ms 82.148.96.254
20 372 ms 294 ms 324 ms 212.77.216.2
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

One thing though I strongly recommend you get a router. It won't fix
this problem, but it will make your Internet connection safer.

I also noticed if I try to browse via the IP address that I'm redirected
to the web address. At this point I'm thinking it's time to check with
a different browser. I'd first try this one.

http://www.mozilla.com/firefox/
hi joe

c the result

C:\Documents and Settings\Sunita>TRACERT 212.77.217.243
Tracing route to 212.77.217.243
over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 221.222.222.6 2
17 ms 16 ms 16 ms 213.130.110.1 3 18 ms 16 ms
16 ms 172.24.17.17 4 19 ms 19 ms 16 ms
172.25.171.1 5 18 ms 21 ms 17 ms 172.25.161.2
6 16 ms 16 ms 16 ms 82.148.96.186 7
17 ms 19 ms 19 ms 82.148.96.181 8 19 ms 20 ms
20 ms 82.148.96.254 9 18 ms 19 ms 19 ms
212.77.216.2 10 * * * Request timed
out. 11 * * * Request timed out.
12 * * * Request timed out. 13 *
* * Request timed out. 14 * * *
Request timed out. 15 * * * Request timed
out. 16 * * * Request timed out.
17 * * * Request timed out. 18 *
* * Request timed out. 19 * * *
Request timed out. 20 * * * Request timed
out. 21 * * * Request timed out.
22 * * * Request timed out. 23 *
* * Request timed out. 24 * * *
Request timed out. 25 * * * Request timed
out. 26 * * * Request timed out.
27 * * * Request timed out. 28 *
* * Request timed out. 29 * * *
Request timed out. 30 * * * Request timed
out.
Trace complete.
Click to expand...


--

Don't pay malware vendors - boycott Sony & Symantec for helping them

Please do not contact me directly or ask me to contact you directly for
assistance.

If your question is worth asking, it's worth posting.

If it’s not worth posting you should have done a search on
http://www.google.com/ http://www.google.com/grphp?hl=en&tab=wg&q= or
http://news.google.com/froogle?hl=en&tab=nf&ned=us&q= before wasting our
time.

If I sound hostile or arrogant you need to read the following before
posting a question "How To Ask Questions The Smart Way" at
(The site I've linked
to just has this article I think people should read before posting a
technical question.)
 
Back
Top