FFXIAH becomes unavailable until modem reset.

[Rajwa]

I have a pretty annoying problem I am trying to solve. Certain sites (mainly FFXIAH) become unavailable after I browse them for about 15~60 minutes, sometimes a little longer. The only way I can browse them is to reset my modem or go through a proxy (proxy's wont let me change servers though). I've tried both my modems (I have 2 connections), reset them to factory default, everything I can really think of but the problem keeps happening. Does anyone have an idea or suggestion on what is happening? And even better, how to fix it?

[Luciola]

clear cookies, delete browser temp files, increase temporary file storage capacity.....

[Rajwa]

Done all that. It still stops working after a while. Also tried uninstalling and reinstalling Firefox to see if something was messing up with it. Later I hope to try a friends laptop to see if its my PC or a network issue.

[Kurt Cobain]

ipconfig /flushdns

i think is the command, when i had comcast it used to happen to me and that fixed it (doing it when it would lock up)

[Rajwa]

Haven't tried that, will next time it happens thanks.

[Rajwa]

Took awhile for FFXIAH to stop loading this time, but it finally has, and ipconfig /flushdns doesn't resolve it. Not sure if it matters, but I have Comcast Buisness for my internet connection.

[Zeith]

In what manner do they become unavailable? Are you getting DNS resolution failures (e.g., "Can't find the host at ffxiah.com/Server not found") or is there some other variety of failure, such as the connection timing out or becoming reset?

[Rajwa]

In what manner do they become unavailable? Are you getting DNS resolution failures (e.g., "Can't find the host at ffxiah.com/Server not found") or is there some other variety of failure, such as the connection timing out or becoming reset?

Network time out errors.

[Zeith]

Assuming you're using Windows, try these two commands and post the results:

nslookup ffxiah.com

and

tracert ffxiah.com

if you don't mind.

[Rajwa]

nslookup:

Server: www
Address: 10.1.10.1

Non-authoritative answer
Name: ffxiah.com
Address: 74.54.240.36

It wont let me copy the tracert results... but it's just a lot of "Request Timed Out".

[Zeith]

That's interesting, your web server is also your DNS? In any case, it doesn't look like you're having trouble resolving the hostname, so the problem is somewhere along your route. The only external references on ffxiah.com are to playonline.com and kingbehemoth.com, but if you're seeing RTO on your traceroute to ffxiah.com, it's probably their host that's your problem. You might try just pinging them to see what the latency from ping is, it might just be a matter of your web browser timing out even though you've got a good route. For reference, here's what my rtt times look like:

:~$ ping ffxiah.com
PING ffxiah.com (74.54.240.36) 56(84) bytes of data.
64 bytes from ffxiah.com (74.54.240.36): icmp_seq=1 ttl=48 time=43.7 ms
64 bytes from ffxiah.com (74.54.240.36): icmp_seq=2 ttl=48 time=43.7 ms
64 bytes from ffxiah.com (74.54.240.36): icmp_seq=3 ttl=48 time=43.5 ms
64 bytes from ffxiah.com (74.54.240.36): icmp_seq=4 ttl=48 time=43.4 ms
64 bytes from ffxiah.com (74.54.240.36): icmp_seq=5 ttl=48 time=44.8 ms
64 bytes from ffxiah.com (74.54.240.36): icmp_seq=6 ttl=48 time=44.5 ms
64 bytes from ffxiah.com (74.54.240.36): icmp_seq=7 ttl=48 time=43.6 ms
64 bytes from ffxiah.com (74.54.240.36): icmp_seq=8 ttl=48 time=43.4 ms
64 bytes from ffxiah.com (74.54.240.36): icmp_seq=9 ttl=48 time=43.5 ms
64 bytes from ffxiah.com (74.54.240.36): icmp_seq=10 ttl=48 time=45.0 ms
^C
--- ffxiah.com ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9010ms
rtt min/avg/max/mdev = 43.424/43.941/45.047/0.607 ms

[Rajwa]

I don't have a web server. As for when I ping, it just results in "request timed out" as well.

Thanks for the replies btw, even if it never gets figure out I appreciate people trying to help lol.

[Zeith]

No problem. I wish I could be of more assistance, but it looks like there's a problem somewhere on your route, that's the sort of thing that can take forever to diagnose, it's possible and even probable that the faulty hardware is not at your premises. Next time you are able to access ffxiah.com, I'd recommend running tracert again and taking note of the path and maybe saving it in a document somewhere. Then, when you can't access again, see if you can find a path to each hop. It won't fix the problem, but it may give you a clearer picture of where it lies. It may be an endpoint router controlled by Comcast, and you could at least call them and harass them if that were the case.