[archieve]

hi all,
i'm having some problems with wireless connection on my laptop. i'm able to connect any website i so desire (which is nice) *except* mine (http://metafold.net). i've been doing a lot of work on it lately and was most dismayed when this problem suddenly cropped up this morning. for some reason, smartftp (and the equivalent web-version provided by my host) will not log me in. also, when i try to load the website (in firefox or ie), it just times out.

i tried using cmd.exe to ping and / or tracert the connection. both failed (didn't go anywhere)--just stating that a the host couldn't be resolved / that it wasn't there. is this an IP address problem? is it something with my DNS settings? i'm pretty clueless about this sort of thing and just want to get back to fixin' up the website, so any ideas are super-appreciated. thanks a lot!



ethan

[Advertisements]

Website works fine as of three hours after you posted this. Maybe it was a temporary outage.

[Neil Jones]

Website works fine as of three hours after you posted this. Maybe it was a temporary outage.

[archieve]

hi all,
yeah...sorry if i wasn't clear--i know the website itself is working. the problem is (for some reason) i can't access it. me personally. my computer's IP address or DNS cache or something is somehow interfering with my accessing that particular website. i'm pretty sure the problem's on my end.

when i run tracert for "http://metafold.net", i get an error message: "tracert [url="http://metafold.net""]http://metafold.net"[/url] and it returns"unable to resolve target system name [url="http://metafold.net""]http://metafold.net"[/url].
(5) pinging from cmd gives me: "ping request could not find host [url="http://metafold.net""]http://metafold.net"[/url]

*however*, when i enter the site's ip address (67.210.98.210) directly (rather than the text of the website address), tracert gives me this:

"Tracing route to laran.lunarmania.com [67.210.98.210]
over a maximum of 30 hops:

1 1 ms 2 ms 2 ms 10.199.94.129
2 * * * Request timed out.
3 3 ms 2 ms 2 ms 10.192.91.6
4 2 ms 3 ms 4 ms 128.42.171.46
5 2 ms 3 ms 4 ms ge-5-1-114.hsa2.Houston1.Level3.net [63.214.240.
33]
6 3 ms 3 ms 5 ms so-6-0-0.mp1.Houston1.Level3.net [4.68.96.53]
7 42 ms 91 ms 101 ms as-1-0.bbr2.LosAngeles1.Level3.net [64.159.0.246
]
8 50 ms 40 ms 41 ms vlan79.csw2.LosAngeles1.Level3.net [4.68.20.126]

9 40 ms 66 ms 40 ms ge-8-0.hsa2.LosAngeles1.Level3.net [4.68.102.41]

10 122 ms 68 ms 56 ms 4.79.250.22
11 63 ms 61 ms 71 ms ge0502-csr2.rvs1.marquisnet.com [208.110.168.14]

12 58 ms 56 ms 57 ms unused-future-customer-ip.marquisnet.com [208.11
0.171.26]
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."

any ideas? thanks a lot!


ethan

[Dellica]

If you think it's a DNS-issue you could always try to flush your dns by typing in a commandwindow (start - run - "cmd"): ipconfig /flushdns
Make sure you have administrator rights tho.


If you get the message "this action requires elevation" you should do the following:
create a desktop icon shortcut to CMD.EXE by right-dragging cmd.exe onto the desktop. Then set the icon to "run as administrator" automatically by

Right-click on the icon --> Properties --> Shortcut --> Advanced --> "Run as administrator"

There is a difference between being an administrator and running as administrator.
"ipconfig /flushdns" will now work using this icon.

[archieve]

heya dellica,
thanks for the idea! it turns out, unfortunately, that my host was to blame. after their server bogged down, my ftp tried to connect too many times and they automatically blocked my IP address. grrrr. thanks for the tip about flushing the dns cache though--it was probably worth doing anyway. cheers,


ethan