Problem connecting only to specific sites

hi all,
I'm hoping someone will be able to help me out. I'm so very frustrated.

I'm on a G3 ibook running 10.2.8 on dial-up. A few months ago I could
not connect to one specific site. I never solved the problem. Now
there's a second site I cannot to. For simplicity's sake, I'll
concentrate on only one site--misticriver.net.

If I use a wifi connection then I can reach both sites.

This is NOT a good solution to my problem because I only have that
type of connection at school.

I've eliminated the following:

Browser: both Camino and FF fail to connect
ISP: the problem occurs with 2 different dial-up ISPs
Firewall: I have Little Snitch and I don't have those sites blocked.

Other things I've tried:
Disk Utility: I regularly repair and verify disk permissions
Network Utility: traceroute and ping results:"unknown host"

Misc:
Terminal: I don't know anything about terminal. I haven't touched it.
Banning: I'm not banned from either of these sites. I can connect
using wifi, my passwords work, and I emailed the site admin who said I
was a-okay.
Upgrading to Panther/Tiger/Cheetah/Lynx/Whatever: Err, not gonna
happen. Sorry!


Recently installed programs: I rarely install programs and I hadn't
installed anything between when the (latest) site was working and when
it wasn't.

Please help. As I've said, there are now two sites that have this
problem. Once may be dismissed as a weird fluke but twice means that
the problem will probably get worse.

Thank you.

On 2005-10-06 06:44:23 -0400, Julian said:

> Please help. As I've said, there are now two sites that have this
> problem. Once may be dismissed as a weird fluke but twice means that
> the problem will probably get worse.
>
> Thank you.

There is nothing other than a firewall issue that could be wrong with
your machine that would prevent the loading of only some sites. After
you elimnate firewall blocks, then potentially the site is just slow
and the modem chokes. This does not seem to be the problem here.

However, the site name does not get resolved using ARIN which likely
means it is not a properly registered domain name or it maybe name
belonging to a badly configured dymanic DNS.

In traceroute, the last idenfiable host is HOSTDIME. Doing a quick
search on HOSTDIME on dslreports and other sources shows a lot of
users have pretty bad things to say about HOSTDIMES's customer and
technological policies, capabilites and responsiveness. In other words
it looks like your site is hosted a hostdime and they are the ones
responsible. DNS problems are one of the largest complaints I found.

Jim


--
Jim <jen....not....home..remvdots...@....yahoo