From: Jim on
I started getting this error recently only on one of my favorite
sites. It is the same with all computers on the network, with both IE
and Firefox. There is no firewall and I can disable the antivirus and
same problem.

The funny part, I can connect to a subpage of the same site, but not
the main page, which is where I get my financial information. I have
not see the problem on any other page so far. Also, one of our
network computers runs 2000 and IE and it has same problem.

Apparently this is a common problem with no definite answers.
Wikipedia has a page on this problem but none of the solutions I have
tried so far has worked.

I even tried typing in the IP address numerically, same problem, so it
is not IP lookup or whatever you call it...

I tried to do a trace but I don't think it can get past our router.

Can anyone help me with this problem?

Jim

From: Twayne on
Since several machines all see the same thing on just one site, then it'd be
highly likely the problem is at the site, not your end. Let them know; they
might appreciate it.

HTH,

Twayne`


n news:h4igt5d7eq4vlei3qhmhjqvv36j011hapv(a)4ax.com,
Jim <nospam(a)nospam.com> typed:
> I started getting this error recently only on one of my
> favorite sites. It is the same with all computers on the
> network, with both IE and Firefox. There is no firewall
> and I can disable the antivirus and same problem.
>
> The funny part, I can connect to a subpage of the same
> site, but not the main page, which is where I get my
> financial information. I have not see the problem on any
> other page so far. Also, one of our network computers runs
> 2000 and IE and it has same problem.
>
> Apparently this is a common problem with no definite
> answers. Wikipedia has a page on this problem but none of
> the solutions I have tried so far has worked.
>
> I even tried typing in the IP address numerically, same
> problem, so it is not IP lookup or whatever you call it...
>
> I tried to do a trace but I don't think it can get past our
> router.
>
> Can anyone help me with this problem?
>
> Jim



From: Jim on
Answer was found when I contacted the site and their IP man asked me
to run a TRACERT, and when I gave him the results, he suggested I
power down the router, or check the network cable, or a few other
things. I powered down the router, and the first time it did not
work I tried it again, and believe it or not, it cured the problem.

This is very strange, as his main page was the only site it would not
load up, but other pages on the same site would load up. The Tracert
showed asterisks in the first hop, so he knew that the timeout was
either in the router or the modem, but he had no idea why it was just
for that one page..... Go figure. I'm a happy camper...

Jim







On Wed, 28 Apr 2010 13:02:06 -0400, "Twayne" <nobody(a)spamcop.net>
wrote:

>Since several machines all see the same thing on just one site, then it'd be
>highly likely the problem is at the site, not your end. Let them know; they
>might appreciate it.
>
>HTH,
>
>Twayne`
>
>
>n news:h4igt5d7eq4vlei3qhmhjqvv36j011hapv(a)4ax.com,
>Jim <nospam(a)nospam.com> typed:
>> I started getting this error recently only on one of my
>> favorite sites. It is the same with all computers on the
>> network, with both IE and Firefox. There is no firewall
>> and I can disable the antivirus and same problem.
>>
>> The funny part, I can connect to a subpage of the same
>> site, but not the main page, which is where I get my
>> financial information. I have not see the problem on any
>> other page so far. Also, one of our network computers runs
>> 2000 and IE and it has same problem.
>>
>> Apparently this is a common problem with no definite
>> answers. Wikipedia has a page on this problem but none of
>> the solutions I have tried so far has worked.
>>
>> I even tried typing in the IP address numerically, same
>> problem, so it is not IP lookup or whatever you call it...
>>
>> I tried to do a trace but I don't think it can get past our
>> router.
>>
>> Can anyone help me with this problem?
>>
>> Jim
>
>

From: Twayne on
In news:2fnht51euil9e3qdjbi8mu236bomds4jbq(a)4ax.com,
Jim <nospam(a)nospam.com> typed:
> Answer was found when I contacted the site and their IP man
> asked me to run a TRACERT, and when I gave him the results,
> he suggested I power down the router, or check the network
> cable, or a few other things. I powered down the router,
> and the first time it did not work I tried it again, and
> believe it or not, it cured the problem.
>
> This is very strange, as his main page was the only site it
> would not load up, but other pages on the same site would
> load up. The Tracert showed asterisks in the first hop, so
> he knew that the timeout was either in the router or the
> modem, but he had no idea why it was just for that one
> page..... Go figure. I'm a happy camper...
>
> Jim
>
>
>
>
>
>
>
> On Wed, 28 Apr 2010 13:02:06 -0400, "Twayne"
> <nobody(a)spamcop.net> wrote:
>
>> Since several machines all see the same thing on just one
>> site, then it'd be highly likely the problem is at the
>> site, not your end. Let them know; they might appreciate
>> it.
>>
>> HTH,
>>
>> Twayne`
>>
>>
>> n news:h4igt5d7eq4vlei3qhmhjqvv36j011hapv(a)4ax.com,
>> Jim <nospam(a)nospam.com> typed:
>>> I started getting this error recently only on one of my
>>> favorite sites. It is the same with all computers on the
>>> network, with both IE and Firefox. There is no firewall
>>> and I can disable the antivirus and same problem.
>>>
>>> The funny part, I can connect to a subpage of the same
>>> site, but not the main page, which is where I get my
>>> financial information. I have not see the problem on any
>>> other page so far. Also, one of our network computers
>>> runs 2000 and IE and it has same problem.
>>>
>>> Apparently this is a common problem with no definite
>>> answers. Wikipedia has a page on this problem but none of
>>> the solutions I have tried so far has worked.
>>>
>>> I even tried typing in the IP address numerically, same
>>> problem, so it is not IP lookup or whatever you call it...
>>>
>>> I tried to do a trace but I don't think it can get past
>>> our router.
>>>
>>> Can anyone help me with this problem?
>>>
>>> Jim

Glad it's sorted out. Thanks for the update; I've never seen that happen.

HTH,

Twayne`