It is possible that you have the DNC "virus", or your hosts file is corrupt, but it could be as simple as "neopets.com" is down. Try "www.neopets.com" instead.
If you are familiar with the "ping" command, you can try to ping "www.neopets.com" to see if your computer can get to it.
For example:
Code:
>ping neopets.com
Pinging neopets.com [206.220.43.92] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 206.220.43.92:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
>ping www.neopets.com
Pinging www.neopets.com [129.228.36.181] with 32 bytes of data:
Reply from 129.228.36.181: bytes=32 time=91ms TTL=117
Reply from 129.228.36.181: bytes=32 time=91ms TTL=117
Reply from 129.228.36.181: bytes=32 time=91ms TTL=117
Reply from 129.228.36.181: bytes=32 time=92ms TTL=117
Ping statistics for 129.228.36.181:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 91ms, Maximum = 92ms, Average = 91ms
Note that
www.neopets.com is responding, but neopets.com is not.
If you get a "Request timed out" for both, try doing a trace route (tracert)
Login
Register
FAQ
Search
