|
|
|
| |||||||||
![]() |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
#1
|
|||
|
|||
|
Hi,
I'm new here and not sure if I'm doing this right but here goes. Can't access URL Performed Ping test C:\WINDOWS>ping 64.53.83.146 Pinging 64.53.83.146 with 32 bytes of data: Reply from 64.53.83.146: bytes=32 time=373ms TTL=110 Reply from 64.53.83.146: bytes=32 time=448ms TTL=110 Reply from 64.53.83.146: bytes=32 time=365ms TTL=110 Reply from 64.53.83.146: bytes=32 time=404ms TTL=110 Ping statistics for 64.53.83.146: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 365ms, Maximum = 448ms, Average = 397ms Also Tracert only pasted the final few hops 10 1018 ms 296 ms 291 ms tbr2-p012201.sffca.ip.att.net [12.123.13.193] 11 291 ms 292 ms 288 ms tbr1-cl3.la2ca.ip.att.net [12.122.10.26] 12 322 ms 314 ms 315 ms tbr1-cl2.dlstx.ip.att.net [12.122.10.49] 13 362 ms 351 ms 486 ms tbr2-cl1.attga.ip.att.net [12.122.2.90] 14 351 ms 350 ms 352 ms gar1-p390.chlnc.ip.att.net [12.123.149.6] 15 387 ms 370 ms 369 ms 12.125.220.30 16 379 ms 372 ms 367 ms 165.166.24.6 17 369 ms 373 ms 364 ms 165.166.25.10 18 366 ms 359 ms 357 ms atm1-0-1060301.r02.gaatln.infoave.net [165.166.5 5.22] 19 368 ms 372 ms 364 ms evolite.net [64.53.83.146] I've been reading all over today and can't seem to find the right fix. Got the latest DUN from Microsoft Added the domain in the hosts file Also ran lspfix, with no problems showing Nothing works Am hoping this will Thanks guys ![]() |
|
#2
|
||||
|
||||
|
search this forum for the phrase "cannot be displayed". There's a topic a while back where somebody had this problem and it was solved by him running some kind of winsock fix, which corrected some error in the registry. Try that.
Other things, let's check your ability to connect: telnet://64.53.83.146:80 telnet://64.53.83.146:443 a successful result is a black dos screen with no text and just a blinking cursor in the upper left hand corner. A failed result is if there's a black screen saying a message like "connecting..." and after a while it dissappears (timed out) or if the screen appears and dissappears immediately (connection refused). At least, that's what you get on Windows 2000 and possibly XP and 2003. Not sure if you've got one of those, you didn't grace us with that minor bit of information.
__________________
Send me a private message if you would like me to setup your DNS for you for a price of your choosing. This is the preferred method if your DNS needs to be fixed/setup fast and you don't have the time to bounce messages back and forth on a forum. Also, check out these links: Whois Direct | DNS Crawler | NS Trace | Compare Free DNS Hosts |
![]() |
| Viewing: Dev Shed Forums > System Administration > DNS > Page Cannot be Displayed Dns Error |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
|
|